BitStarz document verification: KYC requirements and support guide

Why BitStarz may request KYC documents

The current terms describe Know Your Customer as a verification procedure and allow checks connected with suspicious or fraudulent transactions. The privacy policy identifies official documents as Identity Verification Data used for KYC and anti-money-laundering compliance. A request is therefore an account-control process, not an optional profile decoration. It can occur after registration or around a payment review, and the required evidence can vary with risk and method.

Use true, complete and current registration details from the beginning. A nickname, outdated residence or payment method owned by someone else can create a mismatch that a clearer photo cannot solve. Ordinary terms, bonus review and payment rules still apply after KYC. Ask for clarification when a request does not identify the evidence category or secure destination.

• Identity
• Legal age
• Residential address
• Payment ownership
• Transaction review
• Additional lawful evidence

Read the live request before uploading anything

Open the signed-in account from the official BitStarz domain and read the current verification notice in full. List each requested category, acceptable document, date rule, image side, file format and deadline. Do not assume that a generic internet checklist replaces account-specific instructions. The terms permit additional information, so two players using different payment routes can receive different lawful requests.

If the interface is unclear, contact official support and ask a narrow question: which document, which page or side, which details may be concealed, and which secure upload channel should be used. Retain the reply and ticket identifier. Do not transmit a sample document merely to ask whether it is suitable, and do not send every identity record you own in the hope that one will be accepted.

Prepare government-issued identity evidence

Section 7.2.1 of the current terms describes a government-issued identification document showing full name, date of birth, issue and expiry dates and a photo. Choose a document type accepted by the live request and confirm that it is valid. The spelling and birth date should correspond to the Member Account. If a legal name changed, ask support which linking evidence is required rather than editing either record.

Photograph the document on a plain surface with even light. Include every requested corner and side, keep text in focus and avoid reflections across security features. Do not apply filters, retouch text, combine unrelated files or submit a screen capture of a manipulated image. An older 2020 official FAQ offered detailed capture advice, but the current on-screen instructions take priority if they differ.

Provide a recent proof of residential address

The current terms describe proof of address as a document confirming the residence stated during registration, showing the player's full name, residence address and issue or expiry dates. They expressly say the proof should be no older than 90 days from issuance. Count from the visible document date rather than the day it was downloaded, and ensure the complete address matches the account format.

Use only a category accepted by the live request, which may name a bank record, utility document or official correspondence. A mobile screenshot that omits the issuer, date or page context may be insufficient. Download an original electronic file when the operator requests one. If the player has moved, update the account through the approved procedure and ask which old or new evidence is required before submitting contradictory addresses.

Demonstrate payment-method ownership without exposing secrets

Section 7.2.2 of the terms identifies proof of payment as another core category. The exact evidence depends on the method: a card, e-wallet, bank account or crypto transaction exposes different ownership signals. Use only a method the player lawfully controls and follow the precise masking instruction. Never reveal a card PIN, full security code, online-banking password, private key or wallet seed phrase.

Match the requested payment record to the account transaction by date, amount, currency and reference where available. Do not edit a screenshot to manufacture ownership or borrow a statement from another person. For crypto, a transaction identifier can show movement on a public chain but does not by itself prove ownership of every address; provide only the evidence the verified BitStarz case requests through the authorised channel.

Create clear files on mobile or desktop

Before upload, view each file at full size. Text should remain legible, the orientation should be correct, all requested edges should be present and the file should stay within the supported size and type. Photograph physical documents rather than a monitor displaying them unless the instruction says otherwise. Avoid compression tools that send identity material to an unknown cloud service.

Name files neutrally, for example identity-front or address-2026-08, without placing a full document number in the filename. Keep one controlled working copy and track which version was submitted. If a file is rejected, correct the stated defect rather than uploading the same image repeatedly. Remove metadata only when it does not conflict with the operator's authenticity requirements, and never alter visible evidence.

Upload through an approved secure route

Begin at bitstarz.com, sign in and navigate to the current verification interface. If support instructs another channel, confirm the instruction through the official ticket before sending data. Our affiliate site cannot receive, forward or inspect KYC documents. A page using the BitStarz name, logo or copied help text is not sufficient if its hostname and connection do not match the authorised destination.

Use a private device and trusted connection, close screen-sharing software and verify that no clipboard manager is publishing images. Wait for the upload acknowledgement and record only its reference and time. Avoid submitting the same file in several channels, because duplicates can confuse the review trail and broaden exposure. Never pay a third party to accelerate KYC or grant remote access to complete it.

Respond to a rejection or pending status

A rejection should identify a correctable issue such as blur, crop, expiry, unsupported type or data mismatch. Read the reason in the official account or message, compare it with the original request and replace only the affected file. The 2020 official FAQ says players should check email for the reason and explains common visibility rules, but a six-year-old article cannot override the current case instruction.

A pending label is not a reliable timer. Preserve the submission date, account notice and ticket reference, then allow the stated review period if one is displayed. Do not make repeated deposits, withdrawals or uploads to force movement. If the stated period passes, ask support which document is pending and whether any action is required. A concise status question is safer than resending sensitive evidence in the chat transcript.

Understand withdrawal impact and completion notices

The current terms say non-provision of requested KYC documentation prevents payments and can ultimately lead to suspension or closure after attempted contact. They also say the outstanding balance remains subject to payment after required procedures are completed, while funds linked to terms violations can be retained. These clauses make accurate evidence and timely communication important, but they do not create a fixed approval deadline.

Section 7.3 says the player is informed by email when KYC is completed and may ask customer service for status. Keep the registered mailbox accessible and distinguish that notice from the earlier email-confirmation step. Completion does not prevent future requests for a renewed ID, new address proof or other information when circumstances change. Store the final notice and update evidence before expiry where the live account asks for it.

Protect document privacy and escalate safely

Read the privacy policy for processing purposes, data categories, retention, sharing and the rights available in the relevant jurisdiction. Submit the minimum evidence that satisfies the current request, but do not conceal required information without permission. Keep local files encrypted or otherwise access-controlled, avoid shared photo libraries and remove redundant copies from ordinary downloads folders after the case and record-retention needs are settled.

For support, provide the account identifier, request category, upload time, status and exact non-sensitive error. Do not place complete identification numbers or images into the first message. Use the on-site Help control or published official contact and retain the case number. If a message arrives from social media asking for a document or one-time code, stop and verify it independently through BitStarz before responding.