Where in the Money Path the Document Request Lands

Identity verification is not a registration step in the documents we read. It is a withdrawal condition. The request arrives when money tries to leave, which means it lands at the one point in the route where the account holder has the least room to do anything about it.

Forty-nine verification clauses were readable across the 100 brands in our reference library. This page sets out what those 49 say, which five put a number in writing, and why a widely repeated figure does not appear in any of them. Terms were read on 26 August 2026.

What do all 49 clauses have in common?

One thing, expressed in different words every time: the decision belongs to the operator. Every clause read reserves the right to request identity documents, and none of them limits that right to a stated situation.

The formulations vary in tone and not in substance. One says the operator “reserves the right to request verification documents before being able to process your withdrawal”. Another says documents “can be required on first deposit, before withdrawals are processed”, and adds that random account health checks are also covered. A third simply says withdrawals “may be terminated until the account is fully verified”.

Not one of the 49 clauses says the operator will not ask.

Which five state an amount?

Brand	Stated figure	Clause
Bitcasino.io	€2,500 or crypto equivalent	6.6
Sportsbet.io	€2,500 or crypto equivalent	6.6
Livecasino.io	€2,500 or crypto equivalent	6.6
Rocketpot	$2,500, or 0.05 BTC	11.4
Empire.io	2,000 USDT or equivalent	5.4

Three of those five carry the same figure under the same clause number, 6.6, which is what happens when brands share a document rather than a policy. Bitcasino.io and Livecasino.io also share a licence number.

And every one of the five hedges. The 2,500-euro clauses add that smaller withdrawals may be checked as well; Rocketpot’s clause names a second figure of $2,000 for additional checks; Empire.io’s says the same about smaller withdrawals required by the gaming licence.

A stated threshold in these documents is a floor above which a check is likely, never a ceiling below which one is ruled out.

What about tiered policies?

One brand in the library publishes a staged scheme rather than a single figure. LeeBet’s anti-money-laundering policy requires a first verification step of every user before any withdrawal, a second step for any withdrawal or for deposits over $2,000, and a third for deposits or withdrawals over $5,000 or transfers over $3,000 — while reserving the right to request documents at any time regardless.

That document carries no clause numbering at all, so the figures above are cited to the policy page rather than to a numbered term.

Why does the figure quoted everywhere else not appear here?

A round number in the region of $5,000 circulates widely as the point at which crypto casinos start asking for documents. It does not appear as a general threshold in any of the 49 clauses we read.

The figures that do appear in the documents are €2,500, $2,500, 2,000 USDT, and the staged $2,000 / $3,000 / $5,000 scheme of a single operator’s AML policy. Five brands out of a hundred state anything at all.

Where a number is repeated across review sites but sits in no operator’s terms, the number has no source. We publish what the clause says or we publish nothing.

How many of these clauses can even be cited?

Twenty-seven of the 49 carry a clause number that a reader can quote back. The other 22 were readable but unnumbered — a policy page, an FAQ answer, or a block of terms without numbering.

That distinction matters more than it looks. A numbered clause is a reference; an unnumbered paragraph on a page that can be rewritten silently is not.

Where exactly does the request sit in the route?

At the fifth hop of six. The money has already left the bank, already been converted, already crossed a chain and already been credited to an internal balance before the operator’s clause becomes relevant. The full sequence is set out on our page about the rupee route.

Three consequences follow from the position rather than from the wording:

• The balance is inside the operator’s ledger when the request arrives. It is not on a chain and not in a wallet, so nothing about it can be moved by the account holder while the request is open.
• Every earlier hop is already recorded elsewhere. The exchange at the start of the route is a reporting entity under the Prevention of Money Laundering Act, 2002 following the Ministry of Finance notification of 7 March 2023, so the identity question was answered once before the coin ever moved.
• The withdrawal ceiling and the verification hold interact. A capped payout runs over several periods, and a request that arrives mid-sequence stops the remainder; the published ceilings are tabulated on our page about withdrawal limits.

What the clauses say happens while a request is open

The withdrawal does not proceed. Several of the clauses read say so in terms — the payout is held, or terminated, until verification is complete — and none of them commits the operator to a deadline for reviewing what is submitted.

No clause in the library states a maximum review time. That field is empty across all 49, and an empty field here means the document does not say, not that review is instant.

What this page does not cover

It gives no method for avoiding, delaying or influencing a verification request, and it takes no position on whether any reader should open an account anywhere. It describes what the operators’ own documents say about a step in their process.

Whether money may lawfully take this route at all is a question of Indian statute rather than of any operator’s terms, and it is summarised in the legal note on our USDT and verification guide. Nothing here is legal advice.