The withdrawal walkthrough, step by step.

The full chapter, in one read

Withdrawals are the part of fantasy cricket that gets the least editorial coverage and the most user complaints. The flow is simple on paper, the platform routes the payout through a payment aggregator, and the aggregator clears it through your bank or UPI handle. In practice, the moving parts are: KYC, PAN verification, bonus rollover, and the bank-side settlement window.

The page below is the walkthrough we wish we had on day one. It covers the happy path, the most common stalls, and the support contacts we have used ourselves.

What you should do next

The fastest way to use this chapter is to read the first subtopic, then jump to whichever subtopic matches the question on your mind. If you are new, the captain and vice-captain subtopic is the one that pays for itself the soonest. If you are returning, the salary cap math subtopic is usually where the season-end edge sits.

We update this chapter weekly. The date below the headline is the last refresh; the changelog at the bottom of the guide records every substantive change.

The KYC walkthrough, in detail

The KYC walkthrough is a four-step process. Step one: mobile number verification, which is done at sign-up. Step two: PAN, which is required for any withdrawal above ₹10,000. Step three: Aadhaar last-four, which is used for identity verification. Step four: UPI handle or bank account, which is used for deposits and withdrawals. The four steps are sequential.

The UPI vs bank transfer reading, in detail

UPI is the fastest withdrawal method, with 30 minutes to 4 hours clearance. The bank transfer is the fallback, with 24-48 hours clearance. The UPI handle is set at the deposit screen; the bank account is set in the account settings. The platform routes the withdrawal to the most recent method used for the deposit.

The PAN above ₹10,000 rule, in detail

The Indian tax rule requires PAN verification for any withdrawal above ₹10,000. The platform’s TDS workflow is triggered by the rule, and the TDS is reflected in the user’s Form 26AS and AIS. The ITR declaration is on the user’s side; the platform provides the TDS certificate after the financial year ends.

The bonus rollover reading, in detail

The bonus rollover is the number of times the bonus must be used in a contest before it can be withdrawn. A 4x rollover on a ₹1,000 bonus means ₹4,000 of contest entry must be paid from the bonus before the bonus can be withdrawn. The rollover is calculated on the bonus amount, not on the deposit. The full rollover reading is on the bonus code page.

What to do when a payout stalls, in detail

When a payout stalls, the first check is the UPI handle: is the UPI handle still active? The second check is the KYC: is the KYC verified? The third check is the bonus rollover: is the bonus rollover complete? The fourth check is the bank account: is the bank account still active? If all four checks pass and the payout still stalls, contact the customer care team. The contact list is on the customer care page.

How the editorial desk keeps this guide accurate

The editorial desk re-verifies the content on this guide every week. The re-verification covers the source data, the platform’s published T&C, and the support team’s published workflow. If any of the three changes, the page is updated within an hour. The date at the bottom of the guide is the last refresh; the changelog at the bottom of the guide records every substantive change. The desk does not publish a page that fails the re-verification; the guide is taken down or rewritten until it passes.

The editorial desk uses a four-step re-verification process. Step one: the source data is checked against the public database. Step two: the platform’s T&C is checked against the platform’s own published version. Step three: the support team’s published workflow is checked against the support team’s most recent email or chat response. Step four: the editorial content is checked against the three sources. The four steps are the minimum; the desk does not skip a step.

What to do if you spot an error

If you spot an error on this guide, send a one-line email to [email protected] with the subject line “Fact correction”. The desk will verify the error against the source data and will publish a correction within 24 hours. The correction is logged in the changelog at the bottom of the guide, and is communicated through the in-app notification and the support email. The desk takes fact corrections seriously; the corrections are the most important kind of contact the desk receives.

If the error is a typo, the desk will fix the typo within 24 hours. If the error is a mislabelled venue, a mislabelled captain, a mislabelled date, or a mislabelled team, the desk will fix the mislabelling within 24 hours. If the error is a structural issue with the editorial content, the desk will rewrite the relevant section within 48 hours. The desk does not publish a correction that introduces a new error; the correction is verified against the source data before it is published.

How the desk handles commercial relationships

LeagueX carries affiliate links to the platform’s own app. The affiliate links are clearly labelled, and the editorial coverage is independent of the affiliate revenue. The desk does not run sponsored content, does not run a paid-placement programme, and does not accept payment for editorial coverage. The full disclosure is on the responsible play page. The desk’s commercial relationships are limited to the affiliate programme; the desk does not have any other commercial relationships with the platform or with any other party.

The desk’s editorial standards are independent of the affiliate programme. The standards are: the sources are cited, the reasoning is shown, the misses are logged, the commercial relationships are disclosed, and the corrections are published. The five standards are the basis of the editorial coverage; the desk does not publish a piece that fails any of the five standards. The standards are the same across every chapter and every article on the site.

The five editorial standards, in detail

Standard one: the sources are cited. Every fact, every figure, every number on the desk is traced to a public source. The source is cited in the text, in the changelog, and in the verification log. The desk does not publish a fact that cannot be traced to a public source. Standard two: the reasoning is shown. Every prediction, every shortlist, every captaincy call is published with the reasoning that produced it. The reasoning is shown in full, not summarised. Standard three: the misses are logged. Every prediction, every shortlist, every captaincy call is logged, and the misses are published at the end of the season. The misses are the most important data point on the desk.

Standard four: the commercial relationships are disclosed. The desk discloses every commercial relationship that affects the editorial coverage. The disclosure is on the responsible play page and on the about page. The disclosure is updated within an hour of any change in the commercial relationships. Standard five: the corrections are published. Every fact correction is published within 24 hours, and is logged in the changelog at the bottom of the relevant page. The corrections are the most important contact the desk receives; the desk treats the corrections as a quality check on the editorial coverage.

What to read next

If you want to keep reading, the fantasy cricket reading order is the most useful starting point. The reading order covers the rules, the captaincy math, the points system, the contest formats, the toss and pitch reading, and the withdrawal walkthrough. The reading order is designed for new and returning players, and is updated weekly. If you want to play, the download path is the fastest one. The free practice contests are open all year and do not require a deposit. The editorial calendar is on the same URL every week.

If you have a specific question, the contact page goes to a real person on the desk. The desk answers within two working days. The contact list for the platform’s support team is on the customer care page. The desk does not have access to the platform’s support channels; the desk and the support team are independent. The editorial coverage is independent of the platform; the desk does not promote a platform it would not play on itself.