Before authorising any payment
Read the action shown by the bank or UPI app, not the words in a chat message. Confirm whether you are sending, collecting, approving a mandate or simply viewing a balance. Check the recipient name or UPI ID, amount and purpose on the final approval screen.
NPCI’s UPI safety material states that a UPI PIN is entered to deduct money and is not required for receiving money. That distinction is central to avoiding fake refund and reward requests. Review the UPI Safety Shield before approving an unfamiliar prompt.
- Use your own device and payment app.
- Do not approve a request while someone controls your screen.
- Verify the amount digit by digit.
- Save the recipient display before confirming.
- Stop when a “small verification debit” is demanded to release a larger amount.
When a deposit is debited but not credited
Separate the bank state from the game-wallet state. A successful bank debit does not by itself prove that the receiving system matched the payment to your account. A pending bank status is different again. Use the bank’s record as the source for whether money left, then use the platform ledger for whether it was credited.
- Capture the bank or UPI status, UTR, amount, recipient and exact time.
- Capture the game-wallet status and account ID without exposing the password.
- Do not make the same payment again while the first state is unclear.
- Wait for the payment app’s stated reconciliation window when it shows pending.
- Contact the payment provider if the transaction status is inconsistent.
- Send a masked evidence set to a verified platform channel with one case reference.
Withdrawal review without guessing
| Status | What it may mean | Useful evidence |
|---|---|---|
| Submitted or queued | The request exists but has not reached a final state. | Request ID, amount, submission time and current status capture. |
| Processing | Internal review or payment initiation may be underway. | Any stated processing window and later status changes. |
| Rejected | Account details, limits, verification or terms may need review. | Exact rejection wording; do not replace it with assumptions. |
| Paid but not received | A transfer reference may need checking with the bank or UPI app. | Platform payout reference, bank statement range and recipient details. |
| Blocked pending another payment | This is a serious warning sign, especially when described as tax, unlock or verification money. | Message, number, payment request and all earlier transaction records. |
A legitimate tax or compliance process should be explainable through documented terms and recognised payment routes. A personal contact demanding an extra transfer to “unlock” existing funds should be treated as a possible fraud signal.
Build a clean incident note
Refund, reward and verification-payment traps
A common deception tells the recipient that money is waiting but a small payment, collect-request approval, QR scan or “account verification” is required first. The amount may begin small and increase after each step. The contact may show a fake credit screen or claim that the earlier payment is refundable.
Receiving money through ordinary UPI does not require entering a UPI PIN. Scanning a QR code and entering a PIN normally authorises a payment from your account. Read the bank or payment-app screen rather than the explanation given in chat.
- Do not pay to release a refund, prize or existing withdrawal.
- Do not install a remote-access app to receive money.
- Do not approve a mandate that is described as a one-time identity check.
- Do not rely on a screenshot as proof that funds have been sent.
- Check the actual bank balance and transaction list independently.
Build a transaction timeline, not a screenshot pile
Arrange evidence in the order events occurred: initial request, approval screen, debit notification, bank status, wallet status, support contact and later demands. Add time and source to each item. A short timeline reveals whether a second payment was made before the first status was known and whether an impersonator entered the conversation later.
14:02 — deposit initiated in app; 14:03 — bank shows successful debit and UTR; 14:05 — wallet still unchanged; 14:16 — unverified number offers help and asks for screen share; 14:18 — interaction ended; 14:21 — verified bank support contacted.
Immediate response to suspected financial fraud
- Stop communication with the person asking for more money or remote access.
- Contact the bank or UPI app through the number or route shown in its own official app or website.
- Call 1930 or report through the National Cyber Crime Reporting Portal.
- Preserve chat, phone number, URL, UPI ID, account number, UTR and screenshots.
- Change email, banking and relevant account passwords from a clean device if credentials may be exposed.
- Do not pay an unofficial recovery agent who promises guaranteed return of funds.
The cybercrime portal also provides suspect-checking and reporting facilities for suspicious identifiers. Use official government pages rather than links sent by the suspected contact.
When the problem is a consumer dispute
A service complaint is not automatically a cybercrime, and a cybercrime complaint is not a substitute for contacting the payment provider. Keep the routes separate. For a consumer grievance, the National Consumer Helpline offers complaint channels and a pre-litigation mechanism. The outcome still depends on facts and jurisdiction.
Money boundaries before play
Payment safety also means limiting exposure. Decide the maximum entertainment amount before opening the app, exclude rent, food, loan, medical and emergency money, and never increase the limit to recover a previous loss. Use the session planner to divide a fixed budget before any deposit.
Reconcile the bank state and wallet state before a second transfer
The bank record and the gaming-account record answer different questions. Use both, with the UTR or reference as the bridge, instead of treating one screenshot as proof of the entire transaction.
| Bank/payment state | Wallet or withdrawal state | Safer next action |
|---|---|---|
| Pending | No credit shown | Do not repeat the transfer. Keep the reference and follow the payment provider's reconciliation status. |
| Successful debit | No credit shown | Save UTR, recipient, amount and time; open one reconciliation case with the responsible service. |
| Failed or reversed | No credit shown | Confirm the reversal in the bank record before deciding whether any new payment is needed. |
| Successful debit | Credit shown | Keep the receipt until the balance and account history remain consistent. |
| No incoming credit | Withdrawal marked paid | Request the payout reference and compare recipient details with the bank or UPI account. |
| Any state | Extra payment demanded to release funds | Stop. Do not pay a release, verification, tax or refund fee to an unverified contact. |
Separate a service dispute from a fraud warning
Likely reconciliation or service issue
- You initiated the known transaction yourself.
- The recipient and amount match the intended payment.
- A valid UTR or bank reference exists.
- The disagreement is between bank status and private wallet status.
- No one is asking for a PIN, screen control or a second payment.
Fraud warning
- A stranger initiated contact or moved the conversation to a personal number.
- You are asked for an OTP, UPI PIN, card PIN or remote screen access.
- A small payment is demanded to unlock a larger refund or withdrawal.
- The recipient changes unexpectedly or does not match the described purpose.
- You are told to keep the transaction secret from the bank.
Redact a payment evidence set without destroying its usefulness
Keep the original privately. For a support copy, leave the date, amount, UTR or reference, transaction state and enough recipient information to identify the transfer. Mask unrelated balances, full account numbers, card numbers, QR codes, OTPs and authentication secrets.