Teen Patti Withdrawal Stuck: Status Meanings and Wait Limits

The 30-second answer

A stuck Teen Patti withdrawal is not one problem — it is a payout frozen at one specific state in a chain. The states, in order, are requested → processing → pending at bank → on hold (risk/KYC) → reversed → failed. Each one has a different legitimate wait window and a different escalation trigger. A UPI payout still “processing” should clear or auto-reverse by T+1; a bank-leg “deemed success” can legitimately sit up to T+7 working days while NPCI reconciles; a risk/KYC hold can run 7 to 30 days with a real legal basis behind it. The single worst move is re-requesting or re-depositing — that creates a duplicate flag or a double-lock that buries the original payout deeper. This page is the state machine, with the rule behind every number. The hub — 3 Patti withdrawal: why it’s stuck and how to fix it — covers the wider cluster (rails, tax, per-app tables, legality); this page goes deep on the state itself.

Editor’s verdict, up front. Ninety percent of “my Teen Patti withdrawal is stuck” panic comes from reading a single word — “processing,” “pending,” “under review” — as a verdict, when it’s just a position in a queue. The fix is to find out which state you’re actually in, because the state decides everything: how long you’re legitimately required to wait, who owes you action next, and whether the rule-clock is even running yet. A payout still inside the operator’s queue is a gaming-app problem. A payout that left the app and is “processing” on the bank rail is a payment-system problem with hard RBI/NPCI timelines. A payout “on hold” for risk review is a compliance problem with its own legal window. Same word on your screen, three completely different fights. This guide maps the machine, gives you the maximum wait for each state with the rule behind it, and — most importantly — tells you the one self-inflicted mistake that turns a 24-hour delay into a three-week mess.

2026 context you must read first. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) banned all online money games, and its Rules came into force on 1 May 2026. Many big operators suspended cash play from late August 2025. So a “stuck withdrawal” in 2026 is often a wind-down balance recovery, not a live-app delay — but the state machine below is identical for both, because both run on the same NPCI/RBI rails. The one extra rule for 2026: never deposit “to release” a stuck payout. A new deposit into a money game is now illegal, on top of being the classic theft pattern.

Why this page exists: “stuck” is a state, not a status

When you search “teen patti withdrawal stuck” or “teen patti withdrawal pending,” you are looking at a single word on a screen and trying to decode it. The trouble is that the word is almost meaningless on its own. “Processing” on a Teen Patti app can mean any of five completely different things depending on where in the chain the payout actually is — and each of those five has a different owner, a different clock, and a different fix.

A withdrawal is not a single event. It is a baton passed down a relay: from the app’s wallet, to the operator’s payout system, to a payment aggregator (the company that actually moves money — for most Indian apps that’s a RazorpayX-style or Cashfree-style payout provider), to a sponsor bank, onto the NPCI rail (UPI or IMPS), to your beneficiary bank, and finally into your account. At every handoff, the baton can be held, dropped, or bounced back. The label your app shows is just a crude summary of where the baton is — and because the app is at one end of a long chain, its summary is often behind reality by hours.

This is the core insight the hub doesn’t have room for: the app’s status word lags the rail’s true state. Your money can be sitting “reversed” on the aggregator’s side for an hour before your app updates from “processing” to “failed.” Your payout can be genuinely credited while the app still says “pending,” because the credit confirmation hasn’t flowed back up the chain yet. So the first discipline of un-sticking a withdrawal is to stop trusting the single word and start asking: which named state is the baton actually in, and on whose side?

The rest of this page is that map. We name all six states, define exactly what each one means on the operator and rail side, give the maximum legitimate wait for each (with the rule), and tell you the precise trigger to escalate. Then a decision tree to place your own case, a deep dive on the risk/KYC hold, worked timelines, and copy-paste “status clarification” messages that ask for the one thing that actually moves a stuck payout — not sympathy, but a state and a reference number.

The six states of a stuck payout (the state machine)

Here is the full machine. A withdrawal moves left to right; a “stuck” payout is parked at one of these nodes. The states are drawn from how real Indian payout systems actually label transactions — the public RazorpayX payout life-cycle and Cashfree payout response codes are the closest thing to a published source of truth, because these are the engines most card-game apps sit on top of.

The one-line map: states 0 and 3 are gaming-app problems (lever = app support, then consumer forums). States 1, 2, 4, 5 are payment-rail problems (lever = your bank, NPCI UDIR, then the RBI Ombudsman). Knowing which node you’re parked at tells you which door to knock on — and stops you wasting a week shouting at the wrong one.

A crucial property of this machine: it is directional but not one-way at the failure points. A payout in processing (state 1) can resolve forward to credited, or fall back to reversed (state 4). A payout pending at bank (state 2) can confirm as credited, or time out into reversed. So “reversed” is not the same as “failed” — a reversed payout means your money came back to where it started (the app wallet, recoverable), while a failed payout is a terminal stop that needs you to find out where the money actually is before you can claim it. People conflate these two words constantly, and the conflation is expensive: a reversed payout you can simply re-attempt cleanly, while a failed-but-debited payout needs a formal dispute. They are opposite situations wearing similar labels.

The sections below take each state in turn.

State 0 — Requested: it’s still inside the app

What you see: “withdrawal submitted,” “request placed,” “processing your request,” often with no reference number yet.

What it literally means: Your withdrawal exists as a request in the operator’s system, but it has not been approved into an actual payout yet. No money has been handed to any payment rail. There is no UTR because nothing has been sent. This is the operator’s queue — the equivalent of the RazorpayX “pending” or “queued” state on the engine behind the app, where a payout waits for approval or for the operator’s float account to have settled balance.

Why a payout sits here. Three legitimate reasons, in rough order of frequency:

1. Manual approval queue. Small, clean payouts from trusted accounts auto-approve in seconds. New accounts, first-ever withdrawals, large amounts, round numbers, or a sudden win spike get routed to a human or a slower batch. This is the single biggest source of “pending” on a brand-new account.
2. Operator float / settlement timing. The operator pays you from a pooled account that it tops up on a settlement cycle (often T+1). If that account is waiting for its own settlement, your payout queues until funds land — exactly the RazorpayX “queued” state, which holds a payout “until you add sufficient funds”. You never see this; you just see “pending.”
3. A batch window. Some operators don’t push payouts continuously — they release them in batches (e.g., hourly, or twice a day). A request placed just after a batch ran waits for the next one.

The maximum legitimate wait. There is no RBI rule here, because nothing is on the rail yet — this is governed by the app’s own stated payout SLA, which is typically 1 to 3 working days, with most clean UPI payouts moving in minutes. The practical numbers:

• First-ever withdrawal: up to 24 hours is normal (manual KYC/risk review on your first payout is standard).
• Repeat clean payout: seconds to a few hours.
• Large or flagged payout: can sit in manual review for the app’s full stated window.

The escalation trigger. You escalate when you cross from “slow” to “problem” for your case: past the app’s stated window (or past 24 hours on a first withdrawal) with no status change and no reference number. The lever at this state is app support first — raise an in-app ticket, get a ticket ID, because this is a gaming-app problem, not yet a payment one. The RBI rail rules do not apply to a payout that never left the app.

The trap at this state: because there’s no UTR and no rail involvement, panicking players often cancel and re-request, which throws the payout to the back of the queue, or deposit more “to speed it up,” which does nothing but add money to a stalled account. Both are covered in the “why re-requesting makes it worse” section — they are the most common self-inflicted wounds, and they almost always start here, at state 0.

State 1 — Processing: it’s on the rail now

What you see: “processing,” “payment in progress,” “transferring to your account,” and — critically — this is usually the first state where a UTR / reference number appears.

What it literally means: The operator approved your payout, the payment aggregator accepted it, and money has been handed to a payment rail (UPI or IMPS) and is en route to your beneficiary bank. On the engine side this is the literal RazorpayX “processing” state — “either Razorpay or the contact’s bank is actively handling the payout.” The baton has left the gaming app and is now in the payment system. This is the most important handoff on the whole page, because the moment your payout enters this state, RBI/NPCI rules start to apply to it.

Why a payout sits here. For UPI, “processing” should be momentary — UPI is a real-time rail and a successful credit confirms in seconds. So a UPI payout stuck in “processing” means one of:

• The beneficiary bank is slow to confirm the credit (downtime, a queue on their side).
• The credit confirmation got lost in transit — the money may have reached you, but the “success” signal didn’t flow back. This is the seed of the deemed-success state (state 2).
• The handle didn’t resolve and the rail is about to bounce it (heading for reversed, state 4).

For IMPS (used on larger amounts), “processing” is normally instant too; a stall usually means a beneficiary-detail problem.

The maximum legitimate wait — and the rule. This is where the numbers get hard and quotable. Under RBI’s Harmonisation of Turn Around Time (TAT) circular DPSS.CO.PD No.629/02.01.014/2019-20, dated 20 September 2019, a UPI account-to-account transaction where you were debited but not credited must be auto-reversed by T+1 — the day after the transaction. If the rail can’t confirm your credit, the system is obligated to bounce the money back to source by the next day. So a UPI payout stuck in “processing”:

• Up to T+1: legitimately processing. The rail is either confirming your credit or preparing to reverse it. Do not panic, do not re-request.
• Past T+1, still “processing,” money gone: now the rule is being broken, and you have a claim. The same circular requires ₹100 per day compensation for delay beyond the TAT, credited automatically (suo motu — you don’t have to ask, per the circular, though you should chase it if it doesn’t appear).

The escalation trigger. UPI payout still “processing” with money debited and nothing credited past T+1 → this is now a debited-but-not-credited dispute. Capture the UTR, and open the in-app UPI complaint that feeds NPCI’s Unified Dispute and Issue Resolution (UDIR) system. The step-by-step screens for that dispute live on the UPI failed, money debited fix page and the UTR-location and UDIR walkthrough is on the Teen Patti UPI withdrawal fix page.

The single most useful fact about state 1: the UTR is your proof the baton left the building. Once a payout shows “processing” with a UTR, the gaming app can no longer wave you away with “it’s pending on our side” — you have a rail reference, and a rail reference belongs to a regulated payment system with a published TAT. Capture the UTR the instant it appears, because a “failed” or aged transaction buries it in a sub-menu later, and your bank cannot trace a credit you can’t name.

State 2 — Pending at bank (“deemed success”): the limbo nobody explains

This is the state that creates the longest, most confusing waits, and almost no consumer guide names it correctly. It deserves its own deep section.

What you see: the app or your UPI app shows “processing,” “pending,” or sometimes even “success,” but the money is not in your account and the status won’t move. Days pass. Support says “it’s been sent, check with your bank”; the bank says “we have no record.” You are stuck between two parties who each point at the other.

What it literally means: the payout is in “deemed success” (also called “deemed credit” or “deemed approved”). When the payment system sends a credit instruction to your beneficiary bank and the bank’s confirmation doesn’t come back in time — the bank was down, the network timed out, a packet was lost — NPCI cannot know whether the money landed or not. As NPCI’s own handling defines it, DEEMED denotes a transaction with an unknown CREDIT status because the beneficiary bank’s response didn’t reach NPCI. The transaction is neither confirmed success nor confirmed failure. It is in genuine limbo, waiting for the banks to reconcile.

Why “UPI is instant” doesn’t help you here. UPI is instant on the success path. The uncertainty path runs on reconciliation cycles, not real time. Two systems (the sending side and your beneficiary bank) have to compare records and agree on what happened, and that comparison happens in batches, not instantly. This is the gap between “UPI failed but money debited” hour-one panic and the rule-mandated outcome — the rules give the banks time to sort it out before anything reverses.

The maximum legitimate wait — and the number behind it. The reconciliation window for a deemed-success payout is T+7 working days as the outer limit, even though most deemed-success payouts settle on T+1 or T+2. So the honest expectation:

• T+1 to T+2: the overwhelming majority of deemed-success payouts resolve here — either confirmed as credited (money was always there, the signal was just late) or reversed.
• Up to T+7 working days: still within the legitimate reconciliation window. Frustrating, but not yet a rule breach on the reconciliation side.
• The RBI overlay: note the tension between the two rules. RBI’s TAT circular says a debited-but-not-credited UPI A2A transaction auto-reverses by T+1; NPCI’s deemed-success reconciliation can run to T+7. In practice, what this means for you: if by T+1 the money is neither in your account nor reversed to source, you already have a TAT claim (₹100/day), and the deemed-success reconciliation is running in parallel. You don’t have to wait the full T+7 to start the dispute — you raise the UDIR complaint at T+1 and let reconciliation and your complaint run together.

The escalation trigger. Money debited, not credited, not reversed, past T+1 → raise the UPI dispute now (don’t wait for T+7). The dispute itself can take NPCI 3–5 working days to resolve through UDIR. If the deemed-success transaction is eventually confirmed failed, the reversal is automatic; if it’s confirmed success but you genuinely never got it, you escalate with the UTR to your bank to trace where the credit landed.

The chargeback layer (the deadline nobody tells you about). If a UPI dispute isn’t resolved through the normal return process, it can convert into a chargeback — and NPCI revised the dispute timing rules. Under the revision effective 15 February 2025, NPCI introduced auto-acceptance/rejection of chargebacks based on the beneficiary bank’s TCC (Transaction Credit Confirmation) and Returns, processed in the next settlement cycle after a chargeback is raised. The overall TAT for raising and resolving disputes runs up to 45 days for the chargeback layer. You will rarely touch this layer directly — your bank and NPCI handle it — but it explains why a fully stuck UPI dispute has a long tail: the reconciliation is days, but the formal chargeback machinery has a 45-day outer envelope.

Why this state feels like a black hole: it’s the only one where neither party is lying to you. The app genuinely sent it. Your bank genuinely hasn’t recorded a credit. The truth is sitting unreconciled in between, and the only thing that resolves it is the banks’ batch reconciliation finishing — which the rules cap at T+7 working days but usually finishes by T+2. Your job here is not to push harder; it’s to capture the UTR, raise the T+1 dispute so the rule-clock and compensation start, and let the reconciliation run. Pushing a re-request into a deemed-success payout is how you turn one limbo transaction into two.

State 3 — On hold (risk / KYC review): the deep dive

This is the state players fear most, because it’s the one that feels like the app is keeping your money. Sometimes the fear is warranted; usually it isn’t. It needs the most careful explanation, so this is the longest section.

What you see: “under review,” “verification in progress,” “security check,” “account temporarily restricted,” “withdrawal on hold pending verification.” Often there’s no clear timeline and no specific reason — just a generic hold message.

What it literally means: the operator (or its payment aggregator) has intentionally stopped the payout — not because a rail failed, but because something tripped a risk, anti-fraud, or compliance rule. The money is parked, by design, while a human or a system decides whether to release it. Unlike states 1, 2, and 4, this hold is a choice, which is exactly why it has a legal basis you can push on.

What actually flags a payout into a hold. From how Indian RMG operators and their aggregators are required to run risk and AML, the real triggers, in rough order of frequency:

1. Name mismatch (the silent #1). Your bank/UPI name doesn’t reconcile against your PAN/KYC name. Payout systems run a penny-drop verification — a ₹1 test credit that returns the account holder’s name and a match status (Exact / Partial / Mismatch) — and a “Partial” or “Mismatch” parks the payout for manual review. Over 60% of bank-transfer failures trace to incorrect or mismatched account details. One transposed letter — “RAHUL K” on the handle vs “Rahul Kumar” on PAN — is enough.
2. Win-spike / pattern flag. A sudden large win, an unusual win rate, or a withdrawal pattern that looks like collusion or bonus abuse triggers a play-pattern review. Operators’ terms typically reserve a window — commonly up to 30 days — for an operational audit of play patterns and device checks.
3. AML / Enhanced Due Diligence (EDD). This is the one with the hardest legal basis. Online real-money gaming operators are reporting entities under the Prevention of Money Laundering Act — FIU-IND directed real-money gaming companies to register and comply with AML/CFT obligations, retain transaction records for five years, and file Suspicious Transaction Reports. Cash Transaction Reports must be filed when deposits or withdrawals cross ₹10 lakh in a month. For large or unusual payouts, EDD requires verifying your source of funds, and statutory AML review windows commonly run 5–20 business days while documents are assessed. A payout held for “verification” past a few days is frequently a real AML/EDD check, not an excuse.
4. Duplicate-account / multi-device flag. The anti-fraud engine sees the same device fingerprint, IP, or payment instrument across multiple accounts and freezes the payout pending investigation. (Covered in detail in the next section — this is also where self-inflicted damage compounds.)
5. Payment-aggregator-side hold. The aggregator behind the app can itself freeze settlement. RBI’s payment-aggregator framework lets a PA restrict or suspend settlement for transactions with high-risk scores, suspicious circumstances, or excessive disputes/reversals, and to stop settlement until KYC documents are submitted. So your payout can be held by a company you’ve never heard of, one layer below the app.

The maximum legitimate wait — by trigger. This is where you need the number, because “under review” with no timeline is the most anxiety-inducing message in the whole machine:

The escalation trigger — and the move that actually works. A risk hold can legitimately run days to weeks, so the trigger isn’t “it’s been 6 hours.” The trigger is: past 7 days with no written, specific reason given. The single most effective action on a hold is to demand a written reason and a timeline in a support ticket — not to ask “where is my money,” but to ask the operator to state, in writing, (a) the specific reason for the hold, (b) the exact documents or conditions needed to clear it, and (c) the expected resolution date. A regulated, legitimate operator can answer those three questions. An operator that refuses to give any written reason after 7 days is itself a red flag, and that refusal becomes the basis of your consumer-grievance complaint (template at the end). For the contact channels and the scam-number warning specific to the most-searched app, see Teen Patti Master customer care.

The hold paradox: the very fact that a payout is held rather than paid is, counterintuitively, mild evidence it’s a real review and not theft. A regulated operator that wanted to keep your money wouldn’t hold it in a visible “under review” state generating a paper trail — it would reject it with a reason, or stall on the rail. A held payout is one a system has flagged and a human still has to decide on. Your leverage is to make that decision easy and documented: give them clean matching KYC, your source-of-funds proof if asked, your registered number — and demand the written reason that turns a vague hold into a specific, answerable, escalatable question.

The duplicate-account / multi-device flag, in detail

Of all the hold triggers, this is the one players cause themselves most often, so it earns its own breakdown. The anti-fraud engine behind a real-money app builds a fingerprint of every account from signals you don’t see: the device’s hardware ID, the IP address and network, the payment instrument (the same card or UPI handle), the install signature, and behavioural patterns. When two or more accounts share enough of those signals, the engine treats them as one entity wearing several masks — which is exactly what a bonus-abuser or a collusion ring looks like — and it freezes payouts pending an investigation.

The legitimate version of this flag fires for innocent reasons all the time. Two people in one household sharing a Wi-Fi network and one old phone. A player who reinstalled, made a “fresh” account because they forgot the old login, and now has two accounts on one device. A user whose UPI handle was once linked to a relative’s account. None of these is fraud, but each trips the same wire, and the resulting hold is real — the operator is required to investigate before paying, because paying out across linked accounts is precisely the laundering pattern the PMLA reporting-entity rules make it answer for.

The legitimate maximum wait here is harder to pin to a single number, because it depends on the operator clearing the investigation rather than a fixed rail TAT. Treat it as the same up-to-30-day operational-audit window the play-pattern flag uses, but with one critical difference: a device/duplicate flag does not clear by waiting. It clears by contact. The payout will sit indefinitely until you reach support from your registered number, confirm which account is genuinely yours, and ask the operator to whitelist it and release the payout. Passively waiting on a duplicate flag is the one place “just wait” is the wrong advice — the system has stopped, and only a human resolution restarts it.

The self-inflicted compounding is brutal and worth stating plainly: the worst possible response to a duplicate-flag hold is to create another account to “get around” the block — which adds a third masked entity to the fingerprint and converts a recoverable investigation into a near-certain permanent freeze of every linked account. If you’ve been flagged for duplicates, the rule is the opposite of your instinct: stop making accounts, consolidate to your one verified account, contact support once, in writing, and wait for the human decision. The hub’s ten-reason breakdown lists this as reason #10 for the same reason — it’s the flag that punishes panic hardest.

How to actually get a written reason (and what a legitimate one looks like)

“Demand a written reason” is easy to say. Here is what separates a request that works from one the operator ignores. A weak request asks “where is my money?” — which invites a canned “your payout is under review, please wait” with no information and no clock. A strong request asks three specific, answerable questions and states the consequence of silence:

1. What category is the hold? (Risk, KYC/name-mismatch, AML/source-of-funds, duplicate/device, or other.) Naming the categories forces a specific answer instead of “review.”
2. What exactly do you need from me to clear it? (Which document, in which name, in which format.) This converts a vague freeze into a task you can complete today.
3. What is the resolution date? A legitimate operator running a legitimate review can give a date or a window; an operator stalling cannot.

A legitimate written reason, when you get one, looks like this: it names the category (“source-of-funds verification under our AML obligations”), specifies the document (“a bank statement showing the deposits, in the account name matching your PAN”), and gives a window (“processed within 7 working days of receipt”). That answer is good news disguised as friction — it’s a checklist, and once you complete it the hold has to clear or the operator has to give a new reason, which restarts your evidence trail.

An illegitimate response looks like any of these, and each is a red flag that shifts you from “delay” to “possible scam”: a demand that you deposit money to release the withdrawal (never legitimate, and post-PROGA illegal); a refusal to name any category after 7 days; a “reason” that keeps changing each time you complete the last requirement (the moving-goalpost stall); or routing you to a phone “customer care number” that asks for your OTP or UPI PIN (a phishing script — real reviews never need your PIN). When the response is illegitimate, the written record you’ve built becomes the evidence for your consumer-grievance escalation and, if a PIN/OTP was solicited, your cybercrime report to 1930.

The written-reason discipline in one line: you are not begging for your money, you are creating a documented, dated record that forces a legitimate operator to act and exposes an illegitimate one. Either outcome moves you forward — a clear reason gives you a task, and a refused reason gives you a case.

State 4 — Reversed: your money came back (and why that’s good)

What you see: “reversed,” “returned,” “refunded to wallet,” “transaction failed — amount credited back,” or the money simply reappearing in your app balance after a failed attempt.

What it literally means: the payout was attempted on the rail, failed, and the money was bounced back to its source — the app wallet (for a failed payout leg) or your bank (for a failed deposit-side leg). On the engine, this is the literal RazorpayX “reversed” state: “the payout operation fails and funds are credited back.” A payout moves from processing → reversed the moment the system identifies a failure scenario. This is the rail working correctly — it tried, it couldn’t credit you, so it put the money back where it found it.

Why a payout reverses. The common causes, from the Cashfree payout response codes and RazorpayX error handling:

• Beneficiary account / VPA doesn’t exist or is invalid (“ACCOUNT_DOES_NOT_EXIST”) — you closed the account, mistyped the handle, or the UPI ID no longer resolves.
• IMPS not enabled on the beneficiary account — the rail can’t deliver via that mode.
• Beneficiary bank offline — a temporary failure; a re-attempt later usually succeeds.
• Name mismatch caught at the bank’s end even after the app’s KYC passed.

The maximum legitimate wait. A reversal to your app wallet should reflect quickly — typically same-day, and within T+1 at the outer edge as the rail confirms the failure and bounces the funds. A reversal to your bank (deposit-side failure) follows the same T+1 logic under the RBI TAT circular. So:

• Reversed, money back in app wallet: good outcome — you can now fix the underlying cause (correct the handle, complete KYC, switch payout mode) and re-attempt cleanly.
• Reversed in the app’s status but not yet back in the wallet after T+1: chase it — the reversal hasn’t completed, and the same TAT protection applies.

The escalation trigger. Money shown as “reversed” but not actually back in your wallet or account after T+1 → this is now a debited-but-not-credited reversal failure, and you treat it like state 2/5: capture the UTR, raise the dispute, claim the ₹100/day if past T+1.

Why “reversed” is the good stuck state: it means nobody has your money in limbo — it came home. A reversed payout is fully recoverable because the funds are back at source; you just have to fix what caused the bounce and send it again correctly. This is the one state where a careful, single, corrected re-attempt is the right move — but only after you’ve fixed the root cause (the wrong handle, the name mismatch, the disabled IMPS). Re-attempting a reversed payout without fixing the cause just reverses again. Re-attempting while the original is still “processing” (not yet reversed) is the duplicate-flag mistake in the next section.

State 5 — Failed: the terminal state, and where the money actually is

What you see: “failed,” “rejected,” “transaction declined,” “withdrawal unsuccessful” — usually final, with no “retry” promise.

What it literally means: this is a terminal state — the payout did not complete and won’t, in its current form. But “failed” alone tells you nothing about where your money is, and that’s the only question that matters. Three sub-cases hide under one word:

1. Failed and money never left your withdrawable balance. The request was rejected before any debit (rule failure, KYC block, limit hit). Your balance is intact; this is a state-0/state-3 problem wearing a “failed” label. Nothing to recover — fix the rule and re-request.
2. Failed and money debited from the app wallet but not credited to you and not yet reversed. This is the dangerous one — a terminal “failed” status sitting on top of debited-but-not-credited money. The reversal should run (state 4) under T+1; if it doesn’t, you dispute.
3. Failed on the rail but the operator’s status is “ahead of reality” — the app marked it failed while the rail is still reconciling (deemed success). The money might still credit, or reverse. Don’t act on the app’s “failed” alone; check the UTR’s true rail status.

The maximum legitimate wait. “Failed” is terminal, so there’s no waiting — there’s acting. The wait that matters is the T+1 reversal window on any debited-but-not-credited money sitting under the failed status. If the money was debited and a “failed” status appears, the reversal owes you the money back by T+1.

The escalation trigger. Status “failed” + money gone from your wallet/account + not reversed by T+1 → dispute immediately. This is the strongest consumer-protection case in the whole machine, because RBI’s TAT circular mandates the reversal and the ₹100/day compensation. Capture the UTR, raise the UPI dispute (UDIR), and if past T+1, claim the compensation.

The “failed” trap: people see “failed” and either give up (assuming the money’s gone) or spam re-requests (assuming they need to try again). Both are wrong. First find out where the money is — still in your wallet (re-request after fixing the cause), debited-but-not-credited (T+1 reversal, then dispute), or reconciling on the rail (wait for the true status). The word “failed” is the start of a diagnosis, not the end of one.

Why re-requesting or re-depositing makes it worse — the #1 self-inflicted mistake

This is the most important behavioural section on the page, because the single most common way players turn a 24-hour delay into a three-week mess is by acting on panic. Two specific mistakes, each with a precise mechanism behind why it backfires.

Mistake 1 — Re-requesting a withdrawal that’s still in flight (the duplicate flag / double-lock)

You requested ₹5,000. It’s been “processing” for two hours. You cancel it (or it seems stuck) and request again. Now you’ve created a second withdrawal request for the same money. Here’s what that does, mechanically:

• Balance double-lock. Many apps lock the withdrawable balance the moment a request is placed. A second request can either fail (insufficient unlocked balance, because the first request still holds it) or, worse, place a second lock — so now ₹10,000 of intent sits against ₹5,000 of money, and the system can’t cleanly resolve either until a human untangles it.
• Duplicate-payout flag. Risk engines are tuned to spot the same amount, same beneficiary, same short time window — because that’s exactly what a fraud or a double-spend looks like. Two ₹5,000 requests to the same handle minutes apart is a textbook duplicate signal, and it can move your payout from auto-approve into manual review (state 0 → state 3). You’ve just added a hold to a payout that was about to clear.
• Idempotency collision. Payout engines use idempotency keys to prevent paying the same thing twice. A clumsy re-request can collide with the original’s key, and the safe default for a payment system facing ambiguity is to do nothing and flag for review — so both requests stall. (This is why aggregators document careful re-attempt rules and warn against blind retries on error-code recovery.)

The net effect: a payout that was a slow-but-fine state-1 “processing” becomes a held, flagged, double-locked mess that a support agent now has to manually unwind — which takes longer than if you’d done nothing. The rule: if a payout is in states 0, 1, or 2, do not re-request. Wait the legitimate window. Only re-attempt a payout that has cleanly reached state 4 (reversed), and only after fixing the root cause.

Mistake 2 — Depositing more “to release” or “to unlock” the withdrawal

This is both the most common scam pattern and, post-PROGA, illegal. The mechanics of why it backfires:

• No legal app ever requires a deposit to process a withdrawal. A deposit and a withdrawal are independent transactions. There is no system in which adding ₹X “unlocks” a pending ₹Y payout. Anyone telling you so — in-app, on a “customer care number,” over chat — is running the single clearest theft script there is.
• It deepens an AML flag, not clears it. If your payout is on an EDD/AML hold (state 3), adding more deposits increases your transaction velocity and the cumulative amounts the reporting-entity rules watch — pushing you toward the ₹10 lakh/month CTR threshold and toward a Suspicious Transaction Report, not away from a hold.
• Post-PROGA it’s illegal. A new real-money deposit into an online money game is now prohibited. You’d be committing the prohibited act and feeding a stalled or fraudulent account.

The rule: never deposit to unlock a withdrawal. If anyone or anything tells you to, that’s your signal you’re in a scam, not a delay — report it to the cybercrime helpline 1930 and cybercrime.gov.in. The hub’s red-flags section covers the full scam-vs-delay decision; on this page the point is narrow and absolute: re-requesting buries a good payout, and re-depositing buries you.

The discipline in one sentence: a stuck payout in states 0–2 needs patience and documentation, not action; only a state-4 reversed payout earns a careful single re-attempt; and no state ever earns a new deposit. Every “I tried again and now it’s worse” story starts with breaking one of those three rules.

The diagnostic decision tree: status × days × amount × KYC-state

Place your own case here. Read down the questions in order; the first “yes” path that fits you is your verdict. The four inputs that decide everything are: what status you see, how many days it’s been, the amount, and whether your KYC name matches your bank name.

Branch A — There’s no UTR / reference number yet

Your payout never showed a UTR; it’s “submitted,” “pending,” or “processing your request.”

• You are in State 0 (Requested). The money hasn’t left the app.
• First-ever withdrawal, < 24 hours: normal manual review. Wait. Do nothing.
• Past the app’s stated window (or > 24h on a first payout): raise an in-app ticket, get a ticket ID. Gaming-app problem; app support is the lever.
• Amount is large or a round number: expect manual review; it’s the amount that flagged it, not a fault.
• Do NOT cancel-and-re-request or deposit anything.

Branch B — There’s a UTR, status is “processing,” money is debited

The payout left the app; a reference exists; nothing in your account yet.

• You are in State 1 (Processing) heading toward State 2 (Pending at bank).
• UPI, < T+1: legitimately in flight. Wait through T+1. The rail is confirming or reversing.
• UPI, past T+1, still nothing: debited-but-not-credited. Capture the UTR, raise the UPI dispute (UDIR), claim ₹100/day. The RBI TAT circular is on your side.
• Bank/IMPS leg, < T+7 working days: may be in deemed-success reconciliation. Raise the dispute at T+1 anyway; let reconciliation and the complaint run together.

Branch C — Status is “under review” / “verification” / “on hold”

The payout is intentionally frozen.

• You are in State 3 (On hold).
• KYC name ≠ bank name? This is almost certainly the cause. Fix the name to match your PAN exactly, resubmit, expect 24–72h to clear.
• Large or unusual amount / sudden big win: likely a win-spike or AML/EDD review — legitimately 5–20 business days (AML) or up to ~30 days (play-pattern audit).
• Past 7 days, no written reason: demand a written reason + timeline + required documents in a ticket. Refusal to give one = escalate as consumer grievance.
• Anyone asks you to deposit to “release” it: scam. Stop, report to 1930.

Branch D — Status is “reversed” / “returned” / money back in wallet

• You are in State 4 (Reversed). Good outcome — money came home.
• Back in wallet: fix the root cause (wrong handle, name mismatch, disabled IMPS), then re-attempt once, correctly.
• Shown reversed but not actually back after T+1: treat as debited-but-not-credited; dispute.

Branch E — Status is “failed” / “rejected”

• You are in State 5 (Failed). Find the money first.
• Money still in withdrawable balance: a rule/limit/KYC block. Fix the rule, re-request.
• Money debited, gone, not reversed by T+1: strongest dispute case. Capture UTR, raise UDIR dispute, claim ₹100/day.
• App says failed but UTR shows rail still reconciling: wait for the true rail status; don’t act on the app’s label alone.

Branch F — Money arrived but it’s less than you withdrew

• Not a stuck payout at all — it’s tax. This is the 30% TDS on net winnings under Section 194BA. No dispute needed; the cut appears against your PAN in Form 26AS/AIS. Full worked examples are on the hub. Stand down.

How to use the tree: the status word gets you to the right branch; the days tell you whether the rule-clock is running yet; the amount explains why you were flagged; and the KYC-name-match is the silent variable that resolves more “stuck” cases than any other single fact. Check the name match before you escalate anything — it’s the cheapest fix in the machine.

Worked timelines: three realistic stuck-payout journeys

These are illustrative reconstructions built from the rules above — not personal payout tests. They show how the same “stuck” feeling resolves completely differently depending on which state you’re actually in.

Timeline 1 — The slow-but-fine first withdrawal (State 0, resolves itself)

• Day 0, 9:00 PM: Player requests their first-ever ₹2,000 withdrawal. Status: “processing your request.” No UTR.
• Day 0, 9:05 PM: Player panics, sees no movement, considers re-requesting. Correct move: don’t. This is State 0 manual review on a first payout — legitimately up to 24 hours.
• Day 1, 11:00 AM: Status changes to “processing” with a UTR (now State 1). The operator’s manual KYC review cleared overnight and pushed it to the rail.
• Day 1, 11:02 AM: ₹2,000 credited. Total elapsed: ~14 hours, entirely normal for a first payout.
• Lesson: the only thing that could have gone wrong was the player breaking the no-re-request rule at minute five.

Timeline 2 — The deemed-success limbo (State 2, needs a T+1 dispute)

• Day 0, 6:00 PM: ₹8,000 payout shows “processing” with UTR. Beneficiary bank has intermittent downtime.
• Day 0, 6:01 PM: Credit instruction sent; bank’s confirmation doesn’t return. Transaction is now deemed success (State 2).
• Day 1, all day: Still “processing,” money debited, nothing credited, nothing reversed. This is the T+1 trigger.
• Day 1, evening: Player captures the UTR, raises the in-app UPI dispute (feeds NPCI UDIR), and notes the ₹100/day entitlement.
• Day 2–3: NPCI/bank reconciliation completes within the T+7 working-day window — here it confirms the credit had actually landed late, or reverses and re-credits. Player’s dispute (raised at T+1) ensures the rule-clock and any compensation are running.
• Lesson: the dispute at T+1 is what protects the player; waiting passively for T+7 would have been within the rules but slower and without the compensation clock started.

Timeline 3 — The risk hold on a big win (State 3, needs a written reason)

• Day 0: Player wins ₹40,000 in one session, requests a ₹40,000 withdrawal. Status: “under review.”
• Day 0–2: No movement. This is a win-spike/AML flag — legitimately within the 5–20 business-day EDD window.
• Day 3: Player raises a ticket asking for (a) the specific reason, (b) required documents, (c) a resolution date — in writing.
• Day 4: Operator replies: source-of-funds verification required (a legitimate EDD step for a large, sudden payout). Player submits the requested proof.
• Day 7–12: Hold clears once documents are assessed; ₹40,000 minus 30% TDS on net winnings is paid.
• Lesson: the written-reason request converted a vague, anxiety-inducing hold into a specific, answerable step — and gave the player a documented timeline to escalate against if the operator had stalled past the legitimate window.

Timeline 4 — The duplicate-flag freeze that got worse before it got better

• Day 0: Player’s ₹3,000 payout goes “under review.” Cause: they made a second account months ago on the same phone and forgot.
• Day 0–1: Player assumes it’s a normal delay and waits.
• Day 2: Still frozen. Player’s instinct is to make a “clean” new account and withdraw from there — the single worst move, which would add a third linked entity to the fingerprint.
• Day 2 (corrected path): Instead, player contacts support from the registered number, explains both accounts are theirs, and asks the operator to identify the genuine account and release the payout.
• Day 4–6: Operator verifies, whitelists the real account, and releases ₹3,000 minus applicable TDS.
• Lesson: the duplicate flag is the one hold that never clears by waiting and always worsens with new accounts — the only key is a single, honest, registered-number contact.

What the operator and the rail see that you don’t

The deepest reason “stuck” is so confusing is an information asymmetry: you see one word on a screen, while the payout has three simultaneous truths — the operator’s truth, the aggregator’s truth, and the rail’s truth — and those three are often out of sync by hours. Understanding what each layer can see explains why support’s answer and your bank’s answer can both be honest and still contradict each other.

What you see: a single status label, refreshed whenever the app last polled its payout provider. It is the most lagged view in the chain, because it sits at the top and depends on confirmations flowing all the way back up.

What the operator sees: the payout provider’s status (queued / processing / processed / reversed) plus their own risk and KYC flags. The operator knows whether they approved and released the payout, and whether a hold is theirs. What the operator often cannot see in real time is the final beneficiary-bank credit confirmation — which is why support genuinely says “we’ve sent it, check with your bank.” They’re not lying; the credit leg is below their visibility.

What the aggregator sees: the RazorpayX/Cashfree payout state — the most precise label in the chain. The aggregator knows if a payout is genuinely processing, has reversed, or sits in deemed success awaiting reconciliation. This layer is where the true state lives, and it’s the layer your app’s label is a lagged copy of.

What the rail (NPCI / beneficiary bank) sees: the transaction’s reconciliation status against the UTR — confirmed credit, pending reconciliation, or returned. Your bank can trace a UTR here. This is why the UTR is the master key: it’s the one identifier that lets you query the bottom of the chain directly, bypassing the lagged labels above it.

The practical payoff of understanding the asymmetry: stop trying to reconcile two contradictory upper-layer answers, and go to the bottom layer with the UTR. When the app says “sent” and your bank says “no record,” neither is necessarily wrong — the truth is in the reconciliation status the UTR points to. Capturing the UTR and asking your bank to trace that specific reference collapses the asymmetry into a single answer: either there’s a confirmed credit (and you find where it landed) or there isn’t (and the reversal/dispute is owed).

The asymmetry in one line: your app shows the most lagged truth, the aggregator holds the most precise one, and the UTR is the thread that lets you query the bottom of the chain directly — which is why every escalation on this page funnels you toward capturing and tracing that one number.

How to read your own transaction history to find the true state

You can place yourself in the state machine in under two minutes using records you already have. Three sources, checked in order:

1. The app’s withdrawal/transaction screen. Read two things, not one: the status word and whether a UTR/reference number exists. No UTR = State 0 (still in the app). A UTR present = the payout reached at least State 1 (on the rail), and the rail rules now apply. Also read the withdrawable balance figure, not the headline wallet number — a “missing” payout is sometimes just bonus or deposit money that was never withdrawable in the first place, which is a non-issue, not a stuck payout.

2. Your UPI app’s transaction history. Open the entry for the payout (matched by amount and time) and read its label and reference. Recall the labels differ by app — PhonePe shows “UPI Reference No.”, Google Pay “Bank Reference ID”, Paytm “UPI Ref No.”, BHIM “Transaction ID” — but they’re the same 12-digit UTR. If your UPI app shows the transaction as failed/reversed but your bank balance is unchanged, the money is genuinely not gone and the dispute is straightforward. The exact menu paths to find and dispute each are on the UPI withdrawal fix page.

3. Your bank statement / passbook. This is the ground truth for whether money actually moved on your side. A debit with no matching credit, or a credit you can match to the UTR, settles the question the upper layers can’t. For a deposit-side failure (money left your bank but the chips never arrived), the bank statement is where you confirm the debit to dispute.

Cross-reading these three places resolves most “which state am I in?” questions instantly: no UTR anywhere → State 0, app problem. UTR present, app says processing, bank shows debit but no credit → State 1/2, rail problem, T+1 clock. App says reversed and the money is back in wallet → State 4, fix-and-retry. App says failed, money debited, no reversal → State 5, dispute now. The whole diagnostic is just matching the status word against whether a UTR exists against what your bank statement actually shows — three facts you can pull up yourself before you contact anyone.

The two-minute self-diagnosis: status word + does a UTR exist + does my bank statement show a debit without a credit. Those three facts place you in the machine and tell you whether you’re waiting on the app or on the rail — before a single support message is sent.

Copy-paste status-clarification messages

These ask for the one thing that moves a stuck payout: a named state and a reference number, not sympathy. Fill the brackets. Keep every message factual, dated, and reference-stamped.

Message 1 — Clarify which state you’re in (any stuck status, Day 0–1)

Subject: Withdrawal status clarification — ₹[AMOUNT] requested [DATE, TIME]

My withdrawal of ₹[AMOUNT] requested on [DATE, TIME] shows
"[STATUS shown in app]". Please confirm, specifically:
1. Has this payout been handed to the payment rail yet? (Is there a UTR?)
2. If yes, what is the UTR / reference number?
3. If it is on hold or under review, what is the exact reason and what
   do you need from me to release it?
4. What is the expected resolution date?
Registered mobile: [NUMBER]
UPI ID / bank used: [HANDLE / A/C]
KYC status: [completed / PAN matches bank name: yes/no]
Please share a ticket/complaint ID for this request.

Message 2 — Demand a written reason on a hold (State 3, Day 7+)

Subject: [TICKET ID] Withdrawal on hold ₹[AMOUNT] — written reason requested

My withdrawal of ₹[AMOUNT] (requested [DATE]) has been on hold/under
review for [N] days. Please provide, in writing:
1. The specific reason for the hold (risk, KYC, AML/EDD, or other).
2. The exact documents or conditions required to clear it.
3. A definite resolution date.
My KYC is complete and my bank account name matches my PAN. If a
source-of-funds or document check is required, I will provide it on
receipt of a clear request. If no written reason and timeline is
provided, I will escalate to the National Consumer Helpline (1915)
and, for any rail-side amount, my bank's UPI dispute process.

Message 3 — Convert a stuck rail payout to a dispute (States 1/2/5, past T+1)

Subject: Failed/undelivered UPI payout — UTR [UTR] — refund + TAT compensation

A withdrawal of ₹[AMOUNT] (requested [DATE, TIME]) shows
"[processing/failed/reversed]" with money debited and not credited.
- UTR / reference (RRN): [UTR]
- Beneficiary UPI ID / account: [HANDLE / A/C]
It is now [N] days, past T+1. Per RBI circular
DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019), a debited-but-not-
credited UPI transaction must be auto-reversed by T+1, with ₹100/day
compensation for delay beyond T+1. Please reverse/credit ₹[AMOUNT],
apply the compensation, and share the complaint reference number.

Send Message 3 through your UPI app’s “raise complaint / dispute” on the transaction (it feeds NPCI UDIR) or your bank’s failed-transaction desk with the UTR — the per-app menu paths and the screen-by-screen dispute are on the UPI failed, money debited fix page.

How the state machine maps to the Day-0-to-30 ladder

The hub’s escalation ladder is the when; this page’s state machine is the what. They fit together precisely:

• State 0 (Requested) → Day 0 rung: document and open the in-app ticket. No rail involvement, so no payment dispute yet.
• State 1 (Processing) → Day 0–3: capture the UTR, wait the rail’s TAT (T+1 for UPI).
• State 2 (Pending at bank / deemed success) → Day 1 onward: raise the UPI dispute at T+1; reconciliation runs up to T+7 working days in parallel.
• State 3 (On hold) → Day 0–7 with the app; demand a written reason by Day 7; consumer-helpline route (1915) if no reason past the legitimate window.
• State 4 (Reversed) → fix-and-re-attempt once; dispute only if the reversal itself doesn’t land by T+1.
• State 5 (Failed) → immediate dispute on any debited-but-not-credited money; capture UTR, claim ₹100/day past T+1.

The full ladder with every template and the RBI Ombudsman endgame (the 30-day eligibility gate, cms.rbi.org.in) is on the hub page. This page’s job is to make sure you climb the right ladder — the rail ladder for states 1/2/4/5, the app/consumer ladder for states 0/3 — instead of wasting days on the wrong one.

FAQ

1. What does “processing” actually mean on a Teen Patti withdrawal? It means the operator approved your payout and handed it to a payment rail (UPI or IMPS), and money is in transit — this is the literal RazorpayX “processing” state. For UPI it should clear in seconds; if it’s still “processing” with money debited and nothing credited past T+1, you have a debited-but-not-credited dispute under the RBI TAT circular.

2. How long can a Teen Patti withdrawal legitimately stay “pending”? It depends on the state. Inside the app’s queue (State 0) the limit is the app’s stated window, often 24 hours on a first payout. On the rail in “deemed success” (State 2) the reconciliation outer limit is T+7 working days, though most settle by T+1–T+2. A risk/KYC hold (State 3) can run 7–30 days depending on the trigger.

3. My UPI withdrawal has been “processing” for 2 days — is the money lost? Almost certainly not. Past T+1 a debited-but-not-credited UPI payout is either being reconciled (deemed success, up to T+7 working days) or owed back to you. Capture the UTR and raise the in-app UPI dispute, which feeds NPCI UDIR; NPCI’s resolution window is 3–5 working days, and you’re owed ₹100/day beyond T+1.

4. What is “deemed success” and why is my payout stuck in it? Deemed success is when the payment system sent a credit instruction to your bank but the bank’s confirmation didn’t return in time, so the credit status is unknown — NPCI defines DEEMED as an unknown credit status because the beneficiary bank’s response didn’t reach NPCI. It resolves on bank reconciliation, capped at T+7 working days but usually done by T+2.

5. The app says “reversed” — does that mean I lost the money? No — reversed is the good state. It means the payout failed on the rail and the money was bounced back to source (your app wallet or bank), per the RazorpayX reversed state definition. Fix the cause (wrong handle, name mismatch, disabled IMPS) and re-attempt once. If it shows reversed but isn’t actually back after T+1, dispute it.

6. What’s the difference between “reversed” and “failed”? Reversed means your money came back to source and is recoverable. Failed is a terminal state that tells you nothing about where the money is — it could be still in your wallet (rule block), debited-but-not-credited (T+1 reversal owed), or reconciling on the rail. Always find where the money is before acting on “failed.”

7. Why is my withdrawal “under review” and how long can that last? A review/hold is an intentional freeze for risk, KYC, or AML reasons. A name-mismatch re-check clears in 24–72 hours once you fix it; an AML/EDD source-of-funds check can run 5–20 business days; a play-pattern audit up to ~30 days. Real-money gaming operators are PMLA reporting entities, so large or sudden payouts genuinely trigger these checks.

8. Will re-requesting my stuck withdrawal make it go faster? No — it usually makes it slower. A second request for the same money creates a duplicate-payout flag and can double-lock your balance, moving a payout from auto-approve into manual review. Aggregators warn against blind retries because of idempotency collisions. Only re-attempt a payout that has cleanly reached the reversed state, after fixing the cause.

9. Should I deposit money to “release” or “unlock” a stuck withdrawal? Never. No legal app requires a deposit to process a withdrawal — anyone telling you so is running the clearest theft script there is, and post-PROGA a new deposit into a money game is also illegal. It also pushes you toward the ₹10 lakh/month reporting threshold and deepens any AML flag. Report demands like this to cybercrime 1930.

10. My name on my bank account doesn’t match my PAN — is that why it’s stuck? Very likely. Payout systems run a penny-drop check that returns Exact/Partial/Mismatch on the account name, and a mismatch parks the payout for review — over 60% of bank-transfer failures trace to detail mismatches. Make your bank/UPI name match your PAN exactly, resubmit, and expect 24–72 hours to clear.

11. There’s no UTR on my pending withdrawal — what does that tell me? That the payout is still inside the app (State 0) and hasn’t been handed to any rail — which is why there’s no rail reference. The RBI/NPCI rail rules don’t apply yet; this is a gaming-app problem, so raise an in-app ticket. A UTR only appears once the payout reaches the processing state and is genuinely on UPI/IMPS.

12. How long does the NPCI dispute take once I raise it? NPCI’s stated UDIR resolution window is 3–5 working days. If it converts into a formal chargeback, the revised dispute TAT runs up to 45 days for that machinery, with auto-acceptance/rejection of chargebacks effective 15 February 2025. You rarely touch the chargeback layer directly — your bank and NPCI handle it.

13. When exactly should I escalate to my bank instead of the app? The moment the payout is on the rail (State 1/2/4/5) with money debited and not credited past T+1. Rail problems go to your bank and NPCI; app problems (States 0 and 3) stay with app support first. The split is decided by whether a UTR exists — a UTR means it’s a payment-rail matter with RBI TAT protection.

14. The operator won’t tell me why my payout is held — what now? Send a written ticket demanding (1) the specific reason, (2) the documents needed, (3) a resolution date. A legitimate operator can answer all three. Refusal past 7 days is itself the basis of a complaint — escalate to the National Consumer Helpline 1915 for the service deficiency, and pursue any rail-side amount through your bank.

15. Can I get my balance out of a Teen Patti app that shut down under PROGA? Yes — banks and intermediaries kept processing withdrawals so users could recover existing balances even after cash games stopped. The same state machine applies: complete KYC, follow the in-app withdrawal flow, expect 30% TDS on net winnings, and never re-deposit. The hub’s wind-down recovery section covers the operator-specific detail.

Sources & method. The payout state machine on this page is built from primary and authoritative payment-system sources — not personal payout tests. Key references: the RazorpayX payout states & life-cycle and payout error codes (the engine layer most card-game apps sit on); Cashfree payout response codes and penny-drop verification; the RazorpayX explainer on deemed-success and T+7 reconciliation; RBI’s failed-transaction TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019) and the NPCI IMPS/UPI TAT harmonisation circular; NPCI UPI Help / UDIR; the NPCI revised dispute/chargeback TAT (effective 15 Feb 2025) and chargeback TAT circular; FIU-IND / PMLA reporting-entity obligations for online gaming operators and CTR/STR thresholds; RBI payment-aggregator settlement/KYC hold powers; CBDT Section 194BA TDS; and the Promotion and Regulation of Online Gaming Act, 2025 with its Rules effective 1 May 2026. This page is information, not legal or financial advice — verify each step against your operator’s current Terms and your bank’s UPI dispute policy. Cybercrime reporting: helpline 1930 / cybercrime.gov.in. Consumer grievance: National Consumer Helpline 1915.