Ludo Money Withdrawal: Get Cash Out of Real-Money Ludo Apps

The 30-second answer

TL;DR: A ludo money withdrawal sends your winnings to UPI or bank after PAN/Aadhaar KYC. Real-money ludo is banned under PROGA since 1 May 2026, so Zupee and WinZO kept withdrawals open for existing balances while most “ludo earning” clones never pay. Expect 30% TDS; there is no statutory refund window.

A ludo money withdrawal moves your winnings from a real-money ludo app to your UPI ID or bank account, and a legal app only releases it after PAN + Aadhaar KYC. The hard part is that real-money ludo is now banned in India under PROGA, in force 1 May 2026. Legit operators like Zupee and WinZO stopped cash ludo but kept withdrawals open so users could pull existing balances out; the hundreds of “ludo earning” clones mostly never pay. Expect a 30% TDS cut on net winnings. If your money is stuck, start with the refund and dispute recovery hub — there is no 180-day statutory refund window, so recovery runs on RBI rail rules plus the operator-grievance-to-OGAI ladder.

Editor’s verdict, up front. “Ludo money withdrawal” is now two completely different problems wearing the same search term, and the first thing to do is figure out which one you have. Problem one: you have a real balance on a legitimate app (Zupee, WinZO, MPL, Gameberry-built titles) that wound down cash play after PROGA, and you need to get that existing balance out before the operator finishes its wind-down. Problem two: you downloaded a “ludo earning app” — one of the hundreds of clones promising ₹500 a day — and it’s refusing to let you cash out. Problem one is a recoverable wind-down with real rail protections behind it. Problem two is, far more often than not, a designed-to-never-pay app where your realistic move is to cut losses, report it, and chase only any money that left your bank on the rail. This page maps both, with the exact KYC/tax math, the dispute ladder, copy-paste templates, and a blunt scam-clone checklist.

2026 reality you must read first. The legal ground shifted hard. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) received Presidential assent on 22 August 2025 and prohibits all online money games — skill or chance — where you stake money for a return. The operating Rules came into force on 1 May 2026. Real-money ludo squarely falls inside that ban, so India’s biggest ludo operators suspended their cash formats from late August 2025. The good news: the leading apps paused deposits but kept withdrawals open so users could recover existing balances. The thing nobody tells you: a draft version of the rules floated a 180-day window for operators to repay balances — but that 180-day refund rule was dropped from the final notified Rules 2026. There is no statutory refund clock now. Recovery instead runs on the existing RBI/NPCI rail rules, ordinary consumer and contract law, and the operator-grievance-to-OGAI escalation ladder. The whole guide reads two ways — legit-app balance recovery, and scam-clone damage control — and we flag which is which throughout.

What a ludo money withdrawal actually is

When people search “ludo money withdrawal,” “ludo earning app withdrawal,” “ludo supreme withdrawal,” or “ludo paisa kaise nikale,” they’re describing one thing: getting real rupees — not in-game coins or a “loyalty score” — out of a ludo app and into a bank account. Be precise about the object, because most withdrawal confusion starts here.

A real-money ludo app holds your money in a wallet, and that wallet is made of three separate pots that players wrongly treat as one number:

• Deposit balance — money you added with your own UPI or card. Some apps let you withdraw an unused deposit; many force you to play it through first.
• Winnings balance — money you won at the ludo table or in a tournament. This is the pot that taxes apply to, and the pot that triggers KYC and a risk review on the way out.
• Bonus / cashback / “loyalty” balance — coins the app handed you (welcome bonus, referral credit, daily wheel, a “loyalty level”). This is almost never directly withdrawable. A huge share of “ludo withdrawal not working” complaints are players trying to cash out a locked bonus and reading the locked figure as theft.

A ludo withdrawal, then, is the app moving rupees from your winnings (and eligible deposit) pot to your registered UPI ID or bank account, after deducting any tax it is legally required to deduct. That payout travels over one of two rails:

• UPI — the instant rail run by NPCI. Most ludo payouts under a few thousand rupees go here.
• IMPS / bank transfer (NEFT in some flows) — used for larger amounts, or as a fallback when UPI to your handle fails.

Both rails are operated by banks and payment aggregators regulated by the Reserve Bank of India (RBI). That single fact is the foundation of everything below: once your payout is on the rail, it stops being a “ludo app problem” and becomes a payment-system problem with hard, RBI-mandated timelines and a real complaints authority behind it. That is your one piece of real leverage — and it survives even after the cash game itself is banned.

Why the three-pot split decides whether you get paid

A player who knows their ₹2,000 is an approved winnings payout already handed to UPI is in a completely different position from a player whose ₹2,000 is a loyalty/bonus figure the app never intended to release. The first has the RBI rulebook behind them. The second is arguing about an app’s terms, where they are far weaker. Before you escalate anything, open the app’s withdrawal screen (not the headline wallet number) and read the withdrawable figure — that one number tells you which fight you’re actually in.

The pot also fixes your tax math. Only the winnings pot is taxable under Section 194BA; a returned deposit is your own money coming back and is not “net winnings.” If your ludo payout came back smaller than expected, the first question is which pot it left from — a 30% cut on a winnings payout is tax, while a cut on a pure deposit return is a fee dispute worth raising. The worked examples later make that line exact.

Legit ludo app or scam clone? Sort this before anything else

This is the single most important section on the page, because the entire rest of your strategy forks here. There are roughly four tiers of “ludo app,” and your odds of getting paid drop off a cliff as you go down.

Tier 1 — Established operators that wound down cash play (real balances, real recovery)

These were licensed, KYC-enforcing, tax-deducting Indian operators with real funding and real corporate identities. After PROGA they suspended real-money play but kept withdrawals open:

• Zupee — the biggest real-money ludo name, valued around ₹4,900 crore. Zupee halted its paid games on 21 August 2025, paused deposits, and explicitly said withdrawals would continue so users could pull existing balances. It kept its free titles (Ludo Supreme, Ludo Turbo, Snakes & Ladders) running. Withdrawal services remained operational into 2026 even as the company cut roughly 370 jobs across two rounds.
• WinZO — suspended its real-money operations alongside the rest of the sector and repositioned as a free entertainment platform with 25 crore+ users. Note one sharp caveat below: the ED flagged restricted withdrawals on WinZO even before the ban.
• MPL (Mobile Premier League) — its ludo cash format was part of the sector-wide real-money shutdown.

For Tier 1, your problem is recovering an existing balance from an operator that’s still reachable. That’s the recoverable case, and the rail rules in this guide apply with full force. The Zupee-specific recovery flow has its own deep page: Zupee withdrawal recovery.

Tier 2 — Game-engine / social brands (mostly free, limited cash exposure)

• Ludo Supreme is Zupee’s flagship ludo format; post-ban it continues as a free title, so a “Ludo Supreme withdrawal” is really a Zupee balance question.
• Gameberry Labs’ Ludo Star and similar are largely social/free ludo with cosmetic purchases, not a cash-out app — there may be nothing to “withdraw” in the rupees sense at all. Players sometimes search “ludo star withdrawal” expecting cash that the product never offered.

For Tier 2, the honest answer is often “there is no real-money balance to withdraw” — confirm whether you ever actually had a withdrawable winnings pot before chasing a payout.

Tier 3 — “Ludo earning apps” promising ₹500/day (assume scam until proven otherwise)

Search “ludo earning app” and you’ll hit hundreds of near-identical apps — Ludo Cash, Ludo Win, Ludo365, Ludo League, and a churn of clones — promising “₹500 daily” or “instant withdrawal, no investment.” Independent reviews are brutal: many of these apps “will never pay you a single penny, even if you reach the minimum withdrawal limit”. The mechanics are deliberately rigged:

• The minimum withdrawal is set high (commonly ₹5,000), and your earnings mysteriously slow to ₹0.01 per spin the moment you near it — so you never quite reach the threshold.
• The developer makes money from ads you’re forced to watch, not from a real game economy. Every lost match and every wallet check shows an ad.
• They show fake withdrawal screenshots, use celebrity photos without permission, and sometimes allow a tiny first withdrawal to build trust before demanding a “membership fee” to unlock the rest.

If you’re on a Tier 3 app, the realistic verdict is harsh: you will probably not recover an in-app “balance” that was never real money to begin with. Pursue only money that left your bank (a deposit you paid for that the rail can trace), report the app, and stop feeding it. The shutdown-recovery hub covers the disappeared-operator version of this: recover balance from a shutdown app.

Tier 4 — Offshore / sideloaded / “mod” ludo APKs (worst odds)

Sideloaded “unlimited coins” or “mod” ludo APKs and offshore-hosted cash ludo sit entirely outside Indian regulation. A modified build voids the app’s own terms and can get your account and balance frozen with no recourse. Your RBI leverage here is near zero, and post-PROGA any cash play on these is illegal anyway.

The one-line sort: Tier 1 = recoverable wind-down (use the rail rules and the OGAI ladder). Tier 2 = often nothing to withdraw (it was free). Tier 3 and 4 = damage control (recover only rail-traceable money, report, walk away). Getting this sort right on day one saves you weeks of fighting the wrong door.

The post-PROGA reality: why there’s no 180-day refund clock

Here’s the piece most “ludo withdrawal” explainers get wrong, because they’re reading a draft rule that never made it into law.

When PROGA’s rules were being drafted, an early version floated a 180-day window: operators winding down would have had roughly six months to repay pending user balances, and remitting those balances wouldn’t count as “facilitating” a banned money game. Many trackers still quote that number. But that 180-day refund provision was dropped from the final notified Promotion and Regulation of Online Gaming Rules, 2026. There is no statutory refund window in the rules that actually came into force on 1 May 2026. (For the broader regulatory picture, the Mondaq decode of PROGA and the 2026 Rules is the cleanest primary-flavored summary.)

That changes your recovery strategy in three concrete ways:

• You can’t cite a “180-day rule” to an operator. It isn’t in the law. An operator returning your balance is doing so under ordinary contract and consumer-protection obligations (it owes you money it holds), plus the practical fact that remitting genuinely-owed pre-existing balances is treated as winding down, not as running a banned game.
• Your real leverage is the payment rail and the grievance ladder, not a gaming-specific deadline. If money left your bank and didn’t arrive, the RBI/NPCI failed-transaction rules force a refund (covered below). If the operator is holding an owed balance and stonewalling, the path is the operator’s grievance officer, then escalation to the Online Gaming Authority of India (OGAI).
• Time still matters, just not as a statutory clock. An operator mid-wind-down with layoffs is a fading counterparty. The sooner you complete KYC and request the withdrawal, the better your odds — not because a 180-day rule expires, but because the company itself may not be reachable forever.

The OGAI escalation rung is new — and it’s real

Under the 2026 Rules, an aggrieved end user who is dissatisfied with an operator’s grievance outcome can approach the Online Gaming Authority of India within 30 days. As the Mondaq analysis frames it, “every unresolved user complaint is now one step away from a formal regulatory proceeding.” For a held-balance dispute on a legitimate operator, that OGAI rung is genuine pressure — it’s the gaming-side equivalent of the RBI Ombudsman on the payment side. It does not help against an offshore Tier-4 clone that OGAI can’t reach, which is the same asymmetry that runs through this whole guide.

The post-PROGA bottom line in two sentences: there is no 180-day refund window — that draft rule was dropped. Recovery for a legit app runs on RBI rail rules + contract/consumer law + the operator-to-OGAI grievance ladder, and for a scam clone it runs on rail-traceable money + a cybercrime report, with the in-app “balance” largely unrecoverable.

How a normal ludo withdrawal works (the four gates)

Every withdrawal from a legitimate ludo app passes through four gates in order. A “stuck” payout is just a payout sitting at one of these gates. Naming the gate tells you the fix. (On a wind-down app, gates 1–3 still apply to releasing your existing balance; you simply can’t add to it.)

Gate 1 — KYC verification (PAN + Aadhaar)

No legal real-money app in India can pay cash to an un-verified account. That isn’t the app being difficult; it’s anti-money-laundering law. To withdraw you generally need:

• PAN card — mandatory, because the app must report tax deducted against your PAN.
• Aadhaar or another government ID — for identity and address verification.
• A bank account or UPI ID in your own name that matches the KYC name.

On Zupee, for example, your first withdrawal typically triggers KYC — submitting PAN details, and sometimes Aadhaar for address verification — and a valid PAN is required to claim prizes regardless of value. The single most common silent reason a first ludo withdrawal stalls is a name mismatch: your UPI handle reads “RAHUL K” but your PAN reads “Rahul Kumar,” the risk engine can’t auto-match, and the payout is parked for manual review. If your very first withdrawal is “pending” while later small ones flew through, suspect a name/KYC mismatch first.

First-withdrawal reality check: many apps run a stricter manual review on your first ever payout — even a clean ₹100 test — before they trust the account. A first ludo payout taking longer than later ones is normal, not a red flag by itself.

Gate 2 — The withdrawal request and minimum/limit checks

When you tap “withdraw,” the app checks the amount against its own rules:

• Minimum withdrawal — frequently around ₹100 for UPI on legit apps, higher for bank transfer. On scam clones it’s deliberately set at ₹5,000 so you never reach it.
• Daily / monthly limits — many apps cap how much you can pull in 24 hours. WinZO’s documented practice was especially aggressive: per the Enforcement Directorate, users could add money without limit but were restricted to withdrawing only the “winning amount”, with daily withdrawal caps tied to a “loyalty level” that maxed out below ₹1 lakh/day. A hidden cap looks exactly like a “stuck” withdrawal — the request just sits there.
• Wagering / play-through — if your balance includes bonus money, the app may block withdrawal until you’ve wagered a multiple of the bonus. That’s in the terms you accepted, and it’s the legal reason a “₹500 balance” sometimes refuses to release.

If your withdrawal is rejected or stuck at this gate, the cause is a rule, not a payment failure — and the only fix is to satisfy the rule (finish KYC, lower the amount under the cap, complete the wagering) or dispute the rule’s fairness.

Gate 3 — The app’s payout queue and risk hold

Once your request clears the rules, it enters the operator’s payout queue:

• Auto vs manual review. Small, clean payouts from trusted accounts are usually auto-approved and pushed to UPI in seconds. Larger amounts, new accounts, accounts with unusual win patterns, or accounts flagged for a duplicate device/IP get routed to manual review — that’s where “pending for 6 hours / 1 day” comes from.
• Risk holds. If the anti-fraud system suspects collusion, multi-accounting, bot abuse, or a payment-method problem, it can freeze the payout pending investigation. The tell is usually a support reply mentioning “verification,” “review,” or “security.”

On a wind-down app this queue can also slow simply because the operator has fewer staff. A payout sitting in the queue is far more often a slow approval than a theft — a regulated operator that wanted to keep your money would reject it with a reason, not queue it.

Gate 4 — Settlement on the payment rail (UPI / IMPS)

Finally, the approved payout is handed to the bank/aggregator and travels over UPI or IMPS to your account. UPI is near-instant when it works. But the rail has its own failure modes — a beneficiary bank that’s down, a UPI handle that no longer resolves, a daily UPI limit on your receiving account — and when settlement fails after the app debited its side, you get the dreaded “debited but not credited” state. That state has the strongest consumer protection in the whole chain, and it’s worth understanding precisely.

What’s actually happening when settlement fails: NPCI batch windows and auto-reversal

Here’s the original-insight piece most ludo explainers skip. “UPI is instant” is true for the successful path. The failure path is not instant — it runs on reconciliation cycles, which is why a failed payout can sit in limbo for a day before it bounces back.

When a UPI payout is initiated, money is debited at the sending side and a credit instruction is sent to your bank. If your bank doesn’t confirm the credit (it was down, the handle didn’t resolve, a timeout), the transaction is now in a deemed-failed / pending state. It does not reverse the instant the screen says “failed.” Banks reconcile these in cycles, and the rule that governs the outcome is RBI’s Harmonisation of Turn Around Time (TAT) circular.

Per RBI Circular DPSS.CO.PD No.629/02.01.014/2019-20, dated 20 September 2019, the binding numbers are:

• Account-to-account UPI where you were debited but the beneficiary was not credited: the transaction must be auto-reversed by T+1 (the day after the transaction). If it isn’t, the bank owes you ₹100 per day of delay beyond T+1, credited automatically — you don’t have to ask.
• UPI to a merchant where confirmation failed: auto-reversal window is up to T+5 before the same ₹100/day compensation kicks in.

So if your ludo payout shows “failed” and the money left the app’s wallet, the system is already obligated to put it back, usually within one working day, automatically. That’s why the correct first move on a debited-but-not-credited payout is often wait through T+1, then dispute — not panic-spam support on hour one.

The mechanism that processes these disputes is NPCI’s Unified Dispute and Issue Resolution (UDIR) system, surfaced for consumers at the UPI Help portal (upihelp.npci.org.in). UDIR can auto-convert an unresolved complaint into a chargeback once the prescribed TAT lapses. There’s also an NPCI UPI complaint line at 1800-120-1740 and a help email at [email protected]. (The ₹100/day compensation applies to technical/system failures, not to your mistakes like sending to a wrong handle — but a stuck app-to-you payout is a system path, so it’s covered.)

The practical takeaway: a failed ludo UPI payout is the best stuck state to be in, because the refund is rule-mandated and largely automatic. A “success / paid” payout that never arrived is worse — there the money supposedly went somewhere, so you need the UTR to prove it didn’t reach you. And a payout still sitting at the app’s queue (Gate 3) is a ludo-app problem until the app actually hands it to the rail.

The ludo withdrawal-time reality table

Forget “instant.” Here is what’s actually normal versus delayed versus a problem, per rail and stage. Timings marked with a rule reference are RBI/NPCI-mandated; the rest are typical behaviour for legitimate apps and should be read as estimates, not personal payout tests.

Read that table as a clock. The moment you cross from “slow” into “problem” for your row is the moment you start the written paper trail in the next section. Don’t escalate early (support will just tell you to wait), and don’t escalate late (you’ll blow past a TAT and lose the easy refund).

Per-app ludo withdrawal reality: stated rules vs observed behaviour

The numbers below split into two columns on purpose. Operator-claimed is what the app’s own pages state. Observed / realistic is what’s widely reported, framed third-person — not a personal test. Treat the claimed column as the promise and the observed column as the planning assumption. Every legit app here also deducts 30% TDS on net winnings under Section 194BA before paying, so a payout that arrives smaller than requested is usually tax, not a delay.

A blunt caveat for 2026: Zupee, WinZO and MPL discontinued real-money ludo after PROGA. Their rows describe how they worked and how a wind-down balance recovery still behaves, because the leading apps kept withdrawals open. The “ludo earning” clone row describes a category, not a single trustworthy product.

Zupee (real-money ludo discontinued under PROGA — wind-down recovery)

WinZO (real-money ludo suspended under PROGA — restricted-withdrawal history)

MPL Ludo (real-money discontinued under PROGA)

”Ludo earning” clones (Ludo Cash, Ludo Win, and lookalikes) — assume scam

Editor’s verdict on the per-app tables: for Zupee, WinZO and MPL, the cash product is gone — your only live task is recovering an existing balance, and the rail protections plus the OGAI rung cover that. For a “ludo earning” clone, treat the marketing numbers as fiction and assume the in-app balance is unrecoverable; chase only money that left your bank.

The failure-mode taxonomy: which kind of “stuck” do you have?

Diagnosing the type is 80% of the fix, because each type escalates differently. Here’s the six-type triage, then a deeper ten-reason breakdown with a specific fix for each.

Type 1 — Pending / processing (sitting in the app’s queue)

Symptom: the app shows “processing,” “pending,” or “under review.” No UTR yet. What’s really happening: Gate 3. Auto-approval didn’t fire — manual review, a daily cap, or a thinly-staffed wind-down queue. Fix: Wait the stated window (24 hours on a first withdrawal). Past it, raise an in-app ticket (Day 0). This is a ludo-app problem, so app support is the first lever. Deeper guide: the shutdown-app recovery page covers the wind-down-queue case.

Type 2 — “Paid / success” in the app, but nothing in your bank

Symptom: the app marks the withdrawal “completed” and may show a UTR, but your bank never received it. What’s really happening: a genuine rail failure that hasn’t reflected, a payout to a stale handle, or (rarely) the app’s status running ahead of reality. Fix: Get the UTR, then ask your bank to trace it. No credit against that UTR = proof the money didn’t reach you. The UTR is everything here.

Type 3 — Failed, but money debited (UPI debited-but-not-credited)

Symptom: the screen says “failed,” yet the amount left somewhere. What’s really happening: Gate 4 rail failure — the most consumer-protected state. Fix: This is the T+1 auto-reversal case. Note the UTR, wait through T+1, then raise a UPI dispute (it routes into NPCI UDIR) and claim ₹100/day if past T+1.

Type 4 — Amount received is less than you withdrew

Symptom: money arrived, but smaller than your withdrawal. What’s really happening: almost always TDS — 30% on net winnings under Section 194BA. Not theft, not a fee dispute. Fix: No dispute needed. The deducted amount appears against your PAN in Form 26AS / AIS and is creditable when you file.

Type 5 — KYC rejected / account blocked or frozen

Symptom: withdrawal blocked with a KYC-failed or account-restricted message. What’s really happening: Gate 1. Name mismatch, blurry document, a flagged account, or a risk freeze. Fix: Resubmit clean KYC matching your bank name exactly; if frozen for “investigation,” demand a written reason and timeline.

Type 6 — Limit hit / minimum not met

Symptom: withdrawal won’t submit, or silently fails, around a round number or right after a previous payout. What’s really happening: Gate 2. Under the minimum, over a daily cap (recall WinZO’s loyalty-tier caps), or un-wagered bonus. Fix: Check the stated minimum (~₹100 on legit apps) and the daily cap. Split the withdrawal under the cap, or wait for the 24-hour reset.

The taxonomy in one line: Types 1, 5, 6 are ludo-app problems (escalate to the app, then the grievance ladder to OGAI). Types 2, 3 are payment-rail problems (escalate to your bank, NPCI, then RBI). Type 4 is not a problem at all — it’s tax. Sorting your case into the right column is the difference between a fix in 3 days and a month of shouting at the wrong door.

The ten concrete reasons a ludo payout actually stalls — with the specific fix for each

The six types are the shape. Here is the deeper layer: the ten specific mechanical reasons a payout sits, in rough order of frequency, each with the one fix that clears it.

1. KYC name mismatch (bank/UPI vs PAN). Your UPI reads “RAHUL K,” your PAN reads “Rahul Kumar,” the risk engine can’t auto-match. Fix: make your UPI/bank name match PAN exactly, re-submit KYC, use the same account to deposit and withdraw. The single most common silent stall.
2. Name mismatch at the bank’s end. Even if app KYC passed, a credit can fail if the beneficiary name doesn’t reconcile. Fix: confirm your bank holder name matches PAN; correct it with the bank, not the app.
3. Daily/monthly cap hit. Recall WinZO’s loyalty-tier daily caps below ₹1 lakh. Fix: check the stated cap, split the request, or wait for the 24-hour reset.
4. Risk-review hold on a win spike or new account. A sudden large win or a big first withdrawal triggers manual review. Fix: wait the stated window, then ask support in writing for a timeline; keep the ticket ID.
5. TDS/GST deduction confusion. The payout arrived 30% lighter. Fix: none needed — that’s Section 194BA TDS; confirm against the app’s TDS statement and your AIS. A deposit buying fewer coins is the separate 28% GST.
6. Bank batch window (NEFT/IMPS fallbacks). A bank-transfer payout missed a half-hourly NEFT batch. Fix: allow 30 minutes to a couple of hours; only escalate past 24 hours.
7. NPCI / bank downtime. The beneficiary bank or UPI rail is temporarily down. Fix: this resolves on the rail’s own reconciliation — wait through T+1; if still missing, it’s the debited-but-not-credited case with ₹100/day protection.
8. App-side wallet vs withdrawable balance. Your “balance” shows ₹800 but only ₹300 is withdrawable; the rest is deposit or loyalty/bonus. Fix: read the withdrawal screen’s withdrawable figure, not the headline wallet number.
9. Locked bonus / “loyalty” balance. A welcome/referral bonus carries a play-through you haven’t met, so it’s locked. Fix: finish the stated wagering, or accept it’s non-withdrawable; this is in the terms, not a bug. On scam clones, the “loyalty balance” is often never withdrawable by design.
10. Duplicate-account / multi-device flag. The anti-fraud system sees the same device, IP, or instrument across accounts and freezes the payout. Fix: stop creating accounts, contact support with your registered number, ask for the specific reason in writing — never spin up a “new” account to escape it, which deepens the flag.

For the payment-rail reasons (6, 7) the refund hub goes screen-by-screen: refund and dispute recovery.

The payout rails: UPI vs IMPS vs NEFT vs bank transfer

Which rail your ludo payout rides decides how fast it clears, its cap, and which dispute path applies when it fails. Most ludo payouts default to UPI for small amounts and fall back to IMPS/NEFT for larger ones or when a UPI handle won’t resolve.

The practical implications for a stuck ludo payout:

• Small payout on UPI gets the strongest protection: the RBI TAT circular forces a T+1 auto-reversal on a debited-but-not-credited transaction, ₹100/day after. The easiest case to win.
• Large payout on IMPS is normally instant; a stall usually means a beneficiary-detail problem you dispute through your bank with the RRN/UTR, not through a UPI app.
• NEFT delay of up to a couple of hours is normal batch timing, not a failure — it settles in half-hourly batches. Don’t escalate a NEFT payout inside the first two hours.
• A UPI handle that no longer resolves (you changed banks, deleted the app, closed the linked account) is a common reason a “paid” payout never lands. The fix: update your withdrawal method to a live account and ask support to re-issue, with the original UTR as evidence the first attempt failed.

Knowing the rail tells you who to complain to. UPI failures go to the UPI app / NPCI UDIR first. IMPS and NEFT failures go to your bank’s failed-transaction desk first. Both ultimately escalate to your bank’s grievance officer, then the RBI Ombudsman — but the first door differs.

Find your UTR and raise a UDIR complaint — exact menu path per UPI app

You cannot trace or dispute a “paid but not received” ludo payout without the UTR (also shown as a 12-digit reference / RRN). Every UPI app labels it differently and buries it in a different menu. Here’s exactly where to look, and how to raise the in-app complaint that feeds NPCI’s UDIR, for the four apps most Indians use (app-by-app labels here).

PhonePe

• Find the UTR: History → tap the transaction → shown as “UPI Reference No.” (12 digits). Also in the bank SMS and your statement.
• Raise the complaint: on that transaction’s detail screen, tap Help / Contact Support → choose “money debited but not received” / “payment failed” → submit. PhonePe routes it to your bank and into the NPCI dispute flow.

Google Pay

• Find the UTR: tap the transaction → scroll to details → it appears as “Bank Reference ID” / “UPI transaction ID” (12 digits).
• Raise the complaint: on the transaction screen, tap the support/question option → select the failed/not-received issue → raise dispute. It’s forwarded to your bank through the same UDIR mechanism.

Paytm

• Find the UTR: Balance & History / Passbook → tap UPI & Bank Transfer → open the transaction → shown as “UPI Ref No.”
• Raise the complaint: on that transaction, tap Help & Support at the bottom → pick the dispute reason → submit. Use the per-transaction help path, not the generic app help menu.

BHIM

• Find the UTR: Transaction History → tap the transaction → labelled “Transaction ID.”
• Raise the complaint: open the problem transaction → tap “Raise Concern” → file. BHIM sends it to your bank.

If the in-app route stalls or the app won’t let you raise a concern (common when the app no longer recognises the beneficiary), go straight to the NPCI UPI Help portal “Dispute Redressal” page and file with the transaction ID, bank, amount, date and email — or call 1800-120-1740. NPCI’s stated UDIR resolution window is 3–5 working days.

One thing the apps don’t make obvious: the UTR is the same number whether labelled UPI Reference No., Bank Reference ID, UPI Ref No. or Transaction ID — the single thread tying your debit to a missing credit. Capture it on Day 0, because once a “failed” transaction ages out of the app’s quick view, digging it back out is far harder, and your bank cannot trace a credit you can’t name.

”I got less than I withdrew” — the ludo tax reality (194BA and GST)

A massive share of “the ludo app cheated me” complaints are actually tax, correctly deducted. If your payout arrived but was smaller than your winnings, read this before disputing — fighting a legal TDS deduction wastes the days you’d need for a real problem.

Income tax: 30% TDS on net winnings (Section 194BA)

Since 1 April 2023, every legal online-gaming app in India must deduct TDS at 30% on your net winnings — with no minimum threshold. The old ₹10,000 threshold is gone. This is Section 194BA of the Income-tax Act, with the computation mechanism in Rule 133 and the CBDT Circular No. 5/2023 dated 22 May 2023.

“Net winnings” is not “every win.” Per Rule 133, the financial-year formula is:

Net winnings = (A + D) − (B + C) where A = total amount withdrawn during the year, D = closing wallet balance at 31 March, B = total non-taxable deposits during the year, C = opening wallet balance at 1 April. (Non-withdrawable bonuses are excluded from balances and are not deposits.) — Rule 133 / Circular 5/2023

In plain terms, the app taxes the amount you actually came out ahead, not every rupee that crossed the board. TDS is deducted at each withdrawal and on any remaining net winnings at financial-year end — so a year-end balance you never withdrew can still be taxed. The 30% is reported against your PAN, which is exactly why PAN-KYC is mandatory before you can withdraw, and why a PAN mismatch stalls payouts.

Worked example 1 — a net-winner (deposit, win, withdraw)

Assume a single ludo account, no opening balance, a clean financial year.

• You deposit ₹10,000 (this is B, your non-taxable deposit).
• You play and your withdrawable balance grows to ₹25,000.
• You withdraw ₹25,000 (this is A).
• Opening balance C = ₹0, closing balance D = ₹0.

Net winnings = (A + D) − (B + C) = (25,000 + 0) − (10,000 + 0) = ₹15,000.

TDS at 30% on ₹15,000 = ₹4,500. So the app pays out ₹25,000 − ₹4,500 = ₹20,500 to your bank and remits ₹4,500 against your PAN. Your bank shows ₹20,500 arriving; the “missing” ₹4,500 is in Form 26AS / AIS and is creditable when you file — you’re not simply losing it.

The per-withdrawal nuance. Within a year, the app computes net winnings comprised in each withdrawal and only taxes the part not already taxed — so it doesn’t double-tax. Per CBDT’s worked illustration, if your net winnings in April were ₹90 (below ₹100, no TDS that month) and you then have ₹200 more net winnings withdrawn in May, the app deducts 30% on the cumulative ₹290, not on ₹200 alone.

The year-end edge case. Suppose you withdrew nothing during the year but ended 31 March with ₹15,000 of net winnings still in the wallet (A = 0, D = 15,000). Net winnings = (0 + 15,000) − 0 = ₹15,000, and the app must deduct ₹4,500 TDS on that balance at year-end even though you never cashed out. This is why a ludo wallet can quietly shrink at the start of April — that’s the year-end 194BA deduction, not a glitch. It matters extra during a wind-down: an un-withdrawn balance can still be taxed before you recover it.

Worked example 2 — a net-loser (no TDS)

Now the player who lost on the year.

• You deposit ₹10,000 (B).
• You play, win some, lose more, and withdraw ₹6,000 total during the year (A).
• Opening C = ₹0, closing D = ₹0.

Net winnings = (6,000 + 0) − (10,000 + 0) = −₹4,000.

Net winnings are negative, so there is no TDS — you didn’t come out ahead. The app should pay your ₹6,000 withdrawals in full. Two warnings from the CBDT guidance: a negative net-winnings figure cannot claw back TDS the app already deducted on an earlier withdrawal in the same year (you adjust that in your ITR), and if you hold multiple accounts on the same platform, the app must consolidate all of them before computing net winnings — so a loss on one account offsets a win on another within the same operator, but not across different operators.

GST: 28% on deposits (why your deposit bought fewer coins)

Separately, since 1 October 2023, online money gaming attracts 28% GST on the full value of deposits (not on winnings), under CBIC Notifications dated 29 September 2023. That’s a deposit-side tax, so it doesn’t reduce a withdrawal — but it’s why ₹100 deposited converted to fewer playable coins than you expected. Players who don’t know this misread the gap as a “deposit not fully credited” bug. It isn’t; it’s the 28% GST.

The ludo tax bottom line in two numbers: 30% off your net winnings on the way out (Section 194BA, no threshold), and 28% GST on your deposits on the way in. Neither is the app stealing. If your shortfall matches a 30% cut on net winnings, stand down — that’s TDS, yours to reclaim at filing. A forward note: from 1 April 2026, the 194BA provision is consolidated under Section 393(3) of the new Income-tax Act, 2025, but the 30% on net winnings, no threshold substance carries over.

The universal Day-0-to-30 escalation ladder

This is the spine of recovery, and it works because it matches each action to the rule-clock from the table above. Don’t skip rungs (you’ll waste days), and don’t jump to RBI on Day 1 (they’ll bounce you back to the entity). Climb in order; every rung has a copy-paste template next.

Day 0 — Freeze the evidence and open the in-app ticket

The single highest-leverage thing you do on Day 0 isn’t complaining — it’s documentation. Within the first hour:

• Screenshot everything: the withdrawal request, the status screen, the amount, the timestamp, and your wallet balance before and after. Date-stamped screenshots are your evidence later.
• Capture the UTR / transaction reference the moment one appears. No UTR = you can’t trace a “paid” payout.
• Raise the in-app support ticket with the amount, timestamp, and UTR. Get a ticket / complaint ID in writing — this timestamps your complaint, which matters for the 30-day OGAI and Ombudsman clocks later.

Do not start a second account, do not deposit more “to unlock” the withdrawal (illegal post-PROGA and the clearest scam pattern), and never share an OTP or UPI PIN with anyone who “calls to help.” Legitimate support never needs your PIN or OTP.

Day 1–3 — Official support email + wait the rail’s TAT

• Send the same complaint by the app’s official support email (from its listing / official site), referencing the in-app ticket ID. Email creates a paper trail an in-app chat can’t.
• If this is a failed/debited UPI case (Type 3), this is the T+1 window — let the auto-reversal run before disputing.
• If the app publishes a same-day or 1–3 working-day SLA, you’re still inside it. Be firm but patient.

Day 4–7 — Open the payment-side dispute (UTR + NPCI)

If the money is genuinely gone on the rail (Types 2 and 3) and hasn’t come back:

• Open your UPI app’s “raise complaint / dispute” on that transaction (path per app above). This feeds NPCI UDIR, which can auto-convert to a chargeback after the TAT.
• Or call your bank and lodge a failed-transaction complaint with the UTR; ask explicitly for the ₹100/day compensation if past T+1 (the RBI TAT circular entitles you to it on system failures).
• You can also use the NPCI UPI Help portal or the line 1800-120-1740. NPCI’s stated UDIR window is 3–5 working days.

Day 8–15 — Formal bank complaint + operator grievance officer

• Escalate the bank complaint to a written formal complaint if the helpline did nothing. Get a complaint reference number.
• Send the operator’s grievance officer a final-notice email: restate the facts, the ticket ID, the UTR, the days elapsed, and state you’ll escalate to OGAI, the RBI Ombudsman, and the National Consumer Helpline if unresolved. A clear, dated final notice often unsticks a payout because it signals you know the process — and for a legit wind-down operator, the OGAI mention now carries real weight.

Day 16–30 — OGAI, RBI Ombudsman, and consumer forum

If the operator’s grievance outcome is unsatisfactory, or a payment failure remains unresolved:

• For a held balance on a legitimate operator, escalate to the Online Gaming Authority of India (OGAI) — under the PROGA Rules 2026, an aggrieved user dissatisfied with the operator’s grievance outcome may approach OGAI within 30 days.
• For a payment-rail failure, after 30 days without resolution from the regulated entity (your bank / payment-system participant), file with the RBI Integrated Ombudsman Scheme 2021 (RB-IOS) at cms.rbi.org.in. Redress is free.
• For the consumer-service angle (an app refusing a clearly-owed, KYC-clean payout), the National Consumer Helpline 1915 and the consumer-forum route apply.
• If you suspect outright fraud — a clone app, a fake “customer care number,” an OTP scam — report immediately to the cybercrime helpline 1930 and cybercrime.gov.in, and flag the payment entity on RBI’s Sachet portal.

Honest limit of this ladder: OGAI and the RBI Ombudsman are powerful against regulated operators and the payment rail. They’re weaker against a scam clone or offshore app that simply ignores everyone, because that operator may sit outside Indian regulatory reach. That asymmetry is the single best argument for only ever playing where KYC and payouts are real — and for treating a “ludo earning” clone’s in-app balance as likely gone.

Copy-paste complaint templates

Fill in the bracketed parts. Keep every message factual, dated, and ID-stamped — emotion doesn’t move a payout, a UTR does.

Template A — In-app support ticket (Day 0)

Subject: Ludo withdrawal not received — Ticket request

My withdrawal of Rs [AMOUNT] requested on [DATE, TIME] is showing
"[STATUS shown in app]" and has not reached my account.
Registered mobile: [NUMBER]
UPI ID / bank used: [HANDLE / A/C]
UTR / reference (if shown): [UTR]
KYC status: completed (PAN + Aadhaar verified)
Please confirm the payout status and the UTR, and resolve within your
stated payout window. Please share a complaint/ticket ID for this request.

Template B — Operator grievance-officer escalation (Day 1–3)

Subject: [Ticket ID] Ludo withdrawal of Rs [AMOUNT] not credited — escalation

To: [official support email] / Grievance Officer

I raised in-app ticket [TICKET ID] on [DATE] for a withdrawal of
Rs [AMOUNT] that has not been credited to [UPI/bank]. It has now been
[N] days, past your stated payout window of [X working days].

Transaction details:
- Amount: Rs [AMOUNT]
- Requested: [DATE, TIME]
- Status in app: [STATUS]
- UTR / reference: [UTR]
- Registered number: [NUMBER]
- KYC: completed (PAN matches bank account name)

Please credit the payout or provide the UTR and a written reason for the
delay within 48 hours. If unresolved, I will escalate to the Online Gaming
Authority of India (OGAI) under the PROGA Rules 2026, my bank's UPI dispute
process, NPCI UDIR, the RBI Ombudsman (RB-IOS 2021), and the National
Consumer Helpline (1915).

Template C — Bank / UPI failed-transaction dispute (Day 4–7)

Subject: Failed UPI credit — UTR [UTR] — request refund + TAT compensation

A UPI transaction was debited but not credited to my account.
- UTR / reference (RRN): [UTR]
- Amount: Rs [AMOUNT]
- Date/time: [DATE, TIME]
- My account / UPI ID: [A/C or HANDLE]

Per RBI circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019), a
debited-but-not-credited transaction must be auto-reversed by T+1, with
Rs 100/day compensation for delay beyond T+1. It has now been [N] days.
Please reverse the amount and credit the applicable compensation, and
share the complaint reference number.

Template D — RBI Ombudsman (RB-IOS) grievance (Day 30+)

Nature of complaint: Deficiency in service — failed/unresolved digital
payment (ludo withdrawal not credited).

Regulated entity: [YOUR BANK / payment system participant]
Date of original transaction: [DATE]
Amount: Rs [AMOUNT]   UTR: [UTR]
Complaint first raised with the entity on: [DATE], reference [REF]
Entity's response: [none / unresolved] after 30 days.
Relief sought: credit of Rs [AMOUNT] + Rs 100/day compensation per
RBI TAT circular DPSS.CO.PD No.629/02.01.014/2019-20.

File Template D at cms.rbi.org.in only after 30 days without resolution, since that’s the eligibility gate for the RB-IOS 2021.

Template E — National Consumer Helpline complaint (parallel, for app-side deficiency)

To: National Consumer Helpline (1915 / consumerhelpline.gov.in)

Complaint: Service deficiency — ludo app refusing/failing to pay a
verified, KYC-complete withdrawal.

- Operator / app: [APP NAME]
- Registered mobile: [NUMBER]
- Withdrawal amount owed: Rs [AMOUNT]
- Requested on: [DATE]; in-app ticket [TICKET ID] raised [DATE]
- App's status / response: [STATUS / no response after N days]
- KYC: completed; PAN matches bank account name
Relief sought: release of Rs [AMOUNT] to my registered account, and a
written reason for the delay.

Use Template E in parallel with the bank/RBI route when the failure is on the app’s side (it holds an approved, owed balance). The consumer-helpline angle reaches the operator’s service obligation; the RBI route reaches the payment rail.

Grievance contact reference block

Keep this handy; it’s the whole escalation map in one place. Use the door that matches your problem type.

Order of doors, in one line: app → operator grievance officer → OGAI (for a held balance) and app → bank/UPI → NPCI → RBI Ombudsman (for a rail failure), with consumer helpline 1915 in parallel for app-side deficiency and cybercrime 1930 the instant fraud is involved.

Is it a delay or a scam? Red flags that change your strategy

Most stuck payouts on legitimate ludo apps are delays. But the “ludo earning” category is overrun with apps that are not legal, not licensed, or outright clones, and on those the ladder above has limited teeth. Use these red flags to decide how hard to fight versus how fast to cut losses:

• No PAN/KYC was ever required to deposit or withdraw. A legal app must do KYC. No KYC is a sign you’re not on a regulated platform — your RBI leverage shrinks.
• The minimum withdrawal is high and you can never reach it. A ₹5,000 floor while spins drop to ₹0.01 is the textbook rigged-math scam. Real apps set ~₹100 floors.
• You’re forced to watch ads to “earn,” and the developer hides its company name, website, or contact. That opacity plus an ad-revenue model is the clearest clone signature.
• “Pay a membership fee / deposit ₹X to unlock your withdrawal.” No legal app requires a deposit to withdraw. This is the single clearest theft pattern — and post-PROGA, a new deposit into a money game is also illegal. Stop, document, report.
• Fake withdrawal screenshots and celebrity photos. Scam clones fabricate proof and borrow celebrity faces to build false trust before the membership-fee ask.
• A sideloaded / “mod” / “unlimited coins” APK. Modified builds void the terms and can freeze your account and balance with no recourse.
• The “app” vanished and pending withdrawals went dark. A genuine reinstall keeps your balance (it’s tied to your registered number). A disappeared operator is a worse problem — though a legitimate PROGA wind-down is the opposite case: cash games stopped, but you should still be able to withdraw an existing balance.

If two or more are true on your ludo app, the realistic verdict is harsh: pursue the bank/UPI dispute and a cybercrime report for any rail loss, but lower your expectation of recovering a balance held inside an unlicensed operator — and don’t feed it another rupee.

Where to get real, official help

There is no “faster ludo app” that fixes a stuck payout, and after PROGA 2025 (in force 1 May 2026) moving to another real-money ludo service is not a legal option in India. What actually recovers money is the official chain, used in order, with your paper trail intact:

• For a held balance on a legit operator: the operator’s grievance officer first, then OGAI within 30 days of an unsatisfactory outcome. The broader withdrawal-and-refund hub walks this end to end: refund and dispute recovery, and for a discontinued app specifically, recover balance from a shutdown app.
• For a rail failure (debit not credited): your bank first, then NPCI UDIR, then the RBI Ombudsman after 30 days. The auto-reversal is T+1 and compensation is ₹100/day under the RBI TAT circular.
• For app-side deficiency: National Consumer Helpline 1915 in parallel.
• For fraud: cybercrime 1930 / cybercrime.gov.in plus the RBI Sachet portal.

Editor’s verdict. A rail failure — money left your bank but never reached you — is the recoverable kind; the rules force a refund. A balance held inside a discontinued-but-legitimate operator (Zupee, WinZO, MPL) is recoverable too, through the operator-to-OGAI ladder, as long as you complete KYC and act while the operator is still reachable. A balance inside a “ludo earning” clone is the hard kind — pursue rail-traceable money and report the fraud, but never deposit more “to unlock” a withdrawal. Post-PROGA that deposit is both throwing good money after bad and illegal.

Related fixes (go deeper on your exact case)

For the case that matches your symptom, these go step-by-step:

• Any refund / held-balance recovery → refund and dispute recovery — the master hub for the whole recovery ladder.
• App shut down / wound down → recover balance from a shutdown app — the disappeared/wind-down operator playbook.
• Zupee specifically → Zupee withdrawal recovery — the Zupee post-shutdown withdrawal flow.
• Card-game (Teen Patti) parallel → 3 Patti withdrawal — the same rail rules and ladder for the adjacent vertical.

FAQ

1. How long does a ludo money withdrawal take? Most UPI payouts from legitimate ludo apps settle in minutes to a few hours, with same-day as the norm. Zupee, for example, processes UPI withdrawals “instantly or within a few minutes” and bank transfers in a few hours. If a UPI payout is debited but not credited, RBI’s TAT circular requires auto-reversal by T+1, after which you’re owed ₹100 per day.

2. Can I still withdraw from Zupee after the real-money ban? Yes for an existing balance. Zupee halted paid games on 21 August 2025, paused deposits, and kept withdrawals open, and the service was still processing withdrawals in 2026. Complete KYC, request the withdrawal, and don’t re-deposit — deposits are off and a new RMG deposit is illegal. The Zupee recovery page covers the exact steps.

3. Is there really no 180-day refund window for my ludo balance? Correct. A draft of the rules floated a 180-day repayment window, but that provision was dropped from the final notified Promotion and Regulation of Online Gaming Rules, 2026. There is no statutory refund clock. Recovery runs on RBI rail rules, ordinary contract/consumer law, and the operator-grievance-to-OGAI ladder under the 2026 Rules.

4. Are “ludo earning apps” that promise ₹500/day legit? Almost never. Independent reviews report many never pay a single rupee: the minimum withdrawal is set at ₹5,000, earnings drop to ₹0.01 per spin near it, the developer earns from ads, and some demand a “membership fee” to “unlock” payouts. Treat any ludo earning clone as a scam until it actually pays — and chase only money that left your bank.

5. Do I need KYC to withdraw from a ludo app? Yes. Every legal real-money app requires PAN and Aadhaar-based KYC before any cash withdrawal, because the app must report 30% TDS against your PAN. On Zupee, the first withdrawal triggers PAN (and sometimes Aadhaar) verification. A name mismatch between your UPI handle and PAN is the single most common silent cause of a stuck first ludo payout.

6. Why did I receive less money than I withdrew? Almost always TDS: legal apps deduct 30% on net winnings under Section 194BA, with no minimum threshold, since 1 April 2023. On a ₹25,000 withdrawal where your net winnings were ₹15,000, that’s a ₹4,500 cut. The deducted amount appears against your PAN in Form 26AS / AIS and is adjustable when you file.

7. How is “net winnings” calculated for ludo TDS? Per Rule 133, net winnings = (withdrawals + closing balance) − (deposits + opening balance) over the financial year, excluding non-withdrawable bonuses. TDS is deducted at each withdrawal and again on any year-end balance. So if you end 31 March with ₹15,000 of net winnings un-withdrawn, the app still deducts ₹4,500 then — relevant if you’re mid-wind-down and haven’t cashed out.

8. My ludo withdrawal was debited but not credited — what happens? Under RBI Circular DPSS.CO.PD No.629 (20 Sep 2019), it must be auto-reversed by T+1. If it isn’t, your bank owes you ₹100 per day of delay, credited automatically — though you should chase it if it doesn’t appear. This is the best stuck state to be in, because the refund is rule-mandated.

9. What is a UTR and where do I find it? A UTR (Unique Transaction Reference) is the 12-digit reference for a UPI/bank transfer. PhonePe labels it “UPI Reference No.”, Google Pay “Bank Reference ID”, Paytm “UPI Ref No.”, BHIM “Transaction ID” — all the same number. You cannot trace or dispute a “paid but not received” ludo withdrawal without it, so capture it on Day 0.

10. Why is my WinZO ludo withdrawal capped so low? WinZO’s documented practice (flagged by the Enforcement Directorate) let users add money without limit but restricted withdrawals to the “winning amount”, with daily caps tied to a “loyalty level” that maxed out below ₹1 lakh/day. A low cap looks like a stuck withdrawal but is a rule — split requests under the cap or wait for the 24-hour reset.

11. The ludo app says “paid / success” but I got nothing — how do I prove it? Get the UTR from the app and ask your bank to trace it. No record of a credit against that UTR = evidence the money didn’t reach you. Open a UPI dispute (NPCI UDIR) and escalate. NPCI’s stated resolution window is 3–5 working days.

12. Which is faster — UPI, IMPS or NEFT for my ludo payout? UPI is instant (cap ~₹1 lakh/day) and IMPS is instant up to ₹5 lakh; NEFT settles in 30 minutes to 2 hours because it runs half-hourly batches. A NEFT payout that takes an hour is normal, not stuck — don’t escalate it inside the first two hours.

13. Where do I complain if a legit ludo operator won’t pay an owed balance? Climb in order: the operator’s grievance officer, then OGAI within 30 days of an unsatisfactory outcome under the PROGA Rules 2026. For any rail failure, run the bank → NPCI → RBI Ombudsman path in parallel, and the National Consumer Helpline 1915 for service deficiency.

14. Are the “ludo customer care numbers” on Google safe to call? Frequently not. Most legal apps have no public phone helpline and route support in-app; scammers post fake “care numbers” to phish your OTP and UPI PIN. Never share an OTP or PIN with a caller, and report fake numbers to the cybercrime helpline 1930 and cybercrime.gov.in.

15. Can I get my money back if a ludo app turns out to be a scam? For money lost on the payment rail, pursue the bank/UPI dispute, NPCI, and RBI Ombudsman, and report fraud to 1930 and the RBI Sachet portal. But recovery of a balance held inside an unlicensed or offshore ludo clone that ignores you is not guaranteed — it may sit outside Indian regulatory reach. That’s the strongest reason to only play where KYC and payouts are real, and to assume a “ludo earning” clone’s in-app balance is gone.

Sources & method. Withdrawal timings, taxes, legality and escalation steps on this page are built from primary regulatory sources, named operator pages, and reported industry coverage — not personal payout tests. Key references: the Promotion and Regulation of Online Gaming Act, 2025 and its Rules effective 1 May 2026; the Mondaq decode of PROGA and the 2026 Rules (no 180-day refund window in the final rules; OGAI 30-day grievance escalation); the sector-wide real-money shutdown and Zupee’s 21 Aug 2025 halt with withdrawals kept open; the WinZO suspension and ED findings on restricted withdrawals; RBI failed-transaction TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019); RBI Integrated Ombudsman Scheme 2021 and cms.rbi.org.in; NPCI and NPCI UPI Help / UDIR; CBDT Section 194BA, Rule 133 and Circular No. 5/2023; CBIC 28% GST notifications (29 Sep 2023); scam ludo earning app red flags; cybercrime reporting at cybercrime.gov.in / helpline 1930; National Consumer Helpline 1915. 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.