BDG Game Deposit and Withdrawal: check wallet status.

Status separation

Payment status and game balance are different records

A bank or UPI app can show a successful transaction while the receiving service has not yet matched it to an account. Conversely, an in-app withdrawal status can say processed before the receiving bank displays a credit. Record the two systems independently.

For a deposit, keep the UTR, amount, payment time, sender account, receiving handle, account identifier and in-app balance before and after. For a withdrawal, keep the request ID, requested amount, deductions, submission time, status changes and the bank statement window covering the expected credit.

Do not edit screenshots, except to redact unrelated sensitive information. Keep the original files privately. A complete timeline reduces confusion when support responses arrive out of order.

Deposit mismatch

When money leaves but balance does not change

Confirm that the payment reached the intended recipient and was not reversed. Check whether the UTR is final, the amount matches the instruction and the receiving handle is the one shown during that transaction. Do not reuse an old QR code or handle without fresh confirmation.

Capture the in-app transaction list and current balance. If the service has a deposit reference field, enter only the actual UTR. Do not create a fake reference or send another payment to “trigger” reconciliation.

Escalate with one message containing the masked account identifier, amount, UTR, timestamp, receiving handle and balance evidence. Keep a case number or message ID. If support changes the recipient after the event, preserve both versions.

Withdrawal states

Pending, processed and credited are not interchangeable

“Pending” normally means the request has not reached a final state. “Processed” may mean the service completed its internal step. “Credited” should be confirmed in the receiving financial record. Do not mark the case resolved solely because one interface changed wording.

Compare the requested amount with any fees or deductions disclosed before confirmation. If identity verification is requested, use only a confirmed in-account route and never share OTP, PIN or remote device access.

If the stated timeframe passes, send one structured escalation. Repeated new tickets can fragment the history. Keep the oldest open reference and add new evidence to it where possible.

Fraud response

Stop the money flow when pressure appears

An unexpected second payment to release the first is a critical warning. So are requests to move to a private contact, pay a personal handle, install remote-control software or show a banking screen. Stop, preserve the conversation and contact the payment provider.

For suspected financial cyber fraud in India, the National Cyber Crime Reporting Portal provides complaint options and identifies 1930 for financial-fraud assistance. Act promptly; do not wait for a social contact to “investigate” while more money is requested.

Reconciliation detail

Build a timeline both sides can read

Begin with the account state before the event. Record the visible balance, transaction list and exact destination. Add the payment-provider event with UTR, amount, time and recipient. Then add every in-account status change and support response in chronological order.

Use exact times rather than “yesterday” or “a while ago.” If systems display different time zones, label them. Keep one amount per event: requested amount, sent amount, fee, credited amount and received amount may differ for legitimate or disputed reasons.

A clear timeline prevents two common mistakes: treating a bank success state as an in-account credit, and treating an internal processed state as a bank receipt. Each status should retain its source.

Resolution standard

Close the case only when the financial record matches

For a deposit, resolution means the correct account received the correct credit or the payment was reversed through the relevant provider. For a withdrawal, resolution means the receiving account shows the expected credit after disclosed deductions, or the service restored the balance with a documented reason.

A promise, ticket closure or changed label is not enough if the financial record still differs. Capture the final outcome and retain the case reference. Do not delete the original transaction evidence immediately after resolution.

If the recipient denies the transaction and the provider confirms delivery, escalate with both records. If fraud is suspected, use authorised financial and cyber-fraud channels rather than paying an intermediary to recover funds.