Crypto gaming has matured rapidly, but many operators are still treating wallet screening as a box-ticking formality rather than a live risk control. The consequences range from frozen withdrawals and strained payment-processor relationships to full regulatory action. Getting the fundamentals right is not complicated, but it does require discipline and the right tooling.
Why Tainted Funds Are a Distinct Risk in Crypto Gaming
Unlike fiat transactions, on-chain deposits carry a visible history. Every wallet address has a trail, and chain-analysis tools can trace funds back through dozens of hops to their origin. Regulators, banking partners and licensed payment gateways are increasingly running these checks themselves. If your platform accepts a deposit that they later flag, the liability sits with you, not with the player.
Tainted funds typically arrive from one of four sources: darknet markets, ransomware wallets, mixer or tumbler services, and wallets associated with sanctioned individuals or entities. Accepting even a small share of these funds can trigger a Suspicious Activity Report obligation, jeopardise your bank accounts, or put your licence renewal at risk.
The Most Common Screening Mistakes Operators Make
1. Screening Only at Deposit, Not at Withdrawal
Many operators run a risk check when a deposit arrives and then consider the job done. This misses a critical window. Withdrawals are where regulators expect you to confirm that the funds leaving your platform are going to a wallet the player legitimately controls, and that the destination address has not been flagged since the original deposit. A wallet that was clean on day one can appear on a sanctions list within weeks.
2. Using a Single Data Provider
No chain-analysis provider has complete coverage of every risk category across every blockchain. Relying on one vendor creates blind spots. A wallet flagged as high-risk by one service may show as clean on another due to differing methodologies or data freshness. Operators with significant crypto volume should consider layering two providers or cross-referencing results for transactions above a defined threshold.
3. Setting Risk-Score Thresholds Too High
Most chain-analysis tools assign a percentage-based risk score, where a higher number indicates greater exposure to illicit activity. A common mistake is setting the block threshold at 75 percent or higher, effectively allowing wallets with meaningful taint to pass through. Industry practice among compliant operators is trending toward blocking or escalating anything above 15 to 25 percent indirect exposure, with stricter limits for direct exposure. Your threshold should be documented in your AML policy and signed off by your MLRO.
4. No Process for Partial Taint
Funds rarely arrive 100 percent tainted. More often, a deposit contains a mixture of clean and flagged value. Operators without a partial-taint policy either block legitimate players unnecessarily or wave through transactions that should trigger enhanced due diligence. A proportionate approach, one that requires source-of-funds documentation when indirect exposure exceeds your threshold, is both commercially sensible and defensible to regulators.
5. Failing to Document Screening Decisions
Screening logs are audit evidence. If your compliance team overrides a flag, that decision must be recorded with a rationale, a timestamp and the name of the person who approved it. Regulators reviewing a crypto AML breach consistently cite poor record-keeping as an aggravating factor when determining penalties.
Building a Practical Screening Workflow
A robust workflow does not need to be complex. At OnlineShine, we recommend the following structure for operators handling any volume of crypto deposits:
- Screen the depositing address at the point the transaction is broadcast, before crediting the player account.
- Apply a secondary check on the source wallet when the deposit value exceeds your enhanced due diligence threshold.
- Re-screen destination addresses at withdrawal, regardless of prior checks.
- Maintain a risk-score log with every decision, automatic or manual, timestamped and attributed.
- Review your provider configuration quarterly, as sanction lists and risk categories are updated frequently.
- Assign MLRO sign-off to any policy change affecting risk-score thresholds.
Regulatory Expectations Are Tightening
The FATF Travel Rule, now in force across most major licensing jurisdictions, requires originator and beneficiary information to accompany crypto transfers above threshold values. Malta, Gibraltar, Curacao and the Isle of Man have all issued guidance or enforcement actions touching on crypto AML in the past two years. The direction of travel is clear: passive screening is no longer sufficient, and operators who cannot demonstrate a documented, tested process will face growing scrutiny at licence renewal.
A wallet screening programme is only as strong as the policy it sits inside. Tools identify risk; people and processes decide what to do with it.
Where OnlineShine Can Help
Our MLRO and compliance team works with crypto gaming operators to design and stress-test wallet screening workflows, select and configure chain-analysis tooling, and produce the policy documentation regulators expect. If your current process relies on a single provider, undocumented overrides or thresholds you have not revisited since launch, this is a practical starting point for a review.
