A deposit that has not appeared is almost always one of seven things, and only one of them involves money genuinely going astray. The first move in every case is the same: do not send it again. Find the transaction ID, and send one message containing it.
- 01Never send the money a second time
- 02The transaction ID resolves most cases within minutes
- 03Sender name mismatch is the single most common cause
- 04A wrong digit in the receiving number is the second
- 05Check your wallet history, not the confirmation screen
A deposit that has not appeared feels like money vanishing. It almost never is. In the overwhelming majority of cases it is sitting somewhere identifiable, and the transaction ID finds it.
But the first thing to establish is what not to do.
Rule one: do not send it again
This is the instinct, and it is the wrong one every time.
A duplicate transfer takes one problem — a deposit that needs tracing — and makes it two: a deposit that needs tracing, plus a second transfer that now needs returning. The second one is harder and slower to unwind than the first was to trace.
Wait, gather the details, send one message.
The seven causes, ranked
1. Sender name mismatch
The most common cause by a wide margin.
Deposits are matched by sender name. When the name on the sending wallet matches the account, matching takes seconds and is effectively automatic. When it does not — because a cousin sent it, or the wallet is registered to a parent — somebody has to work out whose money this is, by hand, by asking.
That is where hours go. And it gets worse later: withdrawals are paid only to a wallet in your own name, so funding from somebody else’s wallet also stores up a problem for the day you want your money out.
Fix: say whose wallet it came from, immediately, with the name on it.
2. A wrong digit in the receiving number
The classic. Eleven digits, typed once, usually in a hurry before a match starts.
The money left your wallet and arrived somewhere — just not where you intended. The transaction ID shows exactly where.
Fix: send the transaction ID and the number you used. Say straight away if you took the number from an old chat rather than confirming it, because that changes what recovery looks like.
3. The receipt never reached the desk
Sometimes the transfer is perfect and the message about it never got sent — closed app, lost draft, sent to a different chat.
The desk sees an incoming transfer with no account attached to it. It waits.
Fix: send the screenshot with your account name now.
4. Below the minimum
PKR 500 by wallet, PKR 1,000 by bank. Below that a transfer cannot be credited and has to be returned.
Fix: nothing to fix — the money comes back. Note that you pay a transfer fee in each direction, which is why the minimum is worth checking before sending.
5. Bank transfer timing
A bank transfer sent at 8pm on a Friday is not late. It is waiting for Monday.
Bank transfers run on banking hours and stop for weekends and public holidays. IBFT is faster than some alternatives but it is still not instant at all hours.
Fix: wait for the working day, then chase with the reference number.
6. A provider issue
Easypaisa and JazzCash both have maintenance windows and occasional outages. During one, transfers can sit in the provider’s own queue for a while.
Fix: check whether your wallet app itself is behaving normally. If the wallet is struggling, nothing downstream can move.
7. Peak-time volume
Evening before a big match is the busiest window. Credits still happen; the tail is longer.
Fix: allow a bit more time in the hour before a major game, and send the receipt early rather than at the last minute.
The one message that resolves most cases
Send this, in a single message:
Account name: usman31 Amount: PKR 2,000 Sent at: 21:14, 26 September From: 03XX-XXXXXXX (Easypaisa, in my own name) To: the number I was given at 21:10 Transaction ID: [from the wallet history] [screenshot attached]
Everything traceable, nothing secret. That message usually gets a specific answer in one reply.
Compare it with “my deposit is not showing”, which takes four exchanges before arriving at the same point.
Finding the transaction ID
It is in your wallet’s transaction history, not just on the confirmation screen you already dismissed.
- Easypaisa: open the app → transaction history → find the transfer → open it fully
- JazzCash: app → transactions → the entry → full details
Screenshot the whole entry, including the time. This is also why the funding guide suggests screenshotting at the moment of sending: a screenshot now is five seconds, and finding it afterwards is five minutes.
What never helps
- Sending the money again
- Messaging several different people at once. Two threads about one deposit produces confusion, not speed
- Sending ”?” repeatedly. It does not add information
- Sending your wallet PIN or an OTP. Nobody needs these, and a deposit query is never a reason to hand them over
Preventing the next one
- Confirm the receiving number in your existing chat, for every deposit. Numbers change. Old messages go stale.
- Fund from your own wallet. One habit, two problems solved.
- Screenshot before closing the app. Always.
- Send the receipt immediately, with your account name in the same message.
- Check the minimum before pressing send.
Four of the seven causes above disappear entirely if you do those five things.
Full detail: funding your BetPro account.
FAQ