Account Verification After Login At FortuneJack
After you sign in, FortuneJack asks for verification when an action triggers a compliance check, most often a withdrawal request or a change to security and payment details.
Verification is also requested if the account shows a mismatch between profile data and payment details, if you log in from a new country or device and risk checks flag the session, or if the operator needs to confirm age and identity for responsible gambling rules.
Once the request appears in the account area, you upload documents and wait for a manual review; during this time, deposits and gameplay can continue, while withdrawals and some account changes can be paused until approval.
- ID: A clear photo or scan of a government-issued document (passport, national ID card, or driving licence). The file must show your full name, date of birth, document number, and expiry date, with all corners visible.
- Address: A document dated within the last 3 months showing your full name and current address (utility bill, bank statement, tax letter, or council letter). Screenshots without issuer details or documents with cropped headers get rejected.
- Payment method: Proof that the payment method belongs to you. For bank cards, FortuneJack can ask for a photo of the card with the middle digits covered and the CVV hidden, or a bank statement showing the card and your name. For e-wallets or crypto, they can ask for a wallet/account page showing your name or account identifier plus transaction evidence matching the deposit.
- Source of funds (when requested): Documents that show where gambling funds come from, such as recent payslips, a bank statement showing salary credits, or a tax return. This is requested on higher-value withdrawals or when activity patterns trigger anti-fraud checks.
- Selfie / live check (when requested): A selfie holding your ID, or a short live verification video, used when the operator needs to confirm the person uploading documents matches the ID.
Current state: FortuneJack verification is event-driven and tends to appear around withdrawals, profile/payment changes, or risk flags; the core package is ID plus proof of address,