AML Policy
This AML Policy explains the anti-money laundering and counter-terrorist financing principles that may apply in connection with gambling-related account use, payments, verification and withdrawals. The purpose of the policy is to help users understand why identity checks, payment reviews and source-of-funds questions may be required.
Gambling services can be exposed to financial crime risks, including identity misuse, stolen payment methods, duplicate accounts, bonus abuse, fraud, money laundering and attempts to disguise the origin of funds. AML controls are designed to reduce those risks and protect the integrity of account activity.
1. Purpose of AML controls
AML controls exist to make sure that gambling accounts are used by real, eligible users and not for illegal financial activity. These controls may apply during registration, before deposits, before withdrawals, when payment methods change, when unusual activity appears or when an account triggers a risk review.
The goal is not only to check identity once. Account activity may be reviewed over time, especially if transaction behaviour changes, if deposits increase sharply, if withdrawals do not match expected play, or if account information appears inconsistent.
2. Customer identity verification
Users may be asked to verify their identity. This usually means proving that the registered account holder is a real person, is old enough to use the service and matches the details submitted during registration.
Verification may include documents such as:
- Passport, national identity card or driving licence.
- Proof of address, such as a utility bill or bank statement.
- Payment method ownership proof.
- Selfie or liveness check where required.
- Additional documents if earlier information is unclear.
Documents must be valid, clear, complete and unaltered. Blurred, cropped, expired, mismatched or edited documents may be rejected. If the account name does not match the payment method or identity document, additional review may be required.
3. Source of funds and source of wealth
A user may be asked to explain where deposited money comes from. This is known as a source-of-funds check. In higher-risk situations, a broader source-of-wealth check may also be required to understand the user's overall financial background.
Examples of acceptable explanations may include salary, business income, savings, sale of property, investment income, inheritance or other legitimate sources. The type of evidence requested depends on the risk level and transaction pattern.
Users should answer clearly and provide documents when requested. Refusing to explain the source of funds, giving inconsistent answers or providing documents that do not support the transaction history can result in account restrictions or withdrawal delays.
4. Payment method ownership
Users should only use payment methods that belong to them. Depositing with another person's card, bank account, e-wallet or crypto wallet can create serious verification and AML concerns. Even where a payment is not fraudulent, third-party payment use may breach account rules.
A withdrawal may be delayed or blocked if the payment method cannot be verified. Users may need to prove ownership through screenshots, statements, payment provider confirmations or other approved evidence. Sensitive information should only be provided through secure verification channels.
5. Transaction monitoring
Account transactions may be monitored for unusual patterns. This can include deposit frequency, withdrawal behaviour, payment method changes, mismatched account details, rapid movement of funds, little or no gameplay between deposit and withdrawal, repeated failed payments or unusual bonus activity.
Monitoring may be automatic, manual or both. A flagged transaction does not always mean wrongdoing. It means that additional review may be needed before activity continues.
Examples of activity that may require review include:
| Activity pattern | Possible AML concern |
|---|---|
| Large deposits with limited play | Possible movement of funds without normal gambling activity |
| Multiple payment methods | Ownership or fraud risk |
| Frequent account detail changes | Identity inconsistency |
| Deposit and quick withdrawal | Possible payment misuse |
| Duplicate account signals | Account control or bonus abuse risk |
| Refusal to provide documents | Inability to complete due diligence |
6. Suspicious activity
Suspicious activity may include attempts to hide identity, use false documents, split transactions, use third-party funds, create duplicate accounts, misuse bonuses, coordinate activity with other users or avoid verification.
If suspicious activity is identified, account functions may be limited while the review is completed. This can include suspension of deposits, cancellation of withdrawals, bonus removal, account freezing or permanent closure. Where required, information may be reported to relevant compliance, payment or legal channels.
7. Bonus abuse and AML risk
Bonus abuse can overlap with AML and fraud controls. Creating multiple accounts, using shared devices, using several payment methods, coordinating with other users or claiming the same offer repeatedly may trigger both bonus and compliance review.
Users should not treat bonuses as a way to move money through an account. Promotional funds are subject to conditions, and any attempt to exploit bonus rules may result in cancellation of bonus balances, winnings review or account restriction.
8. Withdrawals under review
A withdrawal may be delayed when AML checks are incomplete. This does not automatically mean the withdrawal is refused. It may mean that identity, payment ownership, source of funds or account activity must be reviewed before funds can be released.
Users can reduce delays by keeping account details accurate, using payment methods in their own name, responding to document requests promptly and avoiding inconsistent activity. If further information is requested, the user should provide complete and readable documents.
9. Politically exposed persons and sanctions
Some users may require enhanced due diligence due to political exposure, sanctions screening, high-risk location indicators or unusual financial activity. Additional checks may be required before account access, deposits or withdrawals are allowed.
If a user appears on a sanctions list or cannot pass required screening, the account may be restricted or closed. Enhanced checks are part of risk control and should not be treated as optional when requested.
10. Record keeping
AML-related records may be kept for compliance, audit, fraud prevention, dispute handling and legal purposes. These records can include identity documents, verification outcomes, payment evidence, transaction history, source-of-funds information, account notes and communications.
Some records may need to be retained even after an account is closed. This can help prevent duplicate accounts, support self-exclusion controls, investigate suspicious activity and meet recordkeeping obligations.
11. User cooperation
Users are expected to cooperate with AML and verification requests. This means providing accurate information, submitting clear documents, answering reasonable questions and not attempting to bypass restrictions.
A user should not:
- Provide false or edited documents.
- Use another person's payment method.
- Create duplicate accounts.
- Split transactions to avoid review.
- Hide the source of funds.
- Refuse verification after requesting a withdrawal.
- Use gambling accounts for non-gambling money movement.
Failure to cooperate may lead to delays, cancellation of transactions, account suspension, closure or reporting where required.
12. AML policy updates
This AML Policy may be updated when compliance expectations, payment rules, verification processes or risk controls change. Users should review the current version before relying on the site or engaging in account activity that involves deposits, bonuses or withdrawals.
AML checks are a normal part of gambling account management. Users who provide accurate details, use their own payment methods and respond to verification requests promptly are less likely to experience avoidable delays.