Deposit Not Reflecting in Balance

A deposit that hasn't shown up almost always has a checkable cause before you need to contact support. Work through the order below — most cases resolve at steps 1–3.

Why this happens

Three real causes cover most cases: (1) funds have left your account but haven't finished processing on the payment system's side yet — this is normal, not a sign anything's lost; (2) the name on the paying account doesn't exactly match your DBBet account name, so the system can't auto-match it; (3) the transaction was silently declined by your bank/e-wallet (a daily limit, for example), meaning it was never actually sent.

Resolution Steps

Check the transaction history in your e-wallet or bank app first, not on DBBet. If it shows "Successful," the funds genuinely left your account — move to step 2. If it shows "Failed" or "Pending," the issue is on your bank/wallet's side, and redepositing once that resolves usually fixes it.
Allow 15 minutes, up to a maximum of 48 hours, from when the transaction shows successful in your payment app. The matching and crediting process takes a short amount of time — this is normal, not a problem sign.
Confirm the paying account name exactly matches your DBBet account name. Depositing from a family member's e-wallet or bank account is the single most common cause of a deposit appearing "lost" — the funds arrive in the system but can't be auto-matched to your account.
If it still hasn't arrived after the window above, contact support with: your payment app's transaction reference/ID number, the exact amount and time, and a screenshot of the payment confirmation. Having these ready upfront noticeably speeds up resolution compared to contacting support without them.

Preventing This on Future Deposits

Once this issue is resolved, two small habits reduce the chance of it happening again: first, always deposit from a payment method registered in your own name, not a family member's or friend's, even if you're the one holding the device — the auto-matching system relies on the name matching, not who taps pay. Second, get in the habit of waiting for the "Successful" confirmation in your own payment app before closing it or switching tabs, so you know your side of the transaction for certain before checking your DBBet balance.

When This Isn't a Technical Problem

It's worth distinguishing: a deposit that "hasn't arrived" because it's still in the normal process (steps 1-2 above) is different from a transaction that genuinely failed on your own bank/wallet's side — for example, because a daily transaction limit was exceeded or the balance was insufficient after an admin fee. In the second case, DBBet never received the funds at all, so there's nothing to "find" on DBBet's system — the fix is in your bank/wallet app, not on this page.

FAQ

How long does a deposit usually take?

15 minutes, up to a maximum of 48 hours, from when the transaction shows successful in your payment app. See the resolution steps above if it's been longer than that.

I deposited from someone else's e-wallet account — what do I do?

Contact support with proof of the transaction. It can be manually verified, but it takes longer than a deposit from an account in your own name — for future transactions, always use a payment method registered to you.

Should I deposit again if it hasn't arrived yet?

Don't redeposit just because a few minutes have passed — wait out the window above first. Redepositing before the first transaction has genuinely failed risks creating two transactions that need to be reconciled separately.

Why is the amount that arrived slightly different from what I sent?

For bank transfer/Virtual Account, the system sometimes adds a unique code to the last digit of the amount as a transaction verification marker — make sure you send the exact amount shown on the deposit page, not a rounded figure.