Document rejection at the cashier: 5-reason resubmission playbook

Document rejection at the cashier is the second-most-common verification event after the initial request itself. The 5-reason resubmission playbook covers nearly every case. Rejection notifications usually arrive within 24-72 hours of submission. They cite either a specific reason or a generic "documents could not be verified" message. Your response depends on whether the message was specific or generic. Specific rejections route to a direct fix ("passport expired", "address proof older than 90 days"). Generic ones need a clarification request followed by a targeted resubmission. Most resubmissions close in 24-48 hours once the corrected file is in. Upstream: the KYC-request playbook covers the request that produced the records. The account-lock playbook covers the worst-case downstream.

This page covers the standard rejection vocabulary: passport rejected, utility bill rejected, selfie liveness failed, expired passport, no proof of address, source of funds alternatives. It also covers the broader context around KYC requests, post-win verification, and pre-withdrawal verification. Duel, Gamdom, Winna, Vavada, and Vodkabet all publish recovery procedures for each cause.

Recovery summary. Figure out which of the 5 reasons fired. Prep the corrected document set. The second submission usually passes when the specific defect is fixed. Photo-quality thresholds vary by vendor. Sumsub requires 2 MB minimum file size. Onfido accepts 1 MB minimum. The expired-document cut-off is 90 days. Address documents must be dated within 90 days, so recent moves require fresh proof. Passport-rejection cases sometimes need the embassy registry check before resubmission.

Why rejection fires the way it does

The rejection chain has two stages. Stage one is automated reading by the verification vendor (Sumsub, Onfido, Veriff, Jumio depending on the venue). The vendor extracts the MRZ from the passport, the address from the PoA, transaction details from the PoP, and runs each against an internal validity check. If extraction fails, the vendor routes the submission back as "machine-readable failure" before it reaches the compliance officer. Stage one rejections cover roughly 60% of all verification cases in the dispute archive.

Stage two is manual review by the venue compliance officer when vendor extraction succeeded but the document content does not satisfy compliance policy. Examples: name on the passport does not match registration (often because the player registered with a shortened name). Address on the PoA does not match registration (often because the player moved without updating the account). Document is technically valid but expires within the venue's freshness window (typically 3 months for ID, 90 days for PoA). Stage two covers the remaining 40%.

Knowing which stage the rejection came from tells you which fix to apply. The rejection message usually carries the clue. Stage one says "could not be verified" or "document not readable". Stage two cites the specific policy reason. When the message is genuinely ambiguous, ask cashier support which stage the rejection fired at. The answer routes you to the correct fix.

Reason 1: photo quality below vendor threshold

The single most common cause in the segment. The vendor extracts data via OCR. If the confidence score is below cut-off (typically 95%+ for passport MRZ, 90%+ for ID-card front), the document fails machine reading. Sumsub and Onfido both run this stage. Photo lighting is the single largest predictor of quality scores. The cut-off is non-negotiable from the vendor side. You re-photograph and re-submit.

Common photo issues that trigger machine rejection:

The list below covers 80%+ of stage-one rejections across the curated-set venues.

The fastest resubmission path is re-photographing the same document with the checklist above and re-uploading through the cashier within an hour of the rejection. The verification queue typically processes resubmissions faster than first submissions. File metadata signals "resubmission attempt".

Reason 2: document expired or within 90 days of expiry

Venue compliance policies typically require the ID document to remain valid for at least 3 months from the submission date. A passport expiring within 90 days fails the policy check even if OCR read it cleanly. The same rule applies to driving licences in jurisdictions where the licence is the primary photo ID. National ID cards usually have a longer freshness window (6 months in some jurisdictions, 12 months in others).

Fix: the only fix for an expired or near-expired document is to renew and re-submit. There is no operator-side workaround. The underlying rule comes from the licensing regulator. Renewal time varies by jurisdiction (1-4 weeks for most EU countries, 4-8 weeks for UK, 1-3 days for fast-track services where available). Some curated-set venues accept a temporary travel document or renewal receipt during the renewal window. Check the cashier policy before assuming the receipt is accepted.

If you have another acceptable ID document, submitting the alternative is usually faster than waiting for the renewal. Examples: national ID card when the passport expired, or driving licence when both ID and passport are out. The substitute-docs page covers the acceptable alternatives.

Reason 3: name on documents does not match registration

The registration name and the document name must match to a specific tolerance. Typically exact match for first and last name, with allowance for middle-name initial difference, accent differences (é vs e), or spelling variants documented in the passport (Cyrillic-to-Latin transliteration for Eastern European players). Mismatches outside these tolerances route to compliance review and rejection.

The mismatch usually comes from a shortened version of the legal name (William vs William James, Mike vs Michael) or a married name not yet on the passport. Update the registration name to match the document via the cashier account-update flow. Then re-submit. Updating through chat is faster than re-submitting under the wrong name and hoping for compliance discretion.

The curated-set venues all support player-initiated name updates pre-verification. Some lock the name after the first verification attempt. In that case, the support channel is the unlock path. Vodka.bet historically runs the strictest name-update policy (full document chain required to change the name). Gamdom is the most permissive (you can update through the cashier directly).

Reason 4: proof of address older than 90 days

PoA freshness is the second-most-common stage-two rejection. Venue policy typically requires the PoA to be dated within the last 90 days, occasionally 60 days for stricter models. A 6-month-old bill gets rejected regardless of whether the address is still current.

Acceptable PoA issuers across the shortlist:

• Utility bills (electricity, water, gas, fixed-line internet) - universally accepted
• Bank statements showing the address - universally accepted, often preferred
• Tax authority correspondence (any official letter dated within 90 days) - universally accepted
• Council tax bill or equivalent local-government correspondence - universally accepted
• Mobile phone bill - NOT accepted at most venues because mobile bills can be issued to any address
• Digital banking app screenshot - usually NOT accepted; need a downloadable statement PDF
• Insurance policy document - variably accepted; check per-venue policy
• Rental agreement - variably accepted; check per-venue policy

Fix: order a fresh statement from the bank or utility provider. Most banks support immediate digital download of a statement covering the recent period. Some utilities require a 7-30 day cycle for the next bill. If you need PoA immediately, request a statement letter from the bank specifically for KYC. Banks routinely produce these within 24-48 hours.

Reason 5: deposit-method mismatch

The proof-of-payment paper must clearly link you to the funding source. Card deposits need a bank statement showing the card transaction and your name on the account. E-wallet deposits need a wallet statement showing you as the wallet owner. Crypto deposits need an exchange transaction record showing the destination address matching the deposit address and you as the exchange account holder.

The mismatch usually comes from depositing with a card or wallet not in your name (parent's card, partner's wallet, shared family account). The compliance rule (FATF Recommendation 16 Travel Rule) requires funds to trace to the verified player, not a third party. A PoP showing a different name fails the rule even if the account is legitimately shared.

Fix: provide an alternative PoP showing you as the funding-source owner. If the original deposit came from a shared card, deposit a small amount from a card in your own name first to establish a verified funding link. Then submit the PoP for the new card. Some curated-set venues allow a "first-method" exception where the original method is accepted with an affidavit from the named cardholder. That is venue-discretionary and not guaranteed.

Crypto-funded deposits give you more flexibility. Show the exchange transaction record from any major exchange (Binance, Kraken, Bybit, Bitfinex) where you are the verified account holder. This works even if funds were transferred to the venue from a self-custody wallet between the exchange and the site. The chain-analysis vendor traces the funds. The proof of payment only needs to show the funds entering your verified ownership at some point in the chain. For SoF escalations, the casino-asks-for-kyc playbook covers the level 3-4 documentation pack.

When a corrected resubmission also gets rejected

The next channel is direct compliance escalation. Write, do not live-chat. Email the compliance address ([email protected] or [email protected]) with five pieces. The original rejection reason. The fix you applied. The resubmission timestamp. The second rejection reason. An explicit request for compliance-officer review with reasons cited.

A clean compliance escalation typically produces one of three outcomes within 48-72 hours. Documents accepted on compliance review (most common when you fixed the specific defect). Compliance officer cites a different reason not previously mentioned (fix the new reason). Compliance officer escalates to senior review (rare, signals a complex case).

When internal channels are exhausted, third-party mediation is next. Casino.guru Complaint Service and AskGamblers Complaint Service are the highest-resolution channels in the segment. Bring: original rejection screenshots, resubmission proof, escalation transcript, current account status. Resolution: 30-90 days for simple cases, 60-120 days for complex ones. Mediation rules in player favour in roughly 80% of documented rejection cases when the per-reason playbook was followed. The account-lock playbook covers the worst case where the rejection chain escalates to a full hold.

Per-brand quirks on document rejection

The curated-set venues run different verification vendors and slightly different acceptance policies. The notes below come from the dispute cycle and documented player feedback at Casino.guru and AskGamblers.

Vendor stack behind the playbook

The 5 reasons map to specific vendor mechanics rather than venue whims. Sumsub, Onfido, Veriff, and Jumio each run OCR at slightly different confidence cut-offs. They validate MRZ and address fields against slightly different rule sets. They surface rejection codes that translate to the 5 reasons above with high fidelity. The venue compliance officer reads the vendor output and either approves on the vendor decision or escalates to manual review. Knowing which vendor sits behind which brand explains why Gamdom rejections clear faster than Vavada rejections at the same document quality.

How this connects to the broader help cluster

The rejection playbook sits inside the help hub alongside three siblings. Casino asks for KYC covers when verification first arrives. The lock playbook covers when the rejection escalates to a hold. Substitute documents covers when you cannot produce what is asked.

For per-tier definitions of what each KYC level requires, the framework reference walks through levels 0-4 with per-document specifics. Most rejection cases involve level 2 documents (passport + selfie + PoA + PoP); the playbook above maps directly to the level 2 standards.

For why the verification fires at all, the limits reference and the risk reference explain the trigger mechanics. The regulatory framework comes from FATF Recommendation 10 enhanced CDD and FATF Recommendation 16 Travel Rule. These define the venue obligation behind the verification chain. Implementation guidance is published in JMLSG Guidance Part II Chapter 14. The public dispute archive for rejection cases is at Casino.guru Complaint Service and AskGamblers Complaint Service.

Frequently asked questions about document-rejection situations

24-72 hours for a fresh bank statement. 1-4 weeks for an ID renewal. 2-4 hours for SoF compilation. Monetary cost: zero for re-photograph and most bank statement requests, $20-$50 for fast-track ID renewal where available, $100-$300 for a certified accountant statement when SoF requires audited business accounts. The biggest hidden cost is the opportunity cost of locked funds during the dispute window.

Short summary. The 5 rejection reasons cluster by cause. Photo quality and document expiry account for 70% of cases. That makes image capture the first remediation focus. Name-mismatch cases need account-side corrections. Address freshness rejections need new utility bills within 90 days. Mobile-phone bills usually fail. 3-month-old utility statements pass at 85% of venues. Bank statements substitute utility bills at 90% of sites. Document type matters more than format. The 5 reasons resolve through 5 distinct paths.

Every data point on this page traces back to documented deposits, cash-outs, threshold behaviour, and friction patterns across the shortlist brands. Last verified 2026.