Shuffle account verification guide

Verification in practice

Shuffle runs a staged identity model: email confirmation, then three numbered levels, described in its account verification article and its KYC guide. The front of the funnel is genuinely light. The back of it is open ended, and the gap between those two facts is what a prospective depositor needs to understand.

The levels, document by document

• Level 1, Basic Information. Full legal name, date of birth, address with city, country and postal code, and occupation. No documents.
• Level 2, Identity Verification. One item issued by a government: a passport, a national identity card, a driving licence or a residence permit.
• Level 3, Proof of Address. One document dated inside the previous three months. The listed options are a utility bill, a bank or credit card statement, a signed lease, a letter from a public authority, a tax bill, a mortgage statement or a voter registration certificate.

Funding an account needs email confirmation plus Level 1 only, per the deposit article. Nothing is scanned or uploaded to make a first deposit, which is exactly what the homepage markets when it promises registration, deposit and play inside minutes while conceding that further checks may apply.

What triggers the escalation

No monetary threshold is published. The operator states only that verification is risk based and staged, and that further stages may be requested according to how an account looks in the round. Contractually, clause 4 of the Terms of Service permits verification at any time and clause 9.4 permits additional verification tied to any withdrawal.

The AML policy sets the framework: a written anti money laundering and counter terrorist financing programme built on Curacao regulatory guidance, a Chief Compliance Officer reporting to the board with authority to file suspicious transaction reports with the Curacao Financial Intelligence Unit without prior approval, risk based customer due diligence, ongoing transaction monitoring and staff training.

The data set it records is wallet address, name, address, country, date of birth and postal code. Source of funds is not itemised as a separate published stage, but the policy's risk based language and the complaint record both point to document requests that go beyond the three levels when an account looks unusual.

The asymmetry

Shuffle publishes no turnaround commitment for reviewing what you send. Its stated position is that review times vary with volume and document quality. Set that against a contractual right to demand documents at any moment, including mid payout, and the balance is one sided: your obligation is immediate, the operator's is undefined.

There is no service level to hold it to, and no regulator imposed clock in the published licence conditions.

What that looks like in practice is on the record.

Published complaints describe Level 3 requests and live verification requests arriving only once a payout had been asked for, one manual review that ran beyond 24 days, another of roughly three weeks, and chat access withdrawn while the file sat open, across Casino Guru player reviews and AskGamblers complaints, including one case titled around verification neglected for over 20 days.

A separate case page about a payment in review with documents unverified shows the platform's own counters of 22 of 31 resolved and a two day average first response, which is a response clock rather than a resolution clock.

Two details that reward doing this early

First, the third party card ramps MoonPay and Swapped run their own separate checks, and those do not advance your Shuffle levels, so a card buyer who has already been verified elsewhere still starts at Level 1 here.

Second, verification has a direct financial value on this site: completing Level 2, or Level 3 where Shuffle asks for it, halves the wager to vest requirement on Airdrop 3 tokens, per the airdrop documentation.

The rational play is to clear all three levels while your balance is small and nothing is pending, so that the first significant payout request meets a file that is already complete. That does not immunise you against a hold, since the operator's right to check is unconditional, but it removes the most common reason given for one.