KYC, Age and Geolocation Checks: What Payment Processors Expect From Online Casinos
A processor can't verify your players, but it has to be able to show that you do. Here is where that obligation comes from, why Visa's own age tool doesn't apply, and the evidence underwriters ask for.
Payment processors expect an online casino to verify each player's identity, age and location before money moves, and to prove it with evidence a third party has checked. One source of that expectation is Regulation GG: its card-system due-diligence route asks a gambling customer for a third-party certification that its systems keep activity within licensed limits, including age and location verification. Visa's own age-check service is excluded for gambling, so the controls have to be yours.
KYC (know your customer) in online gambling is the set of checks an operator runs to establish who a player is, that the player is old enough to play, and that the player is located where the operator's license allows play. Payment processors look for it in part because federal rules on gambling payments ask for evidence that these controls exist and work.
Why a payment processor cares about your player checks
Because the processor's own compliance file depends on them. Regulation GG (12 CFR part 233, implementing the Unlawful Internet Gambling Enforcement Act) requires non-exempt participants in designated payment systems, card systems among them, to have written policies and procedures reasonably designed to identify and block restricted transactions (§233.5(a)). For card systems, §233.6(d) offers a due-diligence route at account opening. For a gambling customer, it looks for three things:
- Evidence of legal authority: a license that expressly authorizes internet gambling, or a reasoned legal opinion.
- A written commitment from the operator to report changes in that legal authority.
- A third-party certification that the operator's systems keep its activity within licensed limits, including age and location verification.
The third item turns your player controls into part of the payment file. A processor can't check every player. What this route asks for is an independent party's certification that you do. This is a general description of the regulation, not legal advice; how processors read the rest of it is in our explainer on UIGEA and Regulation GG.
Visa's rules add the license requirement directly: under §5.8.18.1, an online gambling merchant must hold a valid license or other appropriate authority for its site or app. The license, and its conditions on who may play and from where, is the operator's; the processor's interest is that you meet it.
What the third-party certification should cover
Regulation GG's wording is short: systems that keep activity within licensed limits, including age and location verification. Our reading of what that means in practice is that the certification should speak to how each limit in your license is enforced by your systems, not to a policy that says it is.
- Identity. How a player is verified at sign-up, what data sources are used, and what happens to an account that fails or can't be verified.
- Age. How the minimum age in each of your licenses is enforced, and at what point in the flow.
- Location. How a player's location is established at the time of play, how often it is rechecked during a session, and what happens when a check fails.
- Scope. Which brands, sites, apps and states the certification covers. A certification for one state's product may not cover the next state you launch.
The certifier has to be a third party, which rules out a self-assessment. Keep the certification current; a version that predates your last product launch describes a system you no longer run.
Age checks: why Visa's own tool is off the table
Visa offers Age Validate and Birthdate Validate services, and the 24 October 2026 rules exclude gambling from them. Under the new provisions in §7.3.13, the services can't be used by merchants with MCCs including 7995, 7800, 7801 and 7802 (along with 5816 and several others), and their results can't be used as satisfying a legal obligation.
Two consequences follow. A casino or sportsbook can't use the network's age check at all. And even where a merchant in another category uses it, Visa says the answer isn't proof of legal compliance. Age verification for gambling has to come from your own KYC process or your KYC vendor, documented well enough to hand to a certifier and an underwriter.
Walk through your KYC, age and location controls with the people who make VyaPay’s risk decisions.
Talk to VyaPayGeolocation: showing the player is inside the licensed state
Online casino and sports betting licenses are issued by states, so location is a licensing condition. Seven states had live licensed online casinos as of November 2026, according to industry reporting, and each license covers players physically within that state. The state map is in where online casinos are legal in the US.
Underwriters ask about geolocation because it connects to the money in two places. A deposit from a player outside the licensed footprint funds play the license doesn't authorize. And under Visa's §5.8.18.3, winnings paid to a card must come from a wager that was lawfully made and properly identified; our reading is that location records are part of showing a wager was lawful.
Legislatures have noticed the location layer too. New York's S5935A lists "geolocation provider" among the companies barred from supporting online sweepstakes games in the state, alongside financial institutions and payment processors. In New York, at least, location vendors sit in the same sentence of the statute as processors.
Expect questions about the vendor and method, how location is established for web and app players, how often checks run during a session, and how failed or inconclusive checks are handled. The answer an underwriter wants is a description of what your system does, backed by reports, not a list of vendor features.
What underwriting asks to see
Evidence, in documents an underwriter can file. The acquirer may have to hand your original underwriting package to Visa within seven calendar days of a request (§10.4.5.2), so it wants a file that explains itself.
| Item | What it shows |
|---|---|
| Licenses for every state served, with conditions | Legal authority, and the limits the controls must enforce |
| Third-party certification report and its scope | Independent confirmation of age and location controls (Regulation GG) |
| KYC vendor contract and configuration summary | What identity and age checks run, and on whom |
| Geolocation vendor contract and sample reports | How location is established and how failures are logged |
| Blocked-attempt statistics by reason | That the controls stop people, not only describe stopping them |
| Written commitment to report changes in legal authority | That the file will stay true (Regulation GG) |
| Record-retention policy for KYC and location logs | That the evidence will exist when a dispute or audit needs it |
The full application file, including ownership, processing history and dispute data, is in how to get an online casino merchant account.
KYC before money moves, and when a player disputes
Run KYC before the first deposit if you can, and before the first withdrawal at the latest. A player verified at sign-up doesn't need an identity review at withdrawal; one verified late creates a queue at the moment they want to be paid.
Match payment instruments to the verified person. The name on a debit card or bank account should match the player, and for ACH, Nacha's rules have required account validation on first use of an account number for WEB debits since March 2021. That validation confirms the account, not the person, so it complements KYC rather than replacing it.
Keep the records for disputes. In the US, 3-D Secure doesn't remove fraud-dispute exposure at gambling MCCs: §5.8.4.6 says authenticated transactions at 7801, 7802 and 7995 aren't eligible for protection from Dispute Condition 10.4 (Other Fraud – Card-Absent). When a player says a deposit wasn't theirs, your KYC records, device data and location logs are the evidence you have to work with.
VyaPay runs its own processor and underwrites in-house, so the team that reads your KYC and location file at boarding is the team that reviews the account afterwards. If you're a licensed operator preparing an application, send us your file questions.
Frequently asked questions
Can an online casino use Visa's Age Validate service?
No. The October 2026 Visa rules bar merchants under MCCs 7995, 7800, 7801 and 7802, among others, from using Age Validate and Birthdate Validate, and say the results can't satisfy a legal obligation in any case.
Does the payment processor run KYC on my players?
Player verification is the operator's job. The processor runs its own checks on you as the merchant and asks for evidence of yours, including the third-party certification Regulation GG describes.
Is a gambling license enough for a processor to approve me?
A license is necessary but not sufficient. The acquirer also has to register you with Visa as a high-integrity risk merchant, your transactions have to be coded correctly, and the processor can ask for the Regulation GG certification of age and location controls along with the rest of the underwriting file.
Do geolocation rules apply to deposits as well as bets?
The license governs play, and Regulation GG's certification speaks to keeping activity within licensed limits. Our view is that checking location at deposit as well as at wager time is the simpler file to defend; confirm what your regulator requires.
Sources
- 12 CFR Part 233, Regulation GG, via Cornell LII (sections 233.3, 233.5, 233.6)
- 31 U.S.C. 5361–5367, Unlawful Internet Gambling Enforcement Act, via Cornell LII
- Visa, Visa Core Rules and Visa Product and Service Rules, 24 October 2026 (sections 5.8.4.6, 5.8.18.1, 5.8.18.3, 7.3.13, 10.4.5.2)
- New York State Senate, S5935A, signed December 5, 2025
- Nacha, Nacha Operating Rules (WEB debit account validation, effective March 2021)
