If you run an online casino, sportsbook, crypto gambling platform, or even a B2B gaming business with player fund exposure, basic AML isn’t enough. Banks know it. Regulators definitely know it. And honestly, most founders leave this too late.
They assume AML means a policy, a KYC tool, and maybe one part-time compliance person. Nope.
Gambling gets treated as higher risk for pretty obvious reasons – fast-moving money, lots of transactions, cross-border users, chargebacks, payment agents, affiliates, possible mule activity, and customers who can look totally normal right up until they don’t. So the AML bar is higher. Not always written in one neat list, but very real all the same.
If you’re applying for a licence, opening a bank account, adding PSPs, or trying to keep an existing provider from quietly offboarding you, here’s what they usually expect to see.
Basic AML won’t save you
A standard corporate AML pack might be fine for a low-risk consultancy. It won’t cut it for gambling.
Banks and regulators want to know whether your controls match the way gambling money actually moves. Can a player deposit with one card, lose a bit, then withdraw to a different method? Can someone deposit small amounts across multiple accounts? Do you allow crypto deposits through a payment partner? How do you spot collusion, chip dumping, bonus abuse tied to laundering, or accounts opened for somebody else?
That’s the real test. Not whether you downloaded a policy template.
I’ve seen gambling businesses with slick front ends and expensive legal opinions get stuck because the AML side looked generic. The compliance manual said all the usual things. Customer due diligence. Monitoring. Reporting. Fine. But there was nothing gambling-specific in the actual controls. Big mistake.
What “extra controls” usually means in practice
Let’s make this concrete. If you’re in gambling, banks and regulators often expect more depth in at least these areas:
- Customer risk scoring tailored to gambling behaviour, not just country and PEP checks
- Source of funds and source of wealth triggers for players whose activity moves outside normal recreational patterns
- Transaction monitoring rules built around gameplay and payment behaviour together
- Withdrawal controls to stop pass-through activity and payment method abuse
- Enhanced due diligence for high spenders, unusual winners, and cross-border higher-risk customers
- Manual review procedures for alerts that can’t be sensibly closed by software alone
- MLRO oversight that actually functions, rather than a name on an org chart
If you haven’t built those out yet, start there.
Player risk scoring needs to reflect gambling reality
A lot of founders build risk scoring like they’re onboarding SaaS users. Country. Age. Sanctions screening. Maybe occupation if they feel fancy. That’s too thin.
For gambling, the scoring model should react to behaviour over time. Deposit velocity. Number of failed payment attempts. Use of multiple cards or wallets. Device mismatch. Sudden stake increases. Accounts that stay low activity until a big deposit appears. Fast deposit-withdrawal patterns with minimal gameplay. Players funded by third parties. You get the idea.
This is where banks get nosey, and fair enough. They want to know you can explain why customer A is low risk and customer B got escalated on day three. If your model is just “UK good, high-risk country bad,” it won’t survive much scrutiny.
If you need a deeper look at how scoring models are supposed to hold up in real life, this piece on customer risk scoring that regulators and banks actually accept is worth your time.
And yes, document the logic. Every threshold. Every trigger. Every override process. Because six months later, someone will ask.
Source of funds is where operators get lazy
This bit causes alot of pain.
Founders often think source of funds checks are only for very large deposits or jackpot winners. In practice, the trigger is usually broader. A player doesn’t need to be dropping absurd sums to raise questions. Repeated moderate deposits that don’t fit profile. A customer with low declared income but high turnover. Frequent top-ups from different funding methods. Obvious attempts to stay below review thresholds. That’s enough to start asking.
And asking means asking properly.
Not “please confirm your funds are legitimate” in a support email. I mean a documented process for what evidence you ask for, who reviews it, what counts as adequate, how contradictions are handled, and when the account gets restricted pending review.
Good source of funds reviews usually look boring. Payslips. business income evidence. Sale agreements. Bank statements. Tax returns in some cases. The exact standard depends on your market, licence, and player profile, so check current requirements. But the bigger point is this: if your team doesn’t know what “enough evidence” looks like, your control isn’t really a control.
Banks care about your payment flow almost as much as your licence
You can have a perfectly valid gambling structure and still get declined by a bank because the payment setup looks messy. That’s common.
They’ll look at who accepts deposits, where settlement lands, whether player funds are ring-fenced as required in your operating model, how refunds work, and whether the merchant flow creates AML blind spots. If there are introducers, affiliates, white-label relationships, payment agents, or crypto gateways in the chain, expect more questions. Sometimes many more.
This is why gambling businesses often need a proper payment strategy and banking access plan before they start sending applications around. Not after the third rejection. Before.
And if you’re still figuring out whether you need an EMI account, a traditional bank, or both for different parts of the stack, read this breakdown on EMI vs traditional bank accounts. It’s written for fintechs, but the logic applies surprisingly well to gambling setups too.
Your MLRO can’t be decorative
Some operators appoint an MLRO because the checklist says so, then give that person no authority, no data access, and no time. That’s not an MLRO. That’s a hostage.
The person handling AML oversight needs to be able to review alerts, challenge commercial teams, escalate suspicious activity, and push for account restrictions without begging product or VIP managers for permission. If your VIP lead can override compliance because a player is “valuable,” your framework is already wobbling.
For early-stage businesses, a full in-house hire can be overkill. Fair. But you still need real ownership of the function. A decent outsourced setup is usually far better than pretending your COO covers AML on Fridays. If that’s your current plan, fix it. Seriously.
There are situations where using an outsourced AML officer and compliance function makes much more sense, especially if you’re pre-revenue, entering a new jurisdiction, or trying to clean up controls before a banking review.
What regulators and banks will ask for during diligence
It helps to think ahead. If someone reviews your gambling business next month, what will they actually want to see?
- Your AML and responsible gambling policies, with gambling-specific procedures rather than generic wording
- Risk assessment covering products, geographies, payment methods, customer types, and distribution channels
- CDD and EDD workflows, including source of funds triggers and escalation paths
- Transaction monitoring rules and examples of how alerts are investigated and closed
- MLRO reporting lines, training records, and suspicious activity handling procedures
- Payment flow maps – yes, actual maps help – showing where customer funds move
- Evidence that controls operate in real life, not just inside a policy PDF
That last one matters most. A bank won’t be impressed by a lovely manual if your support team is still approving withdrawals after a one-line SOF check and no gameplay review.
Crypto gambling? Expect another layer of scrutiny
If any part of your model touches virtual assets, even indirectly through a processor or wallet provider, the questions get sharper fast.
You’ll likely need clearer wallet tracing logic, better customer profiling, stronger sanctions screening, and a very clean explanation of who does what across the flow. If users can deposit in crypto and withdraw in fiat, or the reverse, be ready to explain the controls in painful detail. Banks hate ambiguity here. Regulators too.
I’ve seen this kill a banking application that was otherwise perfectly workable.
What to do now, before someone asks awkward questions
If your gambling AML framework still feels thin, don’t try to fix everything at once. Start with the weak spots that outsiders spot fastest.
Usually that’s:
- generic risk scoring
- unclear source of funds triggers
- poorly documented withdrawal controls
- no real MLRO ownership
- payment flows that compliance can’t clearly explain
Sort those first. Then test them. Run a fake case. Pick a high-spend player profile, a suspicious deposit pattern, a withdrawal mismatch. See whether your team can actually handle it without making stuff up on the fly.
Because that’s the ugly truth. Plenty of operators have AML documents. Far fewer have AML operations.
And banks can tell the difference pretty quickly.