First, do not pay again
Two payments against one account take far longer to unwind than one that is simply late. Money that has left a wallet is not lost; it is somewhere specific.
Give it ten minutes. A large share of these cases settle on their own inside that window.
Cause one: the reference was wrong
On a manual payment you type the account reference by hand, and one wrong digit sends the money somewhere else. Compare what you entered with the cashier screen, digit by digit.
If it is wrong, say so in the first message to support. A misdirected payment inside the same operator is traceable with the reference and the exact time.
Cause two: the confirmation timed out
The wallet completed the transfer but the operator’s confirmation failed, so the balance posts late rather than never. This is the case that fixes itself.
Nothing you do speeds it up, and repeating the payment only adds a second case to the same ticket.

Ready for the next step?
Open the operator and check the options in your account.
Cause three: the line is not yours
Paying from a relative’s wallet triggers a hold at many operators, because payouts can only return to a line registered in your own name.
The money is not lost, but releasing it usually needs proof and sometimes it is simply refunded. [Verification](/verification/) explains why the names have to match.
Cause four: the account is restricted
An incomplete verification or an account flag can hold a deposit rather than crediting it. The symptom looks identical to a timeout.
Check your account status before writing to support, and finish verification first if it is pending.
Cause five: the wrong recipient
Business numbers are short and similar. If the confirmation message names a different recipient, the case belongs to your mobile money provider rather than the betting site.
Identifying that early saves days, because it is a different queue and a different process.
The message that gets it traced
Send five facts together: the transaction reference from the confirmation message, the amount, the exact time, your sending number and your betting account reference.
Add one line saying which causes you have already ruled out. That turns a template reply into a specific answer.
Stopping it happening again
Use the prompt from the cashier rather than typing a business number, deposit once per session instead of topping up repeatedly, keep the day’s confirmation messages, and always pay from your own registered line.
The first habit alone removes the most common cause. [Payments](/payments/) covers the cashier end to end.
Questions, answered
My money was deducted but the betting balance did not change. What now?
Wait ten minutes, then send support the transaction reference, amount, exact time, your number and your account reference. Do not repeat the payment.
How long should a deposit take?
Seconds. Past ten minutes it is usually a confirmation timeout or a wrong reference rather than a lost payment.
I typed the wrong reference. Is the money gone?
No, but it needs tracing. The reference and exact time are what any investigation starts from.
Can I deposit from someone else’s wallet?
It often triggers a hold, because payouts return only to a line in your own name. Use your own number.
What if the confirmation names a different recipient?
Then the case belongs to your mobile money provider, not the betting site, and their support is the right queue.