Account re-verification: why KYC is requested again and what to save
A repeat KYC does not automatically mean a refused payout or a breach by the casino. The operator may be updating outdated data, checking a new payment method or carrying out an additional risk assessment. But the request must come through an official channel, have a clear purpose and explain which files, fields and format are needed. Save the request itself, the rules, the account status, the list of documents sent, the confirmation of receipt and the full timeline.
Do not send documents through a random messenger and do not publish them via an open link. Do not share your password, CVV, one-time code, seed phrase or full access to your bank. If the scope of the request is unclear, first ask for a written clarification.
Why KYC can be repeated
KYC means customer identification. It is not always a one-time check mark. The FATF Recommendations, as amended in June 2026, describe customer due diligence as a risk-based process that includes monitoring the relationship and keeping information up to date, especially in higher-risk cases. FATF is an international standard for states, while an operator's specific obligation is determined by local law and its licence.
Possible reasons for a new request:
- a document has expired or the quality requirements for it have changed;
- your name, address or other profile details have changed;
- a new payment method has been added;
- information received earlier did not match an independent source;
- a transaction required additional checks under the applicable AML rules;
- an automated check did not give a clear result;
- the operator must confirm that the payment instrument belongs to the account holder;
- the current risk assessment differs from the previous one.
These are possible categories, not proof of the reason in your case. Ask the operator to state the purpose as specifically as the law and the rules allow.
When a request at withdrawal deserves special attention
A withdrawal can be a point for an additional check, but it should not automatically turn into a convenient delay. For operators with a British licence, the current condition LCCP 17.1.1 requires the name, address and date of birth to be verified before a customer is allowed to gamble. It also says that a withdrawal request should not trigger a demand for information that could reasonably have been requested earlier, except in cases of a new legal obligation.
This rule applies only to the relevant UKGC licences. For any other site, check its regulator, the applicable law, the Verification Terms and the Withdrawal Terms.
A normal check or a stalling tactic
| SignManageable checkNeeds written clarification | ||
| Purpose | It is stated what is being verified | Only a “security decision” |
| List | Requirements are given in a single list | Each reply triggers a new, unrelated request |
| Channel | Secure account area or a verified domain | Personal messenger account or an unknown email address |
| Format | Type, period and required fields are clear | Files are rejected without a reason |
| Proportionality | The data is linked to the purpose | Extra information is requested without explanation |
| Status | There is a ticket number and updates | Receipt is not confirmed |
| Repeat | It is explained why the old file is not suitable | The same valid file is requested again without grounds |
One red flag does not prove abuse. Assess the whole sequence and the applicable rules.
Which documents may be requested
There is no universal set. Depending on the purpose, the operator may request:
- a photo ID;
- proof of address;
- a selfie or a liveness check;
- proof of payment method;
- a statement showing a specific transaction;
- an explanation of the origin of a particular transaction;
- source of funds documents as part of a separate check.
Do not send every document “just in case”. Ask:
- What exactly needs to be confirmed?
- Which document is acceptable?
- For what period?
- Which fields must be visible?
- Which information may be covered?
- What file format and maximum size are allowed?
- Where is the official upload channel?
Do not edit a document in a way that makes it unreliable. Agree in writing first on whether you may hide unrelated fields.
What to save before sending
Create a separate folder, but do not keep it in publicly accessible cloud storage.
| FileWhat must be visibleSafe name | ||
| KYC request | Date, sender, purpose, list | 01_KYC-request_2026-09-07.pdf |
| Rules | URL, version, date saved | 02_Verification-Terms.pdf |
| Account status | Restriction and time | 03_Account-status.png |
| Transaction status | ID, amount, currency, date | 04_Transaction-status.png |
| File sent | Exact version, no password in the name | 05_ID-submitted.pdf |
| Confirmation of receipt | Ticket number and list | 06_Receipt-ticket-123.pdf |
| Operator reply | Reason for acceptance or rejection | 07_Operator-response.pdf |
| Timeline | All actions in order | 08_Timeline.xlsx or .md |
Do not include the full document, card or account number in a file name. Keep originals separate from the copies prepared for sending.
A safe nine-step procedure
1. Check the sender
Open the website manually and compare the email domain, the account area address and the contacts in the Terms. Do not follow a shortened link from an unexpected message.
2. Record the starting position
Save the account and transaction status before uploading. If this concerns a withdrawal, write down the ID, amount, currency and date.
3. Ask for a single list
Request template:
Please state the purpose of the repeat check, the full list of documents, the required fields, the accepted format, a secure upload channel and the ticket number.
4. Check your profile
Check the spelling of your name, your address, date of birth, phone number and the owner of the payment method. Do not change data without an explanation if it is linked to the current transaction.
5. Prepare a legible copy
Do not crop required edges, do not apply filters and do not change the text. Remove metadata or cover unrelated fields only if the requirements allow it.
6. Upload through the official channel
A secure section of your account is preferable. If email is used, compare the domain with the official website. Do not put documents behind a public “anyone with the link” share.
7. Get a confirmation
Ask them to confirm each file received and to list all missing items in a single message.
8. Do not create information noise
Do not send the same file ten times through different channels. This complicates the timeline and increases the surface for a leak.
9. Keep your log up to date
After each action, record the date, channel, file, reply and the promised next step.
Data minimisation: an important limit
In its guidance on sharing personal data, the ICO explains to organisations under the UK GDPR the principles of data minimisation, accuracy, storage limitation and security. This is a British legal context, but the practical question is universal: why is each piece of data needed and how is it protected?
Before sending, clarify:
- who receives and controls the data;
- the purpose of each document;
- the retention period;
- to whom the materials may be passed on;
- how to request access, correction or erasure, if that right applies;
- whether unrelated transactions may be hidden;
- how to report a security incident.
Do not demand erasure if the operator is required by law to keep the data. Ask them to explain the legal basis and the retention period.
What you must never send
- your account password;
- your full CVV/CVC;
- a code from an SMS or an authenticator app;
- your seed phrase or private key;
- remote access to your device;
- your online banking login and password;
- a document via a public link;
- extra documents unrelated to the request.
A genuine support agent may ask you to confirm a transaction, but must never receive a secret that allows them to log in or sign a transfer on your behalf.
How long a repeat KYC takes
There is no single international deadline. It depends on the applicable law, the licence, the complexity of the check, the quality of the files and whether additional measures are needed. Do not promise yourself or others a specific date without a clause in the rules or a written reply from the operator.
Ask five manageable questions:
- Have all the files been received?
- Which item is still needed?
- At what stage is the check?
- What time frame does the procedure specify?
- When will the next status update be?
If support asks you to make a new deposit or keep playing to “speed up” KYC or a withdrawal, do not do it and record the request.
When to move to an official complaint
- the purpose of the request is not explained;
- the same valid document is rejected without a reason;
- requirements appear one at a time and are unrelated to each other;
- an insecure channel is used;
- the operator does not confirm receipt;
- the rules and the actual requirements contradict each other;
- the check is described as completed, but the restriction is not explained;
- support suggests cancelling the withdrawal and continuing to play.
First use the internal Complaints procedure. State the account, the transaction, the timeline, the documents already provided and your specific demand. Ask for a reasoned written reply. Then check the regulator or ADR route, if one is provided for this particular licence and dispute.
What to give IPU.bet
The IPU.bet Privacy Policy expressly asks you to mask excessive data in Player Support materials wherever possible. By default, IPU.bet does not need your full passport, bank statement, card details, seed phrase or private key to organise a request.
Prepare for IPU.bet:
- the operator's name and public URL;
- your account ID without the password;
- the ticket number;
- a short timeline;
- the text of the KYC request;
- anonymised status screenshots;
- links to the applicable rules;
- the operator's replies.
Do not forward unredacted documents until IPU.bet support has explained why they are needed and which channel is secure. IPU.bet does not confirm KYC on behalf of the operator and does not guarantee a payout.
How IPU.bet helps
Under the terms of use, Player Support is an informational and organisational service. The team can help take in a request, structure a complaint, organise the information, forward the request to a partner at the user's request and track its status.
It is not a legal service, not ADR and not a guarantee that the partner will reply, approve KYC, unblock the account or process a withdrawal.
Key takeaways
A repeat check can be a normal part of keeping KYC up to date and of risk-based control. A safe request has an official channel, a clear purpose, a complete list and a confirmation of receipt.
Save not only the documents but also the context: the rules, the status before sending, the exact version of the file, the receipt confirmation and the timeline. Share only what is needed and never send access secrets.
18+; 21+ in Kazakhstan. Play responsibly. Gambling is not a way to earn money.
Put together a secure evidence folder using the checklist and refer to the IPU.bet rules. If a repeat KYC has turned into a series of unrelated requests, contact Player Support at ipu.bet with an anonymised timeline.
FAQ
Can an operator ask for my passport again?
Yes, if there is an applicable reason to update or supplement the check. Ask them to state the purpose, the required fields and a secure channel.
Why did KYC come up exactly at withdrawal?
A withdrawal may coincide with an additional check. Under the UKGC, an operator should not postpone until withdrawal information it could reasonably have requested earlier, except where there is a new legal obligation. For other licences, check their rules.
Can I hide transactions on a bank statement?
Only after written agreement. Find out which fields are needed. Hiding data on your own may make the file unusable.
Should I cancel my withdrawal during the check?
Do not change the original request just to keep playing. Record the status and follow the official procedure of the specific operator.
What should I do if a document is rejected again?
Ask them to name the exact defect in the file and to provide the full list of requirements. Save the rejection and, if the chain of unjustified requests keeps repeating, move on to a formal complaint.
Do I need to send my passport to IPU.bet?
By default, no. For an initial review, an anonymised timeline, the rules and the replies are enough. Never send passwords, CVV, codes or private keys.
