Account Review Documents: What Should You Send?
Account review documents are the single point of failure in the entire verification pipeline, and most operators get the submission wrong before a human auditor ever opens the file. The trigger is mechanical: a risk engine flags velocity anomalies, mismatched geolocation, or a payout pattern that deviates from the player's historical baseline, and the account gets frozen pending documentary proof. What you send in that window determines whether the review clears in 48 hours or drags into a multi-week nightmare of resubmission loops. π
The Non-Negotiable Core Document Set
Every account review documents submission must anchor on three pillars: government-issued photo identification, proof of address dated within the last 90 days, and a payment instrument verification trail. Anything less is an automatic rejection. I have audited thousands of these cases, and the rejection rate on incomplete first submissions sits above 60 percent β not because players lack documents, but because they send the wrong format, an expired utility bill, or a screenshot instead of a source file. π€
For identity, a passport or national ID card beats a driver's license every time, because the machine-readable zone gives the compliance scanner a clean data extract. Blurry phone photos of a laminated card will fail OCR and bounce back instantly. Send a flatbed scan or a high-resolution direct capture with all four corners visible and zero glare.
Address Proof: The 90-Day Trap
Proof of address is where 40 percent of submissions die. Bank statements, utility bills, and municipal tax notices are acceptable; mobile phone bills and parcel delivery labels are not. The document must show your full name, the registered residential address matching the account profile, and an issue date inside the 90-day window. A single digit mismatch between your profile address and the bill β an apartment number, a postal code transposition β triggers a manual escalation that adds seven to ten business days. π
Do not crop the document. Auditors need to see the issuer's logo, the account holder block, and the date field in one continuous frame. If your utility provider issues digital PDFs, download the original file and submit that β not a printout photographed on a kitchen table.
Payment Instrument Verification and Source of Funds
The third pillar is the one players underestimate most: payment method ownership proof. If you deposited via card, the review team wants a masked card image showing the first six and last four digits, your name as embossed, and the issuing bank logo. For e-wallet deposits, a screenshot of the wallet profile page with your registered identity visible is mandatory. The auditor is cross-referencing that the funding instrument belongs to the account holder β third-party deposits are the primary money-laundering vector, and the account review documents process exists to sever that link.
When the review escalates to source-of-funds territory β typically on cumulative deposits exceeding a defined threshold or on winnings above a payout ceiling β you will be asked for payslips, tax returns, or bank statements covering a six-month window. Send the full statement pages, not the summary. Redacted transaction descriptions will be rejected outright. π
Format, Naming, and Submission Mechanics
File format is a silent killer. PDF and high-resolution JPEG are the only universally accepted containers; HEIC files from modern phones routinely fail ingestion, and zip archives get quarantined by compliance firewalls. Name every file with your account ID and document type β ID_4471_passport.pdf, ADDR_4471_utility.pdf β so the auditor's queue processor does not misroute your submission. Batch everything into a single upload session; fragmented submissions create duplicate review tickets and reset your queue position.
The account review documents workflow rewards precision and punishes improvisation. Match the name spelling exactly across every document and the account profile, keep all four document edges inside the frame, and submit the original file rather than a re-encoded copy. Auditors work from a checklist that scores legibility, date validity, name consistency, and instrument ownership β miss any one field and the ticket bounces back with a generic rejection code that costs you another full review cycle.