Claim TDS Refund on Online Gaming Winnings: 194BA How-To

The 50-second answer

A gaming TDS refund exists only when your full-year net winnings come out lower than the 30% already withheld under Section 194BA. You claim it by filing ITR-2/ITR-3, reporting gross winnings in Schedule OS under 115BBJ and the operator’s TDS in Schedule TDS2. For a stuck payout that isn’t tax, work refund dispute recovery instead.

This is not tax advice. It is a sourced, practical explainer to help you tell a refundable over-deduction apart from a 30% cut you simply owe. Every number is tied to a primary source — Section 194BA / Rule 133, CBDT Circular 5/2023, or the income tax e-filing portal. For your own return, talk to a qualified chartered accountant.

Why this page exists, and what it is not. There is a separate, longer explainer on this site for the law of gaming tax — the TDS on online gaming overview walks through Section 194BA, Rule 133, and how the 30% is computed. This page does not repeat that. This is the practical how-to-claim: when a refund is genuinely on the table, the exact ITR steps to recover it, and — just as important — the honest cases where no refund exists and you’re owed nothing back. If you came here hoping to “claim back” the 30% on a year you finished ahead, read the hard truth section first; it will save you a wasted filing.

The single rule that decides everything: refund ≠ deduction reversal

Start here, because almost every wrong expectation about gaming TDS refunds collapses into one misunderstanding. People treat the 30% the app took as a deposit they can ask back. It is not. It is tax you may or may not owe, withheld in advance against your PAN.

So the question is never “can I get the 30% back.” The question is: does my actual annual tax on these winnings come out lower than the 30% already withheld? If yes, the gap is refundable through your return. If no, there is nothing to refund — the withholding simply matched the liability, which is exactly what it was designed to do.

Put the two numbers side by side and the whole subject becomes arithmetic:

Tax withheld (TDS): 30% of net winnings, taken by the platform under Section 194BA at each withdrawal and at year-end. This is a real, immediate cut.
Tax owed (final liability): 30% of your full-year net winnings under Section 115BBJ, the charging section, settled when you file.

In the simple, clean case these two are the same number, and a refund of zero is the correct outcome. A refund appears only when, by 31 March, your final liability has fallen below what was already withheld during the year. There are exactly a few ways that happens, and we work each one below. But hold the framing tight: 194BA is the withholding rule; 115BBJ is the charging rule. A refund is the leftover when the withholding overshot the charge.

The one-line rule: a gaming TDS refund is the gap between 30% already withheld and the 30% you actually owe on full-year net winnings — it exists only when the withholding overshot, never just because money was deducted. Confirmed by the PKC Management Consulting 194BA guide and the Patron Accounting note on filing when TDS is deducted.

The 60-second diagnostic: do you even have a refund?

Before any ITR talk, run this. It takes a minute and tells you whether to keep reading the filing sections or stop entirely. Three questions, in order.

Did the platform actually deduct TDS? Check your payout records or the app’s TDS statement. If a payout arrived 30% lighter than the net winnings inside it, yes. If the whole withdrawal is missing with no tax deducted, that’s not a tax problem at all — it’s a stuck payout, and you should work the refund dispute recovery ladder, not file an ITR.
What is your full-year net winnings position? Add every withdrawal plus your wallet balance on 31 March, subtract your own deposits plus your 1 April balance (this is the Rule 133 figure, unpacked in the TDS on online gaming explainer). Then take 30% of that.
Is that 30% less than what was already withheld during the year? If your computed full-year tax is lower than the cumulative TDS the platform took, the difference is your refund. If it’s equal, refund is zero. If it’s higher, you actually owe more at filing.

Only the case where question 3 says “less” puts a refund on the table. The two everyday ways that happens — and they are the entire practical core of this page — are:

The mid-year-win, late-year-loss case. You won early, the platform taxed that winning withdrawal, then you deposited more and lost it. By year-end your net position is lower than the slice already taxed. The earlier TDS overshot your true annual liability, so the excess is refundable.
The year-end over-deduction case. The platform’s 31 March sweep or a per-withdrawal computation withheld more than your reconciled full-year net winnings justify — for example a balance taxed at year-end that you then partly lost in the new year, or a TDS figure that doesn’t match your own Rule 133 math when you reconcile against your certificates.

If neither describes you, skip to the hard truth section. If one does, the rest of this page is your filing manual.

The diagnostic in one line: you have a refund only if your full-year net-winnings tax (30%) comes out below the TDS already withheld — most commonly from a win-then-lose sequence or a year-end over-deduction; otherwise the refund is zero and there’s nothing to claim.

Case 1 worked: the win-then-lose refund (the most common real refund)

This is the scenario the search results describe most often, and it’s worth doing in full rupees because it’s the one case where a refund genuinely appears. The mechanics follow the Stox N Tax Dream11 walkthrough and the Patron Accounting filing guide.

Picture one player, one platform, one financial year:

April: you deposit ₹10,000 of your own money, play well, and your withdrawable balance grows. You withdraw ₹30,000. At that withdrawal the net winnings comprised come to ₹20,000, so the platform deducts 30% × ₹20,000 = ₹6,000 TDS and pays you ₹24,000.
June–December: you deposit a further ₹15,000 from your bank, keep playing, and lose most of it. You withdraw nothing more.
31 March: your wallet closing balance is ₹2,000. Your deposits for the year total ₹25,000 (₹10,000 + ₹15,000).

Now reconcile the full year with Rule 133, (A + D) − (B + C):

Net winnings = (30,000 + 2,000) − (25,000 + 0) = 32,000 − 25,000 = ₹7,000

Your true full-year net winnings are ₹7,000, not the ₹20,000 the April withdrawal was taxed on. Your final liability under Section 115BBJ is 30% × ₹7,000 = ₹2,100. But the platform already withheld ₹6,000. The difference — ₹6,000 − ₹2,100 = ₹3,900 — is your refund, recovered through your ITR.

Why does this happen? Because 194BA withholds at each withdrawal on the net winnings inside it, but your annual liability is computed on the whole year netted together. When a big winning withdrawal early in the year is followed by deposits-and-losses later, the early withholding overshoots the annual figure. The platform does not hand that ₹3,900 back — it cannot, because the later loss happened after the withholding. Only the income tax department refunds it, and only when you file and reconcile. This is the textbook refundable case.

Case 1 in one line: an early winning withdrawal taxed at ₹6,000, followed by later deposits-and-losses that drop your full-year net winnings to ₹7,000 (₹2,100 owed), leaves a ₹3,900 refund — recovered only through your ITR, never from the app.

Case 2 worked: the year-end over-deduction refund

The second refundable case comes from the year-end sweep. On 31 March the platform must deduct 30% on any net winnings still parked in your wallet that weren’t already taxed. Usually that’s correct and final. But two situations can leave that sweep over-stated relative to your true position once you reconcile everything together.

Situation A — a sweep that double-counts against your own records. Suppose across a year the platform’s continuous ledger and your own Rule 133 reconstruction disagree, because a deposit was mis-classified (your bank deposit logged as a taxable credit, say), and the year-end deduction came out higher than your correct net winnings justify. When you file with your own properly-classified figures and the platform’s certificate, the reconciled liability can land below the withheld total, and the gap refunds.

Situation B — winnings parked at year-end that you couldn’t realise. Picture closing 31 March with ₹15,000 of net winnings in the wallet. The platform sweeps 30% × ₹15,000 = ₹4,500 at year-end. But your only income for the year is these winnings, and your total tax computed across the whole picture — once basic settlement runs through the return — equals exactly that ₹4,500, so there’s no refund there. The refund in this family appears when the year-end figure was withheld but your reconciled annual net winnings are genuinely lower, for instance because the closing balance included a non-cashable promotional credit that should have been excluded from the balance under CBDT Circular 5/2023, inflating D and the tax with it.

A concrete number for Situation B. Say the platform swept ₹4,500 on a ₹15,000 closing balance, but ₹3,000 of that “balance” was a play-only, non-withdrawable bonus that the circular says must be excluded from the balance terms. Your correct closing balance is ₹12,000, true net winnings ₹12,000, correct tax 30% × ₹12,000 = ₹3,600. The ₹4,500 withheld overshot by ₹900, which refunds when you file with the corrected figure and the platform’s TDS certificate. (In practice you’d raise the misclassification with the platform first so its 26AS filing matches — more on that below — but the direction is what matters: an over-stated balance produces an over-deduction, and the excess is refundable.)

Case 2 in one line: when the year-end 30% sweep withholds on an over-stated balance — most often a non-cashable bonus wrongly counted in the closing balance — your reconciled net winnings come out lower, and the excess refunds through the return.

The hard truth: when you CANNOT get a refund

This is the section most “how to claim gaming TDS refund” pages bury or skip, and it’s the most important one. Be honest with yourself before you file, because for the majority of players who finished the year ahead, there is no refund — the 30% is simply owed.

Here are the cases where you cannot reduce the 30%, each with the reason.

1. You finished the year net-positive. If your full-year net winnings under Rule 133 are positive, you owe 30% on that figure under Section 115BBJ, full stop. The TDS withheld matches the liability. Filing won’t conjure a refund out of money you genuinely owe in tax. The credit cancels the liability and you’re square.

2. Gaming losses do NOT offset gaming winnings across the year for tax. This is the cruel one, and it’s where most refund hopes die. Under Section 115BBJ, winnings are taxed at a flat 30% with no set-off and no slab benefit. Losses from online gaming cannot be set off against winnings or any other income, and cannot be carried forward to future years. As the TaxTalk net-winnings guide and TaxGuru’s 115BBJ/194BA analysis both state, unadjusted losses at year-end are not carried forward. So a player who won ₹2 lakh and lost ₹1.8 lakh on a different operator cannot net those — the win is taxed at 30%, the loss is gone.

3. Losses only net WITHIN the same operator, and only inside the same year. The one place a loss reduces your taxable figure is within a single platform’s accounts, because Rule 133 nets that operator’s deposits, withdrawals, and balances together. A loss on Account 1 offsets a win on Account 2 on the same operator. But a loss on Operator X does nothing for a win on Operator Y — each is a separate deductor with its own TAN computing independently. There is no cross-operator netting, at the withholding stage or in your return.

4. You can’t deduct your costs. No entry fees, no deposits-as-expenses, no internet bill, no “I spent money chasing the win.” Section 115BBJ allows zero deductions against gaming winnings. The 30% is on net winnings as Rule 133 defines them, and nothing you spent reduces it further.

5. The 30% itself is non-negotiable on a real win. There’s no lower slab, no rebate under Section 87A, no basic-exemption shelter for this income. Even if your total income is below the taxable threshold, gaming winnings are still taxed at the flat 30% under 115BBJ — the basic exemption does not apply to them. So a low earner with a genuine gaming win still owes the full 30%.

The honest summary: a refund exists only when the timing of withholding overshot your annual net position (Cases 1 and 2). If you actually came out ahead for the year across an operator, the 30% is yours to pay, and no amount of filing changes that. Anyone promising to “recover your gaming TDS” on a winning year is selling you a wasted return — or worse.

The hard truth in one line: gaming losses never offset winnings across operators or future years, there are no deductions and no slab relief, and the 30% is owed in full on a net-positive year — a refund exists only when withholding overshot your annual net position, not because you’d like the money back.

How the TDS shows up: Form 16A, Form 26AS, AIS, and TIS

You cannot claim what you can’t see and prove. Before filing, you need to find the deducted TDS in the department’s own records and reconcile it against the platform’s certificate. Four documents matter, and they are not interchangeable. This reconciliation is the single most-skipped step, and skipping it is what triggers refund delays and mismatch notices.

Form 16A — the platform’s TDS certificate

The platform that deducted your TDS (the deductor, holding a TAN) must issue you a Form 16A TDS certificate, downloaded from the TRACES portal (tdscpc.gov.in). For gaming, this is typically issued quarterly — Dream11, for instance, issues Form 16A each quarter where TDS was deducted, per the Stox N Tax guide. Form 16A shows the operator’s TAN, the amount deducted, the section (194BA), and the period. This is the document whose numbers you carry into your return, and the one you reconcile everything else against.

Form 26AS — the credit statement you actually claim from

Form 26AS is your consolidated tax-credit statement on the income tax portal. Since AY 2023-24 it focuses on tax credits — every rupee of TDS deducted against your PAN, tagged by section. Gaming TDS appears under Section 194BA. Here is the rule that trips people up, confirmed by the ClearTax 26AS guide: TDS credit can only be claimed on the basis of Form 26AS. If the TDS shows in your AIS but not in 26AS, you cannot claim it until it appears there — you must get the platform to file a corrected TDS return first. So 26AS, not AIS, is the document that governs your refund claim.

AIS — the Annual Information Statement (the income picture)

The AIS is broader: it carries not just TDS but the underlying transactions reported to the department — including your gaming winnings, “based on data sent directly from the gaming platforms to the income tax department.” Your winnings and the TDS on them appear here. The AIS is where the department sees your gaming income, which is exactly why under-reporting it triggers an automated mismatch. Treat the AIS as the income figure you must match in Schedule OS.

TIS — the Taxpayer Information Summary (the pre-fill)

The TIS is an aggregated, simplified version of the AIS, designed to pre-fill your ITR. It rolls up the AIS line items into category totals. Useful as a starting point, but always reconcile the pre-filled TIS figure against your own Form 16A — pre-fill is a convenience, not gospel, and a wrong pre-fill that you accept blindly becomes your error on the return.

The reconciliation habit, in order: pull Form 16A from the platform, pull 26AS and AIS from the portal, and confirm all three agree on the TDS figure. If the platform’s certificate says ₹6,000 but 26AS says ₹0 or ₹4,000, stop and chase the platform to correct its filing before you file — because you can only claim credit for what sits in 26AS against your PAN. For how a payout that’s short for non-tax reasons differs from this, see minimum withdrawal and charges.

The four-document rule in one line: the platform issues Form 16A (TRACES, usually quarterly), you claim credit only from Form 26AS, the AIS carries the income the department already sees, and the TIS pre-fills your ITR — reconcile all four before filing, because a 26AS that’s missing the TDS means you cannot claim it yet.

Which ITR form: ITR-2 vs ITR-3

Gaming winnings cannot go on the simple ITR-1. You need one of two forms, and which one depends on whether you also run a business.

ITR-2 — use this if you have no business or professional income. This is the form for the vast majority of players: salary, interest, capital gains, and now gaming winnings all fit here. The ITR-2 utility has a dedicated field for online-gaming income under Section 115BBJ, per the Patron Accounting filing guide.
ITR-3 — use this if you also run a business or profession (you have income under the head “Profits and gains of business or profession”). Gaming winnings still go under Income from Other Sources / 115BBJ, but the form has to accommodate your business income too.

The simple ITR-1 (Sahaj) does not accommodate gaming winnings at all — it has no field for 115BBJ income. If you’d normally file ITR-1 (salary plus a little interest) but you have gaming TDS to reclaim, you must step up to ITR-2. That’s not optional; filing ITR-1 with gaming income is an incorrect return.

One filing trigger worth flagging: if your aggregate TDS/TCS for the year exceeds ₹25,000, filing becomes mandatory regardless of your income level, per the PKC guide. Heavy gaming TDS can cross that on its own, so a player who’d otherwise skip filing may be compelled to file — which, conveniently, is also the only way to claim any refund.

The form rule in one line: file ITR-2 if you have no business income, ITR-3 if you do — never ITR-1, which has no field for 115BBJ gaming income; and note that aggregate TDS over ₹25,000 makes filing mandatory anyway.

Exactly where the numbers go: Schedule OS and Schedule TDS2

This is the mechanical heart of the claim. Two schedules carry it: one for the income, one for the tax credit. Get the relationship right and the refund computes itself; get it wrong and you trigger a mismatch.

Schedule OS — the income (report GROSS, not net-of-TDS)

Gaming winnings are Income from Other Sources, entered in Schedule OS, taxed under Section 115BBJ at the flat 30%. The ITR utility has a specific line for income chargeable under 115BBJ — “winnings from online games.”

The critical instruction, and the most common error: report the gross net winnings — the figure before TDS — not the smaller amount that actually reached your bank. If your net winnings were ₹20,000 and ₹6,000 was withheld, you report ₹20,000 in Schedule OS, not the ₹14,000 that landed. Reporting the net-of-TDS figure understates your income and creates a mismatch against your 26AS (which shows TDS computed on the gross), which can draw a defective-return notice. The gross figure is the one against which 194BA TDS appears in your 26AS, and it’s the one the system expects to see.

A subtlety on which year’s figure: report the full-year net winnings per Rule 133 — your reconciled annual figure — as the 115BBJ income. In the win-then-lose Case 1, that’s the ₹7,000 annual net, not the ₹20,000 the April withdrawal was taxed on. Reporting the true ₹7,000 (with the ₹6,000 TDS claimed as credit) is precisely what produces the refund: ₹2,100 owed against ₹6,000 withheld.

Schedule TDS2 — the tax credit (the operator’s TAN is the key)

The TDS itself goes in Schedule TDS2 (TDS on income other than salary). For each platform that deducted, enter:

the platform’s TAN (from its Form 16A),
the amount of TDS deducted,
and the relevant certificate / reference detail.

The TAN is the thread that ties the platform’s deduction to your credit. When you enter it, you’re pointing the system at the TDS return where that operator reported tax against your PAN. If you played multiple operators, each has its own TAN and its own line in TDS2 — and because each computes net winnings independently, you can’t merge them. One TAN, one line, per operator.

The relationship between the two schedules is what makes the refund: Schedule OS sets your liability (30% of net winnings), Schedule TDS2 supplies the credit (what was already withheld). The return subtracts the credit from the liability. If the credit exceeds the liability — exactly the Case 1 and Case 2 situations — the excess is your refund.

The schedules in one line: report gross net winnings in Schedule OS under 115BBJ (never the net-of-TDS amount), claim the withheld tax in Schedule TDS2 against each operator’s TAN, and the refund is whatever the credit exceeds the liability by.

How the refund is actually computed and paid

Once the schedules are filled, the arithmetic is mechanical. Here’s the chain from filed return to money in your bank.

Liability is computed. The return applies 30% under Section 115BBJ to the gaming net winnings in Schedule OS, plus tax on any of your other income under its normal rules. For a player whose only income is gaming, the liability is simply 30% of net winnings (no basic exemption shelters it).
Credits are applied. The TDS from Schedule TDS2 (and any other prepaid tax — advance tax, other TDS) is subtracted from the total liability.
The balance is the result. If credits exceed liability, the surplus is your refund. If liability exceeds credits, you pay the shortfall as self-assessment tax before filing. If they’re equal, nothing moves.
Refund is processed after the return is filed and verified. The Income Tax Department processes the return, cross-checks the TDS claimed against 26AS, and — if it validates — credits the refund directly to your pre-validated bank account. As the ClearTax TDS-refund guide explains, the refund is credited after successful filing and processing.

A worked close-out of Case 1: net winnings ₹7,000 → liability ₹2,100. TDS credit from Schedule TDS2 = ₹6,000. Refund = ₹6,000 − ₹2,100 = ₹3,900, credited to your bank after processing.

Two practical realities about the money:

The refund comes once, at filing — not from the app. As multiple guides stress, the TDS refund “can be claimed and received only once in a year at the time of filing your ITR.” The platform never reverses it; only the department refunds it. Don’t wait for the app to give anything back.
Pre-validate your bank account and link PAN–Aadhaar. A refund can only be credited to a pre-validated bank account on the e-filing portal, and your PAN must be linked to Aadhaar for the return to process cleanly. Sort both before filing, or the refund stalls even after a correct return.

For the difference between this — a tax refund you compute and claim — and a payment refund where money never arrived, the refund dispute recovery page covers the non-tax side, and deposit failed recovery covers the deposit-side mirror image.

The refund computation in one line: the return subtracts your TDS credit from your 115BBJ liability, and any surplus is refunded to your pre-validated bank account after filing and processing — once a year, through the department, never from the app.

Deadlines and the e-verification step you cannot skip

A correct return that misses a deadline or goes un-verified is worthless. These dates govern the whole claim for AY 2026-27 (the year for FY 2025-26 income), per the ClearTax due-date guide and Tax2win’s deadline guide.

31 July 2026 — last date to file ITR-1 and ITR-2 for non-audit taxpayers. Most players filing ITR-2 to reclaim gaming TDS face this date.
31 August 2026 — last date for ITR-3 / ITR-4 for taxpayers not subject to tax audit (a date that’s seen extensions in some years; check the portal close to the deadline).
E-verify within 30 days of filing. This is the step people forget. A filed-but-unverified return is treated as not filed — the refund clock doesn’t even start. You verify via Aadhaar OTP, net banking, or the EVC route on the portal.
Belated return: until 31 December 2026. Miss 31 July and you can still file a belated ITR-2 until 31 December 2026, but with a late fee (₹1,000 if income ≤ ₹5 lakh, up to ₹5,000 above) and delayed refund processing — the department prioritises on-time returns.
Revised return: until 31 December 2026 as well, to correct a filed return.
Updated return window extends further for some corrections, but that’s for fixing under-reporting, not a clean refund claim.

The single highest-leverage habit: file on time and e-verify the same day. Late filing not only attracts a fee, it pushes your refund to the back of the queue. And an un-verified return is invisible to the department — the most common reason a “filed” refund never arrives is a forgotten e-verification within the 30-day window.

The deadline rule in one line: file ITR-2 by 31 July 2026 (ITR-3 by 31 August), e-verify within 30 days or the return is treated as never filed, and use the belated window to 31 December 2026 only as a fallback — late and unverified are the two top reasons refunds stall.

The full step-by-step: filing the claim end-to-end

Putting it together, here is the complete sequence from “I think I was over-deducted” to “refund credited.” Each step has the why attached, because a step you understand is a step you won’t skip.

Step 1 — Confirm a refund exists. Run the 60-second diagnostic. Compute full-year net winnings (Rule 133), take 30%, compare to TDS withheld. Only proceed if the withheld figure is higher. If you finished net-positive across an operator, stop — you owe the 30%.

Step 2 — Gather the documents. Download Form 16A from each platform (TRACES / the app’s tax section), and pull your Form 26AS, AIS, and TIS from the income tax portal. You need the operator’s TAN, the TDS amount, and your reconciled net-winnings figure.

Step 3 — Reconcile. Confirm the TDS in Form 26AS matches the platform’s Form 16A. If 26AS is missing the entry or shows a lower figure, chase the platform to correct its TDS return first — you can only claim what’s in 26AS. Don’t file around a gap; fix it.

Step 4 — Pick the form. ITR-2 if no business income, ITR-3 if you have business income. Not ITR-1.

Step 5 — Report income in Schedule OS. Enter the gross full-year net winnings under the 115BBJ “winnings from online games” line. Gross, before TDS. Match it to the income the AIS shows.

Step 6 — Claim credit in Schedule TDS2. One line per operator: TAN, TDS amount, certificate detail. Multiple operators get multiple lines.

Step 7 — Verify the computed refund. The utility computes liability (30% of net winnings) minus credit (TDS2). Confirm the refund figure equals your expected gap. If it shows tax payable instead, you’ve either under-claimed credit (check TDS2) or over-stated income — re-check before submitting.

Step 8 — Pre-validate your bank account. Ensure the refund destination account is pre-validated on the portal and PAN is Aadhaar-linked. No valid account, no refund.

Step 9 — File and e-verify the same day. Submit, then e-verify within 30 days (do it immediately). Un-verified = not filed.

Step 10 — Track the refund. Monitor refund status on the portal. After processing, the department credits the surplus to your pre-validated account. If processing flags a mismatch, it usually traces back to a 26AS-vs-claim gap from Step 3 — which is why Step 3 matters most.

The end-to-end in one line: confirm the refund exists → gather Form 16A + 26AS/AIS/TIS → reconcile → file ITR-2/ITR-3 → gross income in Schedule OS, TDS credit in Schedule TDS2 → pre-validate bank → file and e-verify within 30 days → track — ten steps, and Step 3 (reconcile to 26AS) is the one that prevents stalls.

Multiple operators: why each is a separate claim

A player who used three or four apps in a year has a more involved return, and getting it wrong is easy. The governing fact: each operator is a separate deductor with its own TAN, computing net winnings independently under its own Rule 133 ledger. There is no shared ledger across operators.

The consequences for your claim:

Each operator is a separate line in Schedule TDS2 with its own TAN and TDS amount. You can’t merge them.
Each operator’s net winnings are computed separately, then your Schedule OS income is the sum of the per-operator net winnings (each operator’s figure can’t go below zero — a negative on one operator doesn’t subtract from a positive on another).
A loss on Operator X does NOT offset a win on Operator Y. This is the cross-operator wall again. If you won ₹50,000 net on Dream11 and lost ₹40,000 net on a different app, your taxable gaming income is ₹50,000 (the Dream11 win) — the ₹40,000 loss is simply gone, not subtracted. Your AIS will carry distinct 194BA entries per platform, each standing alone.
Reconcile each operator’s 26AS entry separately. Pull each platform’s Form 16A and match each against its own 26AS line. A mismatch on one operator can hold up the whole refund.

So a multi-operator refund is really several independent computations stacked into one return. The refund, if any, still comes from the timing overshoot within an operator (Case 1) — never from netting a loss on one app against a win on another. That cross-operator netting does not exist, in your return or anywhere else.

The multi-operator rule in one line: each app is a separate TAN, a separate TDS2 line, and a separate net-winnings computation — you sum the per-operator winnings for Schedule OS, but a loss on one operator never offsets a win on another, so a multi-app refund is several independent claims, not one netted figure.

The 1 April 2026 renumbering: 194BA becomes Section 393(3)

A note for anyone filing across the change, because the citation on your documents shifts even though the math doesn’t. India’s new Income-tax Act, 2025 came into force on 1 April 2026, consolidating the scattered 194-series TDS provisions into a single Section 393.

For gaming, per the India Briefing guide to Section 393 and the TDSMAN note on 393(3):

194BA is now covered under Section 393(3) of the new Act. The number changes; the substance does not.
The rate stays 30% on net winnings, no threshold. Rule 133’s computation carries over unchanged.
The transaction date decides which section applies. Transactions on or before 31 March 2026 sit under the old Act (194BA); transactions from 1 April 2026 fall under Section 393(3).

For a refund claim this is purely cosmetic. The refund math — 30% liability minus TDS credit — is identical. The only difference is the section cited on your TDS certificate and in your return for the newer year. Players feel nothing at the wallet. We flag it only so a 393(3) reference on a 2026-27 certificate doesn’t read as an error.

The 2026 renumbering in one line: from 1 April 2026 the gaming-TDS rule moves from Section 194BA to Section 393(3) of the new Income-tax Act, 2025 — same 30% on net winnings, no threshold, same refund math, just a new section number tied to the transaction date.

Refund vs stuck payout vs deposit failure: three different problems

Because this site is a help cluster, readers arrive conflating three completely different “money missing” situations. Sorting yours into the right bucket on day one saves days at the wrong door. The fix for each lives in a different place.

A TDS over-deduction (this page). The money was correctly withheld as tax, but your annual liability is lower than the withholding, so the excess is refundable. Fix: file your ITR and claim the credit — there’s nobody to complain to, because nothing went wrong. This is a tax recovery.
A stuck or short payout that isn’t tax. The withdrawal is pending past the app’s window, or arrived short for a reason that isn’t a 30% TDS cut. Fix: that’s a payment problem — work the escalation ladder in refund dispute recovery, and for the withdrawal mechanics see the 3 Patti withdrawal guide. Filing an ITR does nothing for a stuck payout.
A failed deposit (money left your bank, chips never credited). That’s the deposit-side mirror image — a payment failure on the way in, not a tax matter at all. Fix: the deposit failed recovery page walks the UPI/bank dispute.

The tell between “tax” and “payment problem” is simple: if the missing amount is roughly 30% of your net winnings, it’s TDS — and your only question is whether it’s refundable (the rest of this page). If the whole payout is missing, or the shortfall doesn’t match a 30% cut, it’s a payment problem, and an ITR won’t touch it. For how minimums, fees, and a TDS cut interact on a single small payout specifically, minimum withdrawal and charges breaks down the components.

The three-buckets rule in one line: a TDS over-deduction is recovered by filing your ITR; a stuck/short payout is a payment problem worked through refund dispute recovery; a failed deposit is the deposit-side dispute — only the first is a tax refund, and the 30%-of-net-winnings test tells them apart.

Common mistakes that kill a gaming TDS refund

Even players with a genuine refund lose it to predictable errors. Here are the recurring ones, each with the fix.

Filing for a refund on a net-positive year. The most common false hope. You won for the year, so the 30% is owed and there’s no refund. Fix: run the diagnostic first; only a timing overshoot (Case 1/2) produces a refund.
Expecting losses to offset across operators. They don’t. A loss on App B never reduces tax on a win at App A. Fix: accept the cross-operator wall; net only within one operator, in the same year.
Reporting net-of-TDS income in Schedule OS. Entering the ₹14,000 that landed instead of the ₹20,000 gross under-states income and triggers a mismatch with 26AS. Fix: always report the gross net winnings; claim the TDS separately as credit.
Claiming TDS that isn’t in 26AS yet. If it’s in your AIS but not 26AS, you can’t claim it. Fix: chase the platform to file a corrected TDS return before you file your ITR.
Filing ITR-1 with gaming income. ITR-1 has no 115BBJ field. Fix: use ITR-2 (or ITR-3 with business income).
Forgetting to e-verify within 30 days. A filed-but-unverified return is treated as not filed; the refund clock never starts. Fix: e-verify the same day you file.
No pre-validated bank account / unlinked PAN-Aadhaar. The refund has nowhere to go. Fix: pre-validate the account and link PAN-Aadhaar before filing.
Mixing up the 28% GST with the 30% TDS. GST sits on deposits (way in) and is generally not recoverable; only the 30% TDS on winnings (way out) is refundable. Fix: don’t try to “reclaim” GST the way you reclaim TDS — see online gaming tax India 2026 for the GST side.

The mistakes in one line: don’t file on a winning year, don’t expect cross-operator offset, don’t report net-of-TDS income, don’t claim TDS missing from 26AS, don’t use ITR-1, don’t forget e-verification, don’t skip bank pre-validation, and don’t confuse GST with TDS — eight errors that each sink a refund.

A note on PROGA 2025 and balance-recovery refunds

The legal backdrop changed everything about new deposits, but not about old TDS. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) banned online money games where you stake money for a return, and the major operators suspended cash play from late 2025. So a live question is: if I’m recovering a stranded balance from a wound-down app, and TDS was deducted on it, can I still claim the refund?

The short answer: yes, the TDS refund mechanism is unchanged for a legitimate balance recovery. TDS deducted on net winnings — whether at a withdrawal while the app was live, at a year-end sweep, or on a recovery payout — still lands against your PAN, still shows in 26AS, and is still reconciled and claimed the same way in your ITR. PROGA banned new deposits; it didn’t repeal the income-tax treatment of winnings already earned. What you must not do is deposit fresh money into a discontinued cash game to “unlock” anything — that’s now illegal and separate from any tax question. For the full legal picture, see the online gaming tax India 2026 and TDS on online gaming explainers.

The PROGA note in one line: a balance-recovery payout that carried net winnings is taxed and refunded exactly like a live-app withdrawal — TDS lands against your PAN, claimable in your ITR — but a fresh deposit into a discontinued game is now illegal, so recover, never re-deposit.

The reverse problem: the platform did NOT deduct TDS

There’s a mirror-image situation that no refund page warns about, and it bites the unprepared at filing. Suppose you won, but the app never deducted the 30% — because it was an informal, unlicensed, or offshore operator that simply ignored the rule, or because your net winnings stayed inside the ₹100 monthly deferral and were never swept. You’d assume that’s good news. It isn’t, and here’s why.

The tax is owed on your net winnings whether or not the platform withheld it. Section 115BBJ charges the 30% on the income; Section 194BA is only the collection mechanism. If the platform skipped collection, the liability didn’t vanish — it lands on you at filing. So a player who won ₹50,000 net on an app that deducted nothing still owes ₹15,000 when they file, and they owe it as self-assessment tax paid before submitting the return, not as a refund-able credit.

This creates three traps:

You can’t claim a credit that doesn’t exist. Schedule TDS2 only credits TDS that’s actually in your 26AS. If nothing was deducted, there’s nothing in 26AS, so there’s nothing to credit — and the full 30% comes out of your pocket at filing.
The income is still visible to the department. Even where the platform didn’t deduct, the winnings can surface in your AIS (platforms report transactions, not just TDS). A win in the AIS with no matching return is exactly the pattern that draws a notice. As the CAalley note on real-money gaming ITR warns, unreported gaming earnings risk tax notices and, in serious cases, prosecution.
There’s no refund here — only a bill. Players sometimes arrive at a “refund” page expecting money back, when their actual position is that they owe tax the app never collected. The honest answer is to compute the 30%, pay it as self-assessment tax, and file clean.

The practical rule: a missing TDS deduction is not a windfall and not a refund opportunity. It’s an unpaid liability you must settle yourself. The only genuine refund cases remain the two timing-overshoot scenarios in Cases 1 and 2 — both of which require that TDS was actually deducted and over-shot your annual figure.

The reverse-problem rule in one line: if the platform never deducted TDS, you still owe the 30% under Section 115BBJ — paid as self-assessment tax before filing, with no credit and no refund — and an undeclared win sitting in your AIS is exactly what triggers a notice.

Recordkeeping built specifically for the refund claim

The players who get refunds cleanly are the ones who kept the right records as the year went, because a Rule 133 reconciliation can’t be rebuilt from memory in July. This list is narrower than a general tax checklist — it’s exactly what a refund claim needs to survive scrutiny.

Every withdrawal confirmation (your A term). Each shows the date, amount, and ideally the net winnings and TDS inside that withdrawal. These are what let you prove the timing overshoot in Case 1 — that a winning withdrawal was taxed early before a later loss.
Every deposit confirmation from your own bank (your B term). Your real deposits are subtracted in Rule 133, so each one reduces taxable net winnings. Crucially, keep proof they came from your own account — that’s what distinguishes a non-taxable deposit (subtracted) from a bonus credit (not subtracted).
Wallet screenshots on 1 April and 31 March (your C and D terms). The opening and closing balances bookend the formula. They’re trivial to capture and impossible to recover once a new year starts. For Case 2, a 31 March screenshot showing what was cashable versus a non-withdrawable bonus is the evidence that a year-end sweep over-stated D.
Every Form 16A TDS certificate, per operator, per quarter. This is the document you carry into Schedule TDS2 and reconcile against 26AS. Without it you can’t prove what was withheld, and you can’t chase a 26AS gap.
A simple per-operator running tally. One row per operator: deposits, withdrawals, closing balance, TDS deducted. Because each operator computes independently and a loss on one never offsets a win on another, you need each operator’s figures kept separate, not pooled.

Hold these for several years — the period a return can be reopened — because if the department queries a gaming-income entry or a refund claim, these confirmations are what resolve it. The single most useful pre-filing habit is the four-way reconciliation: Form 16A against 26AS against AIS against your own tally. When all four agree, the refund computes without friction; when they don’t, the gap is exactly what you fix before filing.

The recordkeeping rule in one line: save withdrawal and deposit confirmations (A and B), 1 April / 31 March wallet screenshots (C and D), and every operator’s Form 16A — then reconcile all four sources, because a refund claim is only as strong as the Rule 133 inputs you can prove.

”Gaming TDS recovery agents”: the scam to avoid

A predictable industry has grown around gaming TDS refunds — operators on social media and messaging apps promising to “recover your full gaming TDS” for a fee or a cut. Most are selling something that doesn’t exist, and some are outright fraud. Knowing the tells protects both your money and your tax record.

The core lie is the one this whole page rebuts: that the 30% on a winning year is recoverable. It is not. A genuine refund exists only when withholding overshot your annual liability (Cases 1 and 2). Anyone promising to “get back” TDS on a year you finished ahead is either going to file a false return in your name — understating your income to manufacture a refund, which is your liability and your prosecution risk when it’s caught — or simply take a fee and vanish.

The red flags, each with the reason it’s a problem:

“We guarantee a refund of your full TDS.” Impossible on a net-positive year. A guarantee on a winning year means a false return.
“Share your income tax portal login / OTP.” Never. A legitimate preparer files with their own credentials or a proper authorisation, never your live login or OTP — that’s account takeover.
“Pay us a percentage of the refund.” Contingency-fee “refund agents” are incentivised to inflate refunds illegitimately. A qualified CA charges a fee for the work, not a cut of a number they’re motivated to fake.
“We’ll show losses to cancel your winnings.” Gaming losses cannot be set off against winnings. Anyone claiming to do this is fabricating entries.

The clean path needs no agent at all for a straightforward claim: reconcile your documents, file ITR-2/ITR-3 yourself or with a named, qualified chartered accountant, report the gross winnings, claim the real TDS, and let the department compute the genuine refund. If your situation is complex — multiple operators, business income, in-kind prizes — pay a real professional for real work. But never hand your portal access or your honesty to someone promising the impossible. For the broader pattern of gaming-money scams and how to spot them, the recovery cluster on this site walks the red flags in detail.

The scam-avoidance rule in one line: nobody can “recover” TDS on a winning year — a guaranteed full refund, a request for your portal login or OTP, a cut-of-the-refund fee, or a promise to “show losses against winnings” are all signs of a false-return scam that becomes your liability, so file the honest figure yourself or with a named CA.

Tracking the refund after you file: what the statuses mean

Filing isn’t the end — the refund moves through processing stages, and knowing them tells you whether to wait or to act. You track it on the income tax e-filing portal under your filed return.

The typical progression:

Return submitted, pending verification. You’ve filed but not e-verified. The refund clock has not started. Resolve this immediately by e-verifying within the 30-day window — an unverified return is invisible to the department.
Successfully verified / under processing. The department has your verified return and is matching it — including cross-checking your Schedule TDS2 claim against 26AS. This is where a 26AS-vs-claim gap surfaces, which is why pre-filing reconciliation matters.
Processed with refund determined. The department agrees a refund is due and has computed the amount. The credit to your pre-validated bank account follows.
Refund issued / credited. The money is sent to your bank. If your account isn’t pre-validated or PAN isn’t Aadhaar-linked, this is where it stalls even on a correct return.
Refund failed / on hold. Usually a bank-validation or mismatch issue. Fix the bank pre-validation or respond to any notice, then the refund re-issues.

Two timing realities. First, on-time returns process faster — the department prioritises returns filed by the due date, so a belated return’s refund waits longer. Second, the refund comes once a year, at processing — there’s no partial or rolling refund, and nothing comes from the app at any point. If processing flags a mismatch, it almost always traces to the TDS-vs-26AS gap, so the fix is upstream: reconcile before you file.

The tracking rule in one line: a refund moves from pending verification → processing → refund determined → credited, the clock only starts after e-verification, on-time returns process fastest, and a stall almost always means a bank pre-validation gap or a TDS-vs-26AS mismatch to fix.

Worked example: reconciling a messy multi-withdrawal year

Real years aren’t clean — deposits and withdrawals interleave, and the per-withdrawal TDS rarely matches the annual figure. Here’s a fuller reconstruction that shows exactly where a refund hides, using one operator across a single financial year.

The activity, in order:

May: deposit ₹20,000 of your own money. Play, win, and withdraw ₹40,000. The net winnings in that withdrawal compute to ₹20,000, so the platform deducts 30% × ₹20,000 = ₹6,000 and pays ₹34,000.
September: deposit a further ₹25,000 from your bank. Play, and withdraw ₹10,000. By now cumulative deposits are ₹45,000 and cumulative withdrawals ₹50,000; the cumulative formula (subtracting the ₹20,000 already taxed) shows no new net winnings in this withdrawal, so no TDS is taken on it.
October–March: you keep playing on the September deposit, lose most of it, and withdraw nothing more.
31 March: closing wallet balance is ₹3,000.

Now the full-year Rule 133 reconciliation, (A + D) − (B + C):

A = total withdrawn = ₹40,000 + ₹10,000 = ₹50,000
D = closing balance = ₹3,000
B = your own deposits = ₹20,000 + ₹25,000 = ₹45,000
C = opening balance = ₹0

Net winnings = (50,000 + 3,000) − (45,000 + 0) = 53,000 − 45,000 = ₹8,000

Your true full-year net winnings are ₹8,000, so your final liability under Section 115BBJ is 30% × ₹8,000 = ₹2,400. But the platform already withheld ₹6,000 back in May, on the ₹20,000 that looked like net winnings at the time — before the later deposit-and-loss dragged your annual position down. The refund is ₹6,000 − ₹2,400 = ₹3,600, recovered when you file.

The lesson the messy year teaches: the per-withdrawal TDS is a running estimate, not the final word. It taxes what looked like profit at each moment. Your annual net winnings — the only figure that decides your real liability — can be much lower once a full year of deposits and losses is netted. The gap between the two is your refund, and it only ever appears at filing, because the platform can’t see the future losses when it withholds. Report the ₹8,000 in Schedule OS, claim the ₹6,000 in Schedule TDS2, and the return computes the ₹3,600 back.

The messy-year lesson in one line: per-withdrawal TDS is a running estimate taxing what looked like profit at the time, while your annual net winnings (₹8,000 here) set the real liability — the gap (₹6,000 withheld minus ₹2,400 owed = ₹3,600) is the refund, visible only at filing.

If you already filed wrong: revised and belated returns

Mistakes happen — you reported net-of-TDS income, forgot a Schedule TDS2 line, or missed the deadline entirely. The system gives you two repair routes, and knowing which applies saves the refund.

You filed on time but got it wrong → revised return. If you’ve already filed but realise you under-claimed TDS, mis-stated income, or left out an operator, you can file a revised return to correct it. For AY 2026-27, the revised-return window runs until 31 December 2026. A revised return fully replaces the original, so re-enter everything correctly — the corrected Schedule OS figure and every Schedule TDS2 line — and re-verify it. The refund then computes off the corrected return.
You missed the deadline entirely → belated return. If you never filed by 31 July (ITR-2) and the income is real, you can still file a belated return until 31 December 2026, with a late fee (₹1,000 if income ≤ ₹5 lakh, up to ₹5,000 above) and slower refund processing. A belated return still lets you claim the TDS credit and recover a genuine refund — it just costs the fee and pushes you down the processing queue.

Two cautions. First, don’t keep revising to chase a refund that isn’t there — repeated revisions on a winning year won’t manufacture a refund and may draw scrutiny. Fix a genuine error once, correctly. Second, after any revised or belated filing, re-do the e-verification within 30 days; the un-verified trap applies to corrected returns exactly as it does to the first one. The repair routes are forgiving, but only if you verify what you fix.

The repair rule in one line: a revised return (until 31 December 2026) corrects an on-time filing, a belated return (same date, with a late fee) rescues a missed deadline — both let you still claim a genuine TDS refund, but you must re-verify within 30 days, and no amount of revising creates a refund on a winning year.

Frequently asked questions

1. Can I get a refund on the 30% TDS deducted from my gaming winnings?

Only if your full-year net winnings tax (30%) comes out lower than the TDS already withheld. The usual case: an early winning withdrawal was taxed (say ₹6,000), then you lost later, so your true annual net winnings — and the 30% on them — drop below ₹6,000. The gap refunds through your ITR. If you finished the year net-positive across an operator, the 30% is owed and there’s no refund.

2. When is a gaming TDS refund actually possible?

In two situations. One: the win-then-lose sequence — a winning withdrawal taxed early, followed by deposits-and-losses that drop your annual net winnings (e.g. ₹6,000 withheld but only ₹2,100 truly owed → ₹3,900 refund). Two: a year-end over-deduction, such as the 31 March sweep withholding on an over-stated balance (a non-cashable bonus wrongly counted), where your reconciled net winnings are lower. Both recover only at filing.

3. Can I set off my gaming losses against my winnings to reduce the tax?

No — not across operators or years. Under Section 115BBJ, gaming losses cannot be set off against winnings or any other income and cannot be carried forward. The only netting is within one operator’s accounts in the same year, via Rule 133. A ₹40,000 loss on App B does nothing for a ₹50,000 win on App A — you’re taxed on the full ₹50,000.

4. Which ITR form do I use to claim a gaming TDS refund?

ITR-2 if you have no business income (most players), or ITR-3 if you also run a business. The simple ITR-1 cannot be used — it has no field for Section 115BBJ gaming income. If you’d normally file ITR-1, you must step up to ITR-2 to report the winnings and claim the credit.

5. Where do I report the gaming winnings, and where does the TDS credit go?

Report the gross net winnings in Schedule OS under Section 115BBJ — the figure before TDS, not the smaller amount that reached your bank. Enter the TDS credit in Schedule TDS2, with the operator’s TAN and the deducted amount. The return subtracts the TDS2 credit from the Schedule OS liability; any surplus is your refund.

6. Why must I report the gross figure, not what landed in my bank?

Because your 26AS shows TDS computed on the gross net winnings. If you report the net-of-TDS amount (e.g. ₹14,000 instead of ₹20,000), you under-state income and create a mismatch with 26AS, which can trigger a defective-return notice. Report the gross ₹20,000 in Schedule OS and claim the ₹6,000 TDS separately as credit.

7. How does the platform’s TDS show up so I can claim it?

The platform issues a Form 16A TDS certificate (from TRACES, usually quarterly), and the deduction appears under Section 194BA in your Form 26AS and your AIS on the income tax portal. You can only claim credit from 26AS — if the TDS is in AIS but missing from 26AS, you must get the platform to file a corrected return before you can claim it.

8. What if the TDS in my 26AS doesn’t match the platform’s certificate?

Stop and fix it before filing. You can only claim the TDS that actually appears in 26AS against your PAN. If the platform’s Form 16A says ₹6,000 but 26AS shows ₹0 or a lower figure, chase the platform to file a corrected TDS return. Filing your ITR around the gap will hold up the refund or fail validation.

9. How is the refund computed and how is it paid?

The return applies 30% to your net winnings (Section 115BBJ), then subtracts your TDS credit (Schedule TDS2). If credit exceeds liability, the surplus is refunded. Example: ₹7,000 net winnings → ₹2,100 owed; ₹6,000 withheld → ₹3,900 refund, credited to your pre-validated bank account after the department processes the return. The refund comes once a year, at filing — never from the app.

10. What are the deadlines for AY 2026-27?

File ITR-2 by 31 July 2026 (non-audit), or ITR-3 by 31 August 2026. E-verify within 30 days of filing or the return is treated as not filed. If you miss 31 July, a belated return is allowed until 31 December 2026 with a late fee and slower refund, and you can revise until 31 December 2026 too. File on time and verify the same day for the fastest refund.

11. I never withdrew but my wallet shrank in April — can I refund that?

That April drop is the year-end 194BA sweep, taxing net winnings parked in your wallet on 31 March. It’s usually correct and not refundable. A refund only appears if the swept balance was over-stated — for instance a non-cashable promotional credit wrongly counted in the closing balance inflating the tax — in which case the excess refunds when you file with the corrected figure.

12. I have a low income overall. Can I avoid the 30% on my gaming win?

No. Gaming winnings under Section 115BBJ are taxed at a flat 30% with no basic-exemption shelter, no slab benefit, no Section 87A rebate, and no deductions. Even if your total income is below the taxable threshold, the gaming win is still taxed at 30%. The basic exemption that protects ordinary income does not apply to this category.

13. I played on several apps. Do I file one claim or several?

It’s several computations in one return. Each operator has its own TAN and its own Schedule TDS2 line, and each computes net winnings independently. You sum the per-operator net winnings for Schedule OS (no operator’s figure goes below zero), and reconcile each platform’s 26AS entry separately. A loss on one app does not offset a win on another.

14. Does the 28% GST on deposits also get refunded?

No. The 28% GST sits on your deposits going in and is an indirect tax that’s generally not recoverable by a player. Only the 30% TDS on winnings going out is refundable, and only when withholding overshot your liability. Don’t try to “claim back” GST the way you claim TDS — they’re different taxes in opposite directions. See online gaming tax India 2026 for the GST side.

15. The whole withdrawal is missing, not just 30% — is that a refund I file for?

No — that’s a stuck payout, not a tax matter, and an ITR won’t touch it. A TDS deduction is roughly 30% of your net winnings; if the entire withdrawal is gone, or the shortfall doesn’t match a 30% cut, it’s a payment problem. Work the refund dispute recovery ladder, and for the withdrawal mechanics see the 3 Patti withdrawal guide.

The bottom line

A gaming TDS refund is not “getting your 30% back” — it’s recovering the gap between what was withheld and what you actually owe on full-year net winnings. That gap exists only in two real cases: an early winning withdrawal taxed before a later loss (Case 1), or a year-end over-deduction on an over-stated balance (Case 2). In both, you recover it the same way: file ITR-2 or ITR-3, report gross net winnings in Schedule OS under Section 115BBJ, claim the TDS in Schedule TDS2 against each operator’s TAN, pre-validate your bank account, and file and e-verify by the deadline. The refund is the surplus of credit over liability, paid once a year by the department, never by the app.

And the honest close: most players who finished a year ahead owe the 30% and have no refund — gaming losses don’t offset winnings across operators or years, there are no deductions, and the flat 30% has no slab relief. Knowing which side of that line you’re on, before you file, is the whole skill. If your missing money isn’t a 30% TDS cut at all, it’s a payment problem — work refund dispute recovery, deposit failed recovery, or the 3 Patti withdrawal ladder instead.

Reminder: this is not tax advice. It is a sourced explainer built from Section 194BA / Rule 133, CBDT Circular 5/2023, and the income tax e-filing portal. Your own return may differ — multiple operators, business income, surcharge thresholds, in-kind prizes all change the picture. For your actual filing, consult a qualified chartered accountant. For the law behind the 30%, see TDS on online gaming; for the full tax picture including GST, see online gaming tax India 2026.

Run your case through the diagnostic