Withdrawal Time by App: How Long a 3 Patti / Rummy Payout Takes

The 40-second answer

A teen patti or rummy withdrawal time is the sum of four clocks, not one: the app’s review window, the KYC gate, the payout rail (UPI, IMPS or NEFT), and the bank credit. A clean repeat UPI payout under ₹1 lakh can land in seconds to a few hours; a first-ever withdrawal or a manual review adds hours up to 24 hours. IMPS clears instantly up to ₹5 lakh; NEFT moves in half-hourly batches, so 30 minutes to 2 hours is normal, not stuck. This page predicts your time and benchmarks it against operator claims.

Read this before you panic. “Instant withdrawal” is a marketing phrase, not a payment guarantee. The honest answer to “how long does my withdrawal take” is it depends on which rail it rode and which gate it’s sitting at — and almost every “stuck” payout is one of five boring, time-bound things, each with a known clock. This is the hub’s /fix/3-patti-withdrawal escalation guide turned inside-out: that page tells you what to do when a payout is late; this page tells you what “late” even means, app by app and method by method, so you don’t escalate a payout that’s still inside its normal window — or wait two days on one that blew past it on hour one.

2026 reality you can’t skip. The timing picture changed when India’s biggest real-money apps stopped taking cash bets. The Promotion and Regulation of Online Gaming Act, 2025 prohibits all online money games, and from late August 2025 operators like RummyCircle, Junglee Rummy, Dream11, MPL and Adda52 suspended their cash formats. That means a large share of 2026 “withdrawal time” questions are actually wind-down recovery questions — “how long until my stranded balance comes out of a discontinued app” — which runs on a different and sometimes slower clock than a live-app payout. This page covers both, and flags which is which. The one rule that overrides every timing number below: never deposit again “to speed up” a withdrawal — on a money game that deposit is now illegal, and it never makes a payout faster.

The anatomy of “how long”: the four clocks inside one withdrawal

When you tap “withdraw” and stare at a “processing” spinner, you are not waiting on one timer. You are waiting on four, in sequence, and your total withdrawal time is whichever ones happen to be slow that day. Naming the four is the whole skill, because it turns a vague “it’s been a while” into a specific “I’m stuck at clock 3, which means I wait for the next batch.”

Clock 1 — The app-side review window

Before any money touches a payment rail, the app’s own systems decide whether to release the payout now or send it to a queue. This is the most variable clock and the one operators talk about least. A small, clean, repeat payout from a trusted account is usually auto-approved in seconds. A first-ever withdrawal, a large amount, a round-number request, a sudden win spike, or any account the risk engine doesn’t fully trust gets routed to manual review, which can add anywhere from a few minutes to 24 hours. Most “pending for 6 hours” complaints live entirely inside clock 1 — the money hasn’t even reached the rail yet.

The single most useful fact about clock 1: it is shortest for accounts that look boring to a fraud system. Same device, same UPI handle every time, KYC name matching the bank name exactly, no bonus-abuse pattern. The more “interesting” your account looks, the longer clock 1 runs.

Clock 2 — The KYC gate

No legal Indian real-money app pays cash to an unverified account, because anti-money-laundering law forbids it. If your PAN and Aadhaar KYC is complete and matches, clock 2 is effectively zero — it was already paid on a prior withdrawal. If it isn’t, clock 2 can dominate everything: a name mismatch between your UPI handle and your PAN parks the payout in manual review until a human resolves it, which is where “first withdrawal stuck for 2 days while later ones were instant” comes from. On RummyCircle the rule was that your PAN had to be verified and match your KYC documents exactly before any withdrawal cleared, and on Junglee Rummy KYC became mandatory at the first withdrawal or once cumulative deposits crossed ₹50,000, whichever hit first. Both apps have discontinued cash play, but the pattern is identical on every legal RMG app: the cash-out is the moment KYC is enforced, so the first withdrawal carries the full clock-2 cost and every one after it pays almost nothing. The hub page /fix/3-patti-withdrawal covers the KYC-mismatch fix in detail; here the point is just timing — budget extra hours for clock 2 on your first payout, and almost none after.

Clock 3 — The payout rail (UPI / IMPS / NEFT)

Once the app approves and KYC is clear, the money is handed to a payment rail, and the rail has its own physics. UPI is near-instant on the success path. IMPS is instant and works 24×7. NEFT does not move instantly — it settles in half-hourly batches, so a NEFT payout that “just missed” a batch waits for the next one, which is why 30 minutes to 2 hours on NEFT is normal rather than broken. RTGS (for very large transfers, minimum ₹2 lakh) is real-time but only used for big amounts. Clock 3 is the one with the hardest, most predictable numbers, because the Reserve Bank of India and NPCI publish the rules. The detailed rail-by-rail matrix is the heart of this page, a few sections down.

Clock 4 — The bank credit (the part nobody controls)

Even after the rail fires, your receiving bank has to post the credit. On UPI and IMPS this is usually instant. But a beneficiary bank that’s temporarily down, a daily-limit cap on your receiving account, or a stale UPI handle that no longer resolves can stall clock 4 — and this is where the dreaded “debited but not credited” state is born. The good news is that clock 4 has the strongest consumer protection of all four: under RBI’s failed-transaction circular, a UPI payout that was debited but not credited must be auto-reversed by T+1, and your bank owes you ₹100 per day of delay after that. So a clock-4 failure is, counter-intuitively, the best place to be stuck — the refund is rule-mandated and largely automatic.

The whole anatomy in one line: your withdrawal time is clock 1 (app review) + clock 2 (KYC, usually only once) + clock 3 (rail physics) + clock 4 (bank credit). Three of the four are usually near-zero on a clean repeat payout, which is why “instant” feels true most of the time — and why, when it isn’t, you can name exactly which clock is running long instead of guessing.

Why the four clocks run in series, not parallel

A subtle point that trips up a lot of people: these clocks are sequential, not simultaneous. The app won’t hand your money to a rail (clock 3) until it has approved the request (clock 1) and confirmed KYC (clock 2). The rail won’t even try to credit your bank (clock 4) until the app has fired it. So a stall at an early clock blocks everything downstream — a payout stuck in manual review hasn’t “lost” on the rail, because it never reached the rail. This matters for where you complain: a payout stuck at clock 1 or 2 is a gaming-app problem, and your lever is app support. A payout stuck at clock 3 or 4 is a payment-rail problem, and your lever is your bank and NPCI. Misreading which clock you’re at sends you to the wrong door and wastes days — the hub’s diagnostic at /fix/3-patti-withdrawal sorts this for you.

How to tell which clock you’re stuck at, from the screen

You can usually read your clock off the status text without asking anyone. “Processing,” “pending,” or “under review” with no UTR means you’re at clock 1 or 2 — the money is still inside the app, nothing has hit the rail, and there’s no transaction reference yet because no transaction has been initiated. A UTR has appeared and the status says “paid” or “success” but your bank shows nothing means you’ve cleared clocks 1–3 and you’re stuck at clock 4, the bank credit — that UTR is the thread you’ll use to trace the missing money. “Failed” with money gone from your wallet is a clock-4 rail failure, the most protected state, governed by the T+1 auto-reversal rule. So the presence or absence of a UTR is the single best signal of how far your payout actually got.

The time-by-app-and-method matrix

Here is the deep version of what the hub’s per-app table only sketches. The columns split deliberately. Operator-claimed is what an app’s own help page or listing states. Observed / realistic is what third-party trackers and player reports widely describe, framed third-person — not a personal payout test. Read the claimed column as the promise and the observed column as your planning number. Every legal app also deducts 30% TDS on net winnings under Section 194BA before paying, so a payout smaller than requested is usually tax, not delay — the hub’s /fix/3-patti-withdrawal tax section has the worked math.

A blunt 2026 caveat sits over the whole table: RummyCircle and Junglee Rummy discontinued cash games under PROGA, so their rows describe how they worked and how a wind-down balance recovery still behaves, since banks were instructed to keep processing those withdrawals. Teen Patti Gold and Teen Patti Master are informal-brand card apps with many skins and less authoritative published numbers, so their observed column matters more than their claimed one.

Teen Patti Gold — withdrawal time by method

Editor’s note on Teen Patti Gold timing. Because “Teen Patti Gold” is a brand applied to many builds, no single authoritative time table exists — judge by the specific listing you installed. The reliable pattern is: UPI repeat payouts are same-day or faster, the first one is slower because of KYC, and bank transfers are the slow lane at 24–48 hours. The app-specific not-received walkthrough is in the hub cluster at /fix/3-patti-withdrawal.

Teen Patti Master — withdrawal time by method

For the contact-and-scam-safety side of this specific app, the cluster’s customer-care guidance lives off the hub at /fix/3-patti-withdrawal. On timing, the Master pattern matches Gold: UPI is the fast lane, first/new-account payouts pay the clock-2 tax, and bank transfer is slow.

Junglee Rummy — withdrawal time (cash discontinued; wind-down recovery)

The dedicated wind-down timing and recovery flow for this operator is at /fix/junglee-rummy-withdrawal. The headline for 2026: there is no live “fast” Junglee payout anymore — there is only a recovery payout, and it runs on normal rail timing once KYC is clean, with the same 30% TDS as before.

RummyCircle — withdrawal time (cash discontinued; wind-down recovery)

RummyCircle’s own published claim of UPI 2–4 hours, bank 24–48 hours is the single most useful operator-stated TAT in this whole guide, because it’s specific and method-split — exactly the shape of a realistic benchmark. Treat it as the upper-bound promise on a clean account, and add clock-2 time on a first/recovery payout where KYC has to re-clear.

Paytm-as-destination — a separate timing wrinkle

A lot of teen patti payouts land in a Paytm UPI handle or Paytm Payments Bank account, and Paytm adds its own small clock. Paytm’s guidance is that a UPI payout is “usually settled within a few hours,” and that a UPI transaction debited but not credited is typically auto-refunded within 24–72 hours, consistent with the NPCI T+1 rule. So if your app says “paid” but Paytm hasn’t shown it, the realistic window before you escalate is the rest of the day, then T+1 — not hour one. The Paytm-specific pending-payout walkthrough, including where the money actually sits, is at /fix/paytm-withdrawal-pending-gaming.

Reading the matrix correctly: across every app, UPI repeat = fast (seconds to a few hours), first/new-account = slower (KYC clock), bank transfer/IMPS = slow lane (24–48h). The operator’s headline “instant” describes the best row only. Plan from the observed column for your specific scenario, not from the marketing line.

The payout rails: UPI vs IMPS vs NEFT vs RTGS, with verified timings

Which rail your payout rides is the single biggest driver of clock 3, and the rail timings are not guesswork — they’re set by RBI and NPCI rules. Here is each rail with its verified clearing time, cap, and failure behaviour. Card-game apps default to UPI for small amounts and fall back to IMPS or NEFT for larger ones or when a UPI handle won’t resolve.

UPI — the instant rail (and its one slow trap)

UPI is run by NPCI and is the default for most card-game payouts because it’s near-instant. The standard limit is ₹1 lakh per day, combining all your outgoing UPI across apps on the same bank account. There’s a timing trap worth knowing for receiving: a brand-new UPI registration is capped at ₹5,000 for the first 24 hours, auto-lifting after 24 hours on Android (72 hours on iPhone). That’s a sending limit, but if your withdrawal destination is a freshly created UPI ID, related low-limit friction can stall the credit. UPI is 24×7×365, so the rail itself never “closes” — a UPI payout at 2 AM on a Sunday clears as fast as one at noon on a Tuesday. The slow path is the failure path, covered below.

IMPS — instant, and the big-amount workhorse

IMPS is also instant and runs 24×7×365, with a per-transaction ceiling of up to ₹5 lakh. This is the rail apps reach for when a payout is too big for a comfortable UPI transfer or when a UPI handle won’t resolve. An IMPS payout that stalls is almost always a beneficiary-detail mismatch rather than a timing issue, so if an IMPS payout is late, suspect wrong account/IFSC details, not the rail.

NEFT — the batch rail (why “an hour” is normal, not stuck)

NEFT is the rail that breaks people’s intuition. It is not instant. Since December 2019 it runs 24×7×365, but it settles in half-hourly batches — banks pass transactions to RBI, which processes them in batches, so your money can take 30 minutes to a couple of hours to land. A NEFT payout that’s been “pending” for 45 minutes is doing exactly what NEFT does. The hard rule: don’t escalate a NEFT payout inside the first two hours. NEFT has no upper limit, which is why some apps use it for large bank-transfer payouts — at the cost of batch-window timing.

RTGS — real-time, but only for big money

RTGS settles transactions in real time, one by one, and has been available 24×7×365 since 14 December 2020. Its catch is a floor: the minimum RTGS transfer is ₹2 lakh, with no maximum. Most card-game payouts never touch RTGS because they’re under the floor, but if you’re recovering a very large balance via bank transfer, RTGS is the fastest rail for that size — and being 24×7 now, even a weekend high-value transfer settles immediately.

The rail cheat-sheet for predicting your time: UPI = seconds, IMPS = instant up to ₹5 lakh, NEFT = 30 min to 2 hours (batches), RTGS = real-time but only above ₹2 lakh. If your payout is small it almost certainly rode UPI, so “instant” is the right expectation and anything past a few hours is worth checking. If it’s a large bank transfer, NEFT batch timing makes a couple of hours completely normal.

The UPI success path, second by second

It’s worth understanding why UPI can be so fast, because it explains both the speed and the rare failures. On a successful UPI payout, the app’s payment partner sends a credit instruction through NPCI to your bank, your bank posts the credit, and a confirmation flows back — all in a few seconds. There’s no batch, no business-hours window, no human. That’s the path the word “instant” describes, and on a clean repeat payout it’s the path you almost always get. The reason it occasionally takes minutes instead of seconds is queueing at the app’s payout partner (lots of payouts firing at once) or a momentary slowdown at your bank, neither of which is a problem — they resolve themselves. So a UPI payout that takes 90 seconds instead of 5 is not “stuck”; it’s just a slightly busy moment on an instant rail.

The UPI failure path is NOT instant — and that’s the trap

Here’s the asymmetry that catches people out: “UPI is instant” is true only for the success path. When a UPI credit fails — your bank was momentarily down, the handle didn’t resolve, a timeout — the transaction doesn’t reverse the instant the screen says “failed.” Instead it sits in a deemed-failed / pending state and is reconciled on a cycle, which is why a failed payout can hang in limbo for up to a day before it bounces back. The rule that governs the bounce-back is the RBI T+1 auto-reversal: the system is already obligated to return your money, usually within one working day, automatically. So a UPI payout that shows “failed” is not lost — it’s on the slowest leg of an otherwise instant rail, and the clock on it is T+1, not “right now.” That distinction is the difference between panicking on hour one and correctly waiting through T+1, which is exactly what the dispute guide at /fix/teen-patti-upi-withdrawal walks through.

Why a “paid” payout can still owe you a UTR trace

The cruelest timing case is the “paid but not received” one, because the app’s status is ahead of reality. The app marks the withdrawal “completed,” sometimes with a UTR, but the credit never posted at your bank — usually because the payout went to a stale or dead handle (you changed banks, closed the linked account, or the handle simply won’t resolve anymore). The rail genuinely tried; it just credited an address that no longer exists. The timing fix here is not “wait” — waiting won’t conjure the money onto a dead handle. It’s to grab the UTR, ask your bank to trace it, confirm there’s no credit against it, then update your withdrawal method to a live account and ask support to re-issue. The original UTR is your evidence the first attempt fired and failed. Capture it on Day 0, because once a payout ages out of the app’s quick view, digging the UTR back out is far harder.

What makes a payout fast vs slow: the seven timing factors

Two players withdraw ₹2,000 from the same app on the same day and one gets it in 40 seconds while the other waits 18 hours. The difference is never random — it’s a stack of seven factors, each of which adds or removes time. Here’s how to read your own situation against them.

Factor 1 — Amount thresholds

Small payouts auto-approve; large ones don’t. Most apps push a clean payout under a few thousand rupees straight to UPI without a human in the loop. Above an internal threshold — which apps don’t publish but is often in the low tens of thousands — the request routes to manual review, adding hours. A round number (₹50,000 exactly, ₹1,00,000 exactly) is doubly likely to be flagged, because round-number pulls are a fraud signal. If speed matters and you’re near a threshold, a slightly smaller, non-round amount frequently clears faster than a big round one.

Factor 2 — First withdrawal vs repeat

This is the biggest single swing. Your first-ever payout from an account carries the full KYC review (clock 2) plus an extra layer of fraud scrutiny — apps run a stricter manual check on a first payout, even a clean ₹100 test, before they trust the account. A first withdrawal taking far longer than later ones is normal, not a red flag. Every subsequent payout skips most of that, which is why your second withdrawal often lands in seconds when your first took a day.

Factor 3 — KYC completeness and name matching

A payout where the bank/UPI name matches the PAN exactly sails through. A payout where it doesn’t — “RAHUL K” on the handle, “Rahul Kumar” on the PAN — gets parked because the risk engine can’t auto-match the names. This is the single most common silent stall, and it converts a would-be 40-second payout into a multi-day manual-review wait. Completeness matters too: a blurry document or a pending Aadhaar verification holds clock 2 open.

Factor 4 — Account trust and risk flags

The fraud system scores your account every time. A brand-new account, a sudden large win, a duplicate-device or duplicate-IP signal, bonus-abuse patterns, or multi-accounting all add risk-review time. These holds can look identical to a normal delay from the outside; the tell is a support reply mentioning “verification,” “review,” or “security.” A boring, consistent account gets the fast lane; an “interesting” one gets the queue.

Factor 5 — Time of day and batch windows

The rail is 24×7, but the app’s payout processing isn’t always. Some operators batch their manual approvals during business hours, so a payout requested at 11 PM may not get human eyes until morning. On the bank side, a NEFT payout’s timing depends entirely on which half-hourly batch it catches — request it one minute after a batch closes and you wait the full ~30 minutes for the next. UPI and IMPS ignore time of day; NEFT and any manual-review step do not.

Factor 6 — Weekend and holiday effects

Here’s a myth worth killing: UPI, IMPS, NEFT and RTGS all run on weekends and bank holidays — UPI and IMPS 24×7×365, NEFT 24×7×365 since 2019, RTGS 24×7×365 since December 2020. So the rail never takes a weekend off. What can lag on a weekend is the app’s manual-review staffing and, occasionally, a receiving bank’s internal posting. So a clean auto-approved UPI payout is just as fast on Sunday as on Wednesday, but a payout that needs a human at the operator may sit until Monday.

Factor 7 — The receiving bank and beneficiary health

Clock 4 is yours, not the app’s. A receiving bank that’s temporarily down, a UPI handle you’ve since abandoned (you changed banks, closed the linked account, deleted the app), or a daily-limit cap on your receiving account can all stall a credit the app already sent. A “paid” payout that never lands is very often a dead beneficiary address — the rail tried to credit a handle that no longer resolves.

The fast-vs-slow formula: a payout is fast when it’s a small, non-round, repeat amount from a KYC-clean, trusted, low-risk account to a live UPI handle on an instant rail. It’s slow when any of those flips — big or round amount, first withdrawal, name mismatch, flagged account, manual-review hour, NEFT batch, or a stale beneficiary. Count how many of your factors are on the slow side; that’s your realistic wait.

Worked timeline 1 — the fast case (clean repeat UPI)

Picture a player making their fifth withdrawal: ₹1,840 (small, non-round), UPI, KYC already done and name-matched, no risk flags, requested at 9 PM on a Saturday. Clock 1 (app review) auto-approves in a second or two because the account is trusted and the amount is small. Clock 2 (KYC) is zero — already paid on earlier payouts. Clock 3 (UPI rail) fires in a few seconds. Clock 4 (bank credit) posts instantly, because UPI and the receiving bank are both up. Total: under a minute, on a weekend night, exactly as the “instant” claim promises. Every assumption lined up on the fast side.

Worked timeline 2 — the slow-but-normal case (first withdrawal, bank transfer)

Now the opposite stack: a player’s first-ever withdrawal, ₹50,000 (large and round), chosen as a bank transfer, with a UPI/PAN name they’re not sure matches, requested at 11 PM on a Sunday. Clock 1 routes to manual review because it’s a first payout, large, and round — a triple flag. Clock 2 runs the full KYC check, and if the name mismatches, it parks until a human resolves it. Even after approval, clock 3 rides NEFT or IMPS, and if NEFT, it waits for the next half-hourly batch; the operator’s manual approval may not happen until Monday business hours. Realistic total: 24–48 hours, possibly into Monday. Nothing here is “stuck” — every clock is just running its slow path, and the player who knows that won’t waste a frantic Sunday escalating a payout that’s behaving normally.

Worked timeline 3 — the genuinely stuck case (debited but not credited)

Third stack: a repeat ₹3,000 UPI payout that shows “failed” but the money left the wallet. Clocks 1, 2 and 3 all passed — the app approved it, KYC was clean, the rail fired — but clock 4 failed at the bank credit. This is the debited-but-not-credited state. The rule clock now governs: it must auto-reverse by T+1, and if it doesn’t, the bank owes ₹100/day after that. So the correct timeline is: note the UTR, wait through T+1, and only if it’s still missing on T+1 do you raise the UDIR dispute and claim compensation. This is the one case where the “stuck” state is actually the most protected, because the refund is rule-mandated — the steps are at /fix/teen-patti-upi-withdrawal.

How to predict YOUR withdrawal time in five questions

You don’t need to guess. Answer these five questions about your specific payout and you can estimate its window before the spinner even resolves.

1. Is this your first withdrawal on this account? If yes, add the KYC clock — budget hours up to 24 hours and treat anything under that as normal. If no, KYC is already paid; the rest of the clocks dominate.
2. Which rail will it ride? Small amount → almost certainly UPI → expect seconds to a few hours. Large amount or bank transfer → IMPS (instant up to ₹5 lakh) or NEFT (30 min – 2 hours, batches). If you can choose the method in-app, UPI is the fastest for small payouts.
3. Does your bank/UPI name match your PAN exactly? If yes, the name won’t park it. If you’re not sure, that uncertainty is the risk — a mismatch is the top silent stall, so verify it before blaming the app.
4. Is the amount large or a round number? A big or round-number pull invites manual review and adds hours. A smaller, non-round amount tends to auto-approve. Splitting a large pull under a likely threshold can be faster overall.
5. What time and day is it, and does the payout need a human? A clean auto-approved UPI payout ignores time and day entirely. A payout that needs manual review at the operator may wait for business hours, and a NEFT payout waits for its next batch.

Stack the answers: a repeat, small, non-round UPI payout from a name-matched account at any time is your seconds-to-minutes case. A first, large, round-number bank transfer requested late on a weekend from an account with a name mismatch is your “could be a day or two, and that’s still not necessarily broken” case. Knowing which one you are stops you from escalating too early — which the hub’s ladder at /fix/3-patti-withdrawal explicitly warns wastes days.

Realistic benchmarks vs operator marketing claims

“Instant withdrawal” is on every app’s landing page. It is true for exactly one row of the matrix — the clean repeat UPI payout — and misleading for the rest. Here is the honest benchmark set, so you can hold an operator’s claim against what the rails actually permit.

What “instant” really means

“Instant” describes the successful UPI path on an already-trusted account. On that path, the four clocks are all near-zero, so the payout really does land in seconds. The marketing claim quietly assumes: not your first withdrawal, KYC already clean, small non-round amount, no risk flag, live handle. Strip away any one of those assumptions and “instant” becomes “minutes to hours” or “up to a day.” The claim isn’t a lie — it’s the best-case row presented as the whole table.

Operator-stated TATs, decoded

The most specific operator claim in this space is RummyCircle’s published UPI 2–4 hours, bank transfer 24–48 hours — and notice it’s not “instant.” That’s a more honest benchmark than “instant” because it’s method-split and gives a range. Teen Patti Gold and Master typically state “UPI minutes to a few hours, bank up to 3 working days.” Read these as: UPI fast lane, bank slow lane, first payout slower than the stated window. When an app says “instant” with no method split and no first-payout caveat, mentally translate it to “instant on the best path, hours-to-a-day otherwise.”

The benchmark table you should actually plan around

The discipline this table buys you: you stop treating “it’s been 3 hours and the app said instant” as a problem on a first withdrawal (it isn’t — you’re inside the window), and you stop treating “it’s been 30 hours” as normal on a clean repeat UPI payout (it isn’t — that’s escalation time). The threshold between “still normal” and “now escalate” is the only number that matters, and it’s different for every row.

The “debited but not credited” benchmark is the one with teeth

Every other benchmark above is industry behaviour you should read as an estimate. The debited-but-not-credited benchmark is rule-mandated: under RBI’s failed-transaction circular, a UPI payout debited but not credited must be auto-reversed by T+1, with ₹100/day compensation after that. So that’s the one row where the timing isn’t a soft expectation — it’s an entitlement. The screen-by-screen UDIR dispute for this exact case is at /fix/teen-patti-upi-withdrawal, and the failed-payout mechanics are covered from the hub at /fix/3-patti-withdrawal.

The benchmark bottom line: trust the rule-based timings (T+1 auto-reversal, NEFT half-hourly batches, IMPS instant) as facts, and treat the app-stated timings as upper-bound promises on the best path. “Instant” is real for one row and aspirational for the rest. Plan from the row you’re actually in.

The receiving-bank side: the clock you control (and its caps)

Three of the four clocks belong to the app and the rail. Clock 4 — the bank credit — is partly yours, and it has its own timing quirks that can make an otherwise-fast payout feel slow even though the app did everything right.

Your receiving account’s own daily limit

UPI’s ₹1 lakh/day cap counts your outgoing transactions, but your receiving account can have its own posting behaviour. A freshly created UPI handle is capped at ₹5,000 for the first 24 hours of its life — auto-lifting after 24 hours on Android (72 hours on iPhone) — so if you set up a brand-new UPI ID specifically to receive a payout, that new-handle friction can stall a larger credit. The fix is timing, not fighting: receive into an established handle, or wait out the new-handle window. This is a clock-4 cause that looks exactly like an app problem but isn’t.

A receiving bank that’s momentarily down

If your bank’s systems are briefly unavailable when the credit instruction arrives, the credit can’t post and the transaction slips toward the deemed-failed state — which then rides the T+1 reconciliation clock. There’s nothing the app can do about your bank being down; this resolves on the rail’s own cycle. The tell is that the app shows “paid/success” while your bank shows nothing, and the UTR exists. That’s a clock-4 trace job, not an app dispute.

A dead or changed beneficiary handle

The most common self-inflicted clock-4 delay: the payout fires at a handle you no longer use. You changed banks, closed the linked account, or deleted the app that hosted the handle. The rail credits a dead address, the credit fails, and you’re left with a “paid” status and no money. The timing reality is blunt — waiting does nothing, because the address is gone. Update your withdrawal method to a live account, ask support to re-issue against the original UTR, and the new attempt rides the normal instant rail.

Why clock 4 is the best-protected delay despite feeling the worst

It feels awful — the app says you were paid, your bank disagrees — but clock 4 carries the strongest consumer rule of all four. A debited-but-not-credited UPI payout must auto-reverse by T+1, with ₹100/day after, and Paytm-destination payouts carry a stated 24–72 hour auto-refund window for the same failure. So the worst-feeling clock has the firmest deadline. The instinct to panic is exactly backwards: a clock-4 failure is the one stuck state where the rules are explicitly on your side, and the hub’s failed-payout walkthrough at /fix/3-patti-withdrawal shows how to invoke them.

Clock 4 in one line: it’s the one clock you partly own, and its delays — new-handle caps, a down bank, a dead beneficiary — feel like app theft but are usually a rail reconciliation governed by T+1 with ₹100/day protection. Trace the UTR, fix the handle if it’s dead, and let the rule clock run.

Deposit timing vs withdrawal timing: don’t confuse the two clocks

A surprising share of “my money is stuck” reports are actually about the deposit side, not the withdrawal side, and the two run on completely different timing logic. Keeping them separate stops you from escalating the wrong thing.

Deposits are near-instant; the confusion is the GST cut

A deposit into a card-game app is a near-instant UPI debit from you to the app — there’s no review queue, no KYC gate on the way in. So a deposit almost never has a “timing” problem. What people misread as a deposit delay is the 28% GST on deposits (in force since 1 October 2023), which means ₹100 deposited may buy fewer playable chips than expected. That’s not money in transit — it’s a tax that landed instantly. The withdrawal side has the opposite shape: slow-ish on the way out (the four clocks), with a 30% TDS on net winnings rather than a deposit-side GST.

Why deposits clear faster than withdrawals

The asymmetry is structural. Money flowing into a gaming app needs no anti-fraud release, no payout queue, no beneficiary-credit step — it’s a simple instant pull. Money flowing out must pass app review, KYC, the rail, and a bank credit, each of which can add time. So “my deposit was instant but my withdrawal is taking hours” isn’t the app being unfair — it’s that depositing and withdrawing are genuinely different operations with different clocks. The withdrawal is the one with all four gates.

When a “deposit not credited” really is a timing issue

Occasionally a deposit does stall — a UPI debit leaves your account but the app’s wallet doesn’t reflect it. That’s the same debited-but-not-credited rail failure as on the withdrawal side, just in the other direction, and it carries the same T+1 auto-reversal protection. So if your deposit money left your bank but never appeared as chips, don’t keep depositing — note the UTR, wait through T+1, and dispute it like any failed UPI transaction. The mechanics match the withdrawal-side failed-payout guide at /fix/teen-patti-upi-withdrawal.

Deposit vs withdrawal timing: deposits are instant (the “shortfall” you see is 28% GST, not a delay), while withdrawals run four clocks (with 30% TDS on net winnings, not GST). A genuinely stalled deposit is the same T+1-protected rail failure as a stalled withdrawal — same fix, opposite direction. Don’t escalate a GST cut as a stuck payout.

The post-PROGA wind-down: how long recovery actually takes

For a large share of 2026 readers the question isn’t “why is my live payout slow” — it’s “how long until I get my stranded balance out of an app that stopped taking bets.” This runs on a related but distinct clock, and it’s worth setting expectations honestly.

What changed, and what didn’t

PROGA prohibited online money games, and the major operators suspended cash play from late August 2025. Crucially, banks and payment intermediaries were instructed to keep processing withdrawals so users could recover existing balances. So the rails — UPI, IMPS, NEFT, RTGS — and the RBI/NPCI protections still fully apply to a recovery payout. What changed is that you can no longer deposit, and the operator’s payout processing may be slower than it was when the app was a live, staffed business.

The recovery clock vs the live-app clock

A recovery payout has the same four clocks, but two of them tend to run longer:

• Clock 1 (app review) can be slower because a wound-down operator runs leaner support and may batch recovery payouts rather than auto-approving them in real time. Budget more patience here than you would for a live app.
• Clock 2 (KYC) is often re-checked on recovery, even if you withdrew fine before — so a name mismatch that never mattered can suddenly stall a recovery. Get your KYC name matching your PAN exactly before you request the recovery.
• Clocks 3 and 4 (the rails and bank credit) are unchanged — once the operator releases the money, it rides the same instant/batch rails with the same T+1 protection on failure.

Realistic recovery timing

There’s no universal published TAT for recovery because each operator wound down on its own schedule, but the realistic shape is: standard rail timing once the operator approves and KYC is clean, with clock 1 potentially adding more than it would on a live app. Expect the same 30% TDS on net winnings on the recovery payout — recovery is not tax-free. The operator-specific recovery timing and flow for one of the biggest is at /fix/junglee-rummy-withdrawal, and if the recovery lands in a Paytm handle, the pending-payout specifics are at /fix/paytm-withdrawal-pending-gaming.

The one rule that overrides all recovery timing

Never deposit again to “speed up” or “unlock” a recovery. On a money game that deposit is now illegal, and it does nothing for your timing — a recovery payout is gated by the operator’s review and your KYC, not by a fresh deposit. Any prompt to deposit “to release your withdrawal” on a discontinued app is a theft pattern; the hub’s red-flags section at /fix/3-patti-withdrawal covers it.

Recovery timing in one line: the rails and the T+1 protection are unchanged, so a released recovery payout still lands on normal rail timing, but the operator’s approval step (clock 1) can run slower on a wound-down app, and KYC is often re-checked (clock 2) — so match your name to your PAN, expect the 30% TDS, and never re-deposit.

Withdrawal time by amount band: the tiers that actually matter

The single most predictable timing variable is how much you’re pulling, because the amount decides which rail you ride and whether a human gets involved. Here’s the practical tier map.

Small (under ~₹5,000): the instant tier

A payout under roughly ₹5,000 is the canonical “instant” case. It almost always rides UPI, sits well under the daily cap, and is small enough that most apps auto-approve it without manual review. On a clean repeat account, this is your seconds-to-minutes payout. The only thing that slows a small payout is a first withdrawal (KYC clock) or a name mismatch — the amount itself isn’t the issue.

Medium (~₹5,000–₹50,000): the maybe-manual tier

Here the amount starts mattering. A payout in this band may still ride UPI (under the ₹1 lakh/day cap) but is more likely to trip an internal review threshold, especially toward the top of the band or on a round number. Realistic timing: minutes to a few hours if auto-approved, up to 24 hours if it routes to manual review. If you’re near the top of this band and want speed, a non-round amount tends to clear faster than a round one.

Large (~₹50,000–₹1 lakh): the review-likely tier

At this size, manual review is common, and the payout may switch from UPI to IMPS (instant, up to ₹5 lakh) or NEFT (batched). Timing: a few hours to 24–48 hours, dominated by the operator’s approval step more than the rail. A round ₹1,00,000 pull is the most-flagged shape there is — expect scrutiny, and budget into the next business day if you request it off-hours.

Very large (above ₹2 lakh): the RTGS-eligible tier

Above ₹2 lakh a bank transfer can use RTGS, which is real-time and 24×7 — so ironically a very large bank transfer can settle faster on the rail than a mid-size NEFT one, once the operator approves it. The bottleneck at this size is clock 1: a large recovery or payout gets the most careful review, so the rail speed is rarely the constraint. Split-vs-single is a real choice here — some players split a very large pull to stay under per-transaction caps and reduce flagging, at the cost of more transactions.

Amount-band timing in one line: under ₹5,000 = instant tier (auto-approve, UPI), ₹5k–₹50k = maybe-manual, ₹50k–₹1L = review-likely (IMPS/NEFT), above ₹2L = RTGS-eligible (real-time rail, but heaviest review). The rail gets faster at the very top (RTGS) while the review gets slower — so big payouts wait on the operator, not the rail.

Tracking your payout status in real time

You don’t have to refresh the app and hope. There are concrete status signals that tell you where your payout is and whether it’s moving, which lets you wait intelligently instead of anxiously.

Read the app’s status text precisely

“Processing / pending / under review” with no UTR means clock 1 or 2 — still inside the app. “Paid / success / completed” with a UTR means it reached the rail; check your bank, and if nothing’s there, it’s a clock-4 trace. “Failed” with money gone means a clock-4 rail failure on the T+1 clock. The status words are not decoration — they map directly to a clock and therefore to a wait time.

Use the bank SMS and statement as the source of truth

Your bank’s own SMS alert or statement entry is the authoritative confirmation a credit actually posted — not the app’s status, which can run ahead of reality. If the app says “paid” but no bank SMS arrived and no statement line exists, the credit didn’t post, and you’re in the “paid but not received” case that needs the UTR trace. Treat the bank record, not the app screen, as the truth about whether you’ve been paid.

Capture the UTR the moment it appears

The UTR (12-digit reference, labelled differently in each UPI app) is the thread that ties a debit to a credit. It appears in the app’s payout record and in your UPI app’s transaction history. Grab it on Day 0, because a failed transaction ages out of the quick view and a bank can’t trace a credit you can’t name. If your payout landed in Paytm, the per-app UTR location and the pending-status walkthrough are at /fix/paytm-withdrawal-pending-gaming.

Real-time tracking in one line: the status text tells you the clock, the UTR is the thread, and the bank SMS/statement is the truth. Read all three and you’ll know whether to keep waiting or to start the trace — no guessing, no refresh-spamming.

Choosing the fastest method for your payout

When an app lets you pick the withdrawal method, the choice changes your timing, so it’s worth a deliberate decision rather than tapping the default.

For small payouts, choose UPI

For anything under the ₹1 lakh daily cap, UPI is the fastest option on the menu — seconds on a clean account, 24×7, no batch. If the app offers UPI and bank transfer for the same small amount, UPI wins on time almost every time. The only reason to skip UPI is a handle problem (a dead or new-and-capped handle), in which case a verified bank account is the safer choice even if it’s a touch slower.

For large payouts, weigh IMPS against NEFT

Above the comfortable UPI range, the choice is usually IMPS versus NEFT, and on timing they’re not equal. IMPS is instant up to ₹5 lakh; NEFT runs half-hourly batches and takes 30 minutes to 2 hours. So if both are offered for a large amount, IMPS is the faster rail — pick it when speed matters and the amount fits its ₹5 lakh ceiling. NEFT’s only timing advantage is that it has no upper limit, which matters above ₹5 lakh.

Match the destination to a live, name-matched account

The fastest method still fails if it points at the wrong place. Whatever rail you choose, send to an account whose name matches your PAN and which is active — that’s what keeps clocks 2 and 4 near-zero. A name-matched, established destination on UPI is the single fastest, lowest-risk combination, and it’s the one to use for every routine payout.

Method choice in one line: small → UPI (seconds), large under ₹5 lakh → IMPS (instant) over NEFT (batched), above ₹5 lakh → NEFT (no cap, but 30 min–2 hours) — always into a live, name-matched account so clocks 2 and 4 stay at zero.

When your withdrawal time crosses from “normal” into “stuck”

Predicting your time is half the job; the other half is knowing the exact moment to stop waiting. Each rail and scenario has a different “now it’s actually stuck” threshold, and crossing it is your cue to start the paper trail that the hub’s escalation ladder at /fix/3-patti-withdrawal walks step by step.

The “still normal” windows

• Repeat UPI payout: normal up to a few hours; watch it past 4–24 hours.
• First-ever withdrawal: normal up to 24 hours; watch it past 24–48 hours.
• Bank/IMPS payout: normal up to 24 hours; watch it past 24–48 hours.
• NEFT payout: normal up to 2 hours (batches); watch it past 24 hours.
• UPI debited-but-not-credited: normal until T+1; after T+1 it’s overdue and you’re owed ₹100/day.

The “now it’s stuck” triggers

You’ve crossed into stuck when: a clean repeat UPI payout passes 24 hours; a first withdrawal passes 48 hours with no support reply; a bank/NEFT/IMPS payout passes 48 hours; or a debited-but-not-credited UPI payout is still missing after T+1. At that point the clock you’re waiting on isn’t “normal slow” anymore — it’s a problem with a named fix.

What to do the moment you cross the line

Don’t escalate early (support will just tell you to wait) and don’t escalate late (you can blow past a rail’s TAT and lose the easy refund). The instant you cross your threshold:

1. Freeze the evidence — screenshot the request, status, amount, timestamp, and your balance before/after.
2. Capture the UTR — the 12-digit reference, the moment it appears; you can’t trace a “paid” payout without it.
3. Raise the in-app ticket and get a complaint ID in writing.

From there the type of stuck decides the door: a failed/debited UPI payout is the T+1 case with the UDIR dispute at /fix/teen-patti-upi-withdrawal; a payout sitting in the app’s queue is an app-support case; a Paytm-destination pending payout has its own walkthrough at /fix/paytm-withdrawal-pending-gaming; and a wind-down recovery follows /fix/junglee-rummy-withdrawal. The full Day-0-to-30 escalation ladder lives on the hub at /fix/3-patti-withdrawal — this page’s job is just to tell you when you’ve earned the right to climb it.

The threshold rule in one line: a payout is “slow but normal” until it crosses its rail’s window (24h for repeat UPI, 48h for first/bank, T+1 for debited-but-not-credited), and “stuck” the moment it passes it. Cross the line → freeze evidence, grab the UTR, open the ticket. That’s the handoff from this timing page to the hub’s escalation ladder.

Related fixes (go deeper on your exact case)

This page is the deep timing reference for the withdrawal cluster. For the action steps that match your symptom, these go further:

• The full escalation ladder + per-app reality table → 3 Patti withdrawal hub — what to do when a payout crosses from slow into stuck, Day 0 to Day 30.
• UPI payout failed / pending → Teen Patti UPI withdrawal fix — the exact NPCI UDIR dispute screens and where the UTR hides.
• Payout landed in Paytm and is pending → Paytm withdrawal pending (gaming) — where the money sits and the 24–72h refund clock.
• Recovering a balance from a discontinued cash app → Junglee Rummy withdrawal — the wind-down recovery flow and its timing.

FAQ

1. How long does a teen patti withdrawal take? A clean repeat UPI payout from a legal app lands in seconds to a few hours, because the app auto-approves it and UPI is near-instant. A first-ever withdrawal adds the KYC review clock, so budget hours up to 24 hours. A bank transfer is the slow lane at 24–48 hours. So there’s no single number — your time is whichever clock is slow that day, and “instant” only describes the best-case repeat-UPI row.

2. How long does a rummy withdrawal take? On a live legal rummy app, RummyCircle’s own stated TAT was UPI 2–4 hours and bank transfer 24–48 hours on business days — a more honest benchmark than “instant.” Since cash rummy is discontinued under PROGA, most 2026 rummy withdrawals are wind-down recovery payouts, which run on standard rail timing once KYC is clean but may have a slower operator-approval step. Expect the same 30% TDS on the recovery payout.

3. Why is my withdrawal taking so long when the app says “instant”? Because “instant” describes only the clean repeat UPI path. Your payout is probably sitting at one of four clocks: app review (manual review adds hours), KYC (a name mismatch can park it for a day or more), the rail (NEFT runs 30 min–2 hour batches), or the bank credit. Count how many slow factors apply to you — first withdrawal, large/round amount, name mismatch, manual-review hour — and that’s your realistic wait.

4. Which is the fastest withdrawal method — UPI, IMPS or NEFT? UPI is fastest for small payouts (seconds, cap ~₹1 lakh/day). IMPS is also instant and handles larger amounts up to ₹5 lakh per transaction. NEFT is the slowest of the three because it settles in half-hourly batches, taking 30 minutes to 2 hours — so a NEFT payout that takes an hour is normal, not stuck. For most card-game payouts, UPI is the fast lane.

5. Is a NEFT payout that’s been pending for an hour stuck? No. NEFT settles in half-hourly batches, so 30 minutes to 2 hours is completely normal — a transfer that just missed a batch waits for the next one. Don’t escalate a NEFT payout inside the first two hours. Only treat it as stuck if it passes 24 hours. NEFT has been 24×7×365 since December 2019, so weekends and nights don’t stop it.

6. Why was my first withdrawal so much slower than later ones? Your first-ever payout carries the full KYC review plus a stricter fraud check — apps run a tougher manual review on a first withdrawal, even a clean ₹100 test, before they trust the account. That’s why a first payout can take up to 24 hours while your second lands in seconds. A slow first withdrawal is normal, not a red flag by itself.

7. Do withdrawals work on weekends and bank holidays? The rails do — UPI and IMPS are 24×7×365, NEFT has been 24×7×365 since 2019, and RTGS since 14 December 2020. So a clean auto-approved UPI payout is just as fast on Sunday as on Wednesday. What can lag on a weekend is the operator’s manual-review staffing — a payout that needs a human may wait until Monday — and occasionally a receiving bank’s internal posting.

8. What makes one payout fast and another slow on the same app? Seven factors: amount (small and non-round auto-approves; large or round-number routes to manual review), first vs repeat (first is slower), KYC name match (a mismatch parks it), account risk flags, time of day (manual review may wait for business hours), rail (UPI fast, NEFT batched), and receiving-bank health. The more factors on the slow side, the longer your wait.

9. How do I predict my own withdrawal time? Answer five questions: Is it your first withdrawal (add the KYC clock)? Which rail — small means UPI (seconds–hours), large means IMPS/NEFT? Does your name match your PAN? Is the amount large or round (manual review)? What time/day, and does it need a human? Stack the answers — a small, non-round, repeat UPI payout from a name-matched account is your seconds case.

10. My withdrawal shows “paid” but the money never arrived — how long before I act? Get the UTR (12-digit reference) and give it the rest of the day on UPI. If it’s still missing, it’s likely a debited-but-not-credited case, which RBI rules require to be auto-reversed by T+1, with ₹100/day compensation after that. A “paid” payout that never lands is often a dead UPI handle (you changed banks or closed the account) — update to a live account and ask support to re-issue with the original UTR.

11. How long does a UPI debited-but-not-credited payout take to come back? By rule, it must be auto-reversed by T+1 (the day after the transaction) under RBI’s failed-transaction circular. If it isn’t, your bank owes you ₹100 per day of delay beyond T+1, credited automatically. Paytm’s guidance similarly says a failed-but-debited UPI is typically auto-refunded within 24–72 hours. This is the one timing that’s a legal entitlement, not an estimate — the dispute steps are at /fix/teen-patti-upi-withdrawal.

12. Does the payout amount affect how long it takes? Yes. A small, non-round payout usually auto-approves and rides UPI in seconds. A large payout often routes to manual review (adding hours), and a round number (₹50,000 exactly) is extra likely to be flagged because round pulls are a fraud signal. If speed matters, a slightly smaller, non-round amount frequently clears faster than a big round one. Above ₹2 lakh a bank transfer may use RTGS, which is real-time.

13. How long does a wind-down recovery from a discontinued app take? There’s no single published TAT, but the realistic shape is standard rail timing once the operator approves and your KYC is clean — the rails and the T+1 failure protection are unchanged. The slower part is the operator’s approval step (clock 1), which can lag on a leaner wound-down business, and KYC is often re-checked (clock 2). Match your name to your PAN, expect the 30% TDS, and never re-deposit — that’s illegal and doesn’t speed anything up. Details at /fix/junglee-rummy-withdrawal.

14. At what point is my withdrawal officially “stuck” and not just slow? Cross the threshold for your row: a clean repeat UPI payout past 24 hours; a first withdrawal past 48 hours with no reply; a bank/NEFT/IMPS payout past 48 hours; or a debited-but-not-credited UPI payout still missing after T+1. The instant you cross it: screenshot everything, capture the UTR, raise the in-app ticket, and start the escalation ladder on the hub at /fix/3-patti-withdrawal.

15. Why did my payout arrive smaller than I withdrew — is that a delay? No, it’s almost always tax, not a timing problem. Legal apps deduct 30% TDS on net winnings under Section 194BA before paying, with no minimum threshold since April 2023. So a ₹25,000 withdrawal with ₹15,000 of net winnings arrives as ₹20,500, with ₹4,500 remitted against your PAN and creditable when you file. The full worked math is on the hub at /fix/3-patti-withdrawal.

Sources & method. Withdrawal-time numbers on this page are built from primary RBI/NPCI rail rules and named operator statements — not personal payout tests. Rail timings: UPI and IMPS run 24×7×365 (IMPS up to ₹5 lakh/transaction); NEFT settles in half-hourly batches, 24×7×365 since December 2019 (Razorpay NEFT timings, IMPS vs NEFT vs RTGS); RTGS is real-time, 24×7×365 since 14 Dec 2020, minimum ₹2 lakh, no maximum (Business Today, 9 Dec 2020, ICICI NEFT/RTGS/IMPS); UPI standard cap ₹1 lakh/day and a ₹5,000 first-24h cap on new registrations (Razorpay UPI limits 2026, Google Pay UPI limits). Failed-transaction protection: a debited-but-not-credited UPI payout auto-reverses by T+1 with ₹100/day after, per RBI Circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019), processed via NPCI UDIR; Paytm’s failed-but-debited refund window is 24–72 hours (Paytm support). Operator TATs: RummyCircle withdraw-cash help (UPI ~2–4h, bank ~24–48h) and Junglee Rummy deposit/withdrawal. Legality: the Promotion and Regulation of Online Gaming Act, 2025, with cash formats suspended from late August 2025 and banks instructed to keep processing recovery withdrawals (Mondaq). TDS: 30% on net winnings under Section 194BA / Rule 133 / CBDT Circular 5/2023 at incometaxindia.gov.in. This page is information, not legal or financial advice — verify each timing against your operator’s current Terms and your bank’s UPI dispute policy.