Can a Payment Facilitator Sign Gambling Merchants? Visa's High-Integrity Risk PayFac Rules
Visa's rules let a payment facilitator sponsor gambling merchants, but only inside a registration chain the acquirer owns, and the acquirer gets the bill when that chain is incomplete.
Yes, but not under an ordinary PayFac registration. Visa lets a payment facilitator sponsor gambling merchants only when its acquirer holds High-Integrity Risk Acquiring registration, the PayFac is registered as a high-integrity risk PayFac, a senior officer of the PayFac signs the sponsored-merchant agreement, and each casino on the platform is registered and monitored. Visa assesses the acquirer if the PayFac isn't registered as required, so the acquirer decides.
A payment facilitator (PayFac) is a company that signs merchants as sponsored merchants under its own acquirer relationship, then boards, funds and supports them itself instead of having each one contract directly with an acquirer. Under the Visa Core Rules, a PayFac considered high-integrity risk, such as one sponsoring online gambling merchants, must also register as a High-Integrity Risk PayFac.
What Visa requires before a PayFac boards its first casino
Several registrations have to be in place before the first deposit, and the PayFac completes none of them alone. They run through the acquirer, the Visa member that answers for every transaction the platform submits.
| Requirement | Visa Core Rules | Who carries it |
|---|---|---|
| Acquirer approved for High-Integrity Risk Acquiring, after a financial review and with good standing in Visa's risk programs | §1.9.5.1 | Acquirer |
| PayFac registered as a High-Integrity Risk PayFac, even if it is already registered as a PayFac | §5.3.1.3 | Acquirer registers; PayFac supplies the file |
| Each high-integrity risk sponsored merchant registered | §1.9.5.1 | Acquirer |
| Agents that solicit these merchants registered as high-risk agents | §1.9.5.1 | Acquirer |
| High-integrity risk sponsored-merchant agreement signed by a senior officer of the PayFac | §10.4.6.1 | PayFac |
| New high-integrity risk sponsored merchants reported, plus monthly activity for all of them | §10.4.6.1 | PayFac |
| Daily monitoring of each merchant against its own baseline | §10.4.5.2 | Acquirer, using the PayFac's data |
The financial review in §1.9.5.1 looks at the acquirer's capital, an investment-grade rating or compensating controls such as collateral, and Visa may add an on-site review. Already holding a PayFac registration for other categories doesn't shorten any of this: §5.3.1.3 is explicit that high-integrity risk status needs its own registration.
Mastercard runs its own program. According to acquirer notices it is now the Specialty Merchant Registration program, took effect in the US on July 24, 2026 for most categories after a late-2025 overhaul, and covers non-face-to-face gambling under 7801, 7802 and 7995. How the two networks' programs line up is covered in the Visa Integrity Risk Program and Mastercard's Specialty Merchant Registration.
Who pays when a PayFac's gambling book breaks the rules?
The acquirer pays Visa's assessments. §12.3.1.1 sets an assessment of USD 25,000 per month for each high-integrity risk PayFac the acquirer fails to register as required, rising to USD 100,000 per 30-day period once it has three violations in a calendar year. The platform isn't on the invoice.
That shapes the contract a platform gets offered. Our reading is that an acquirer looking at those numbers will push the risk down to the PayFac through indemnities, reserves and audit rights, and will want the right to remove any sponsored merchant quickly. Visa gives it grounds to. Under §10.4.6.2, Visa may require the acquirer to contract directly with a sponsored merchant that generates excessive exception items (disputes and credits) over 12 months, or that takes action to evade responsibility for compliance with the Visa Rules. The same section lets Visa disqualify a high-integrity risk PayFac or sponsored merchant under VAMP, and §10.4.5.4 adds disqualification for a merchant that reaches a critical level of disputes or acts to circumvent Visa's programs.
A forced direct contract is quieter than a termination, but the platform still loses: the casino leaves your book and takes its processing revenue with it.
Walk through your sub-merchant model with the people who decide risk at VyaPay.
Talk to VyaPayWhat the acquirer watches on each sponsored casino
It watches each casino as a merchant in its own right, as well as the platform. §10.4.5.2 requires the acquirer to track daily gross volume, average ticket, receipt count and disputes for every high-integrity risk merchant and PayFac, build a baseline over at least one month, begin daily monitoring on the 31st day after the first deposit, review weekly and re-baseline monthly.
Two things follow for the PayFac. Our reading is that the acquirer will want activity broken out per sponsored merchant and per day, in a form it can load, because a monthly platform summary can't feed a daily monitor. And the acquirer must give Visa the original underwriting package and its monitoring records within seven calendar days if asked. If you did the sub-merchant underwriting, that package is yours to produce, so build it to be handed over.
Coding is checked per merchant too. §5.8.18.1 requires online gambling transactions to carry MCC 7995 "even when gambling services are not the merchant's primary business", plus, in the US, the quasi-cash/online gambling indicator. A sponsored merchant that can't separate gambling from its other sales has to code all of them as gambling and tell cardholders they may appear that way on statements. Visa's merchant manual also defines 7801 and 7802 for US government-licensed operators that are registered with Visa; which code a casino gets follows the acquirer's registration.
A sub-merchant onboarding checklist for casino platforms
A player account management (PAM) or white-label platform that boards operators as sponsored merchants needs a file on each one that would survive the seven-day request above. The list follows the rules cited in this post; your acquirer will add its own items.
- A license for every jurisdiction the operator serves. §5.8.18.1 requires a valid license or other appropriate authority to operate the site or app. Map each license to the domains and apps it covers.
- Evidence of legal authority for internet gambling. Regulation GG's card-system due-diligence route (12 CFR 233.6(d)) looks for a license that expressly authorizes internet gambling or a reasoned legal opinion, a written commitment to report changes, and a third-party certification that the operator's systems keep activity within licensed limits, including age and location verification.
- Merchant name and descriptor. §1.5.1.12 requires the name the operator primarily uses with players, shown on its site and used consistently from authorization through dispute records. A platform running several brands needs a name per brand that a player would recognise on a statement.
- MCC and indicator. Confirm the code your acquirer's registration supports, and that the quasi-cash/online gambling indicator is set in every authorization request and clearing record (§7.4.5.1).
- Ownership and principals. Visa's prohibition powers in §1.9.1.4 reach principals as well as companies, so know who they are and ask about prior merchant terminations.
- Processing and dispute history. Statements and dispute data from any prior provider, so the acquirer's baseline starts from something real.
- Senior-officer signature. The high-integrity risk sponsored-merchant agreement needs one (§10.4.6.1). Put it on the checklist so an auditor doesn't find it missing.
- A monthly reporting feed. New high-integrity risk sponsored merchants, and monthly activity for all of them, have to be reported (§10.4.6.1).
The operator-side version of this file, for casinos applying directly, is in the underwriting file acquirers ask online casinos for.
Can a PayFac carry casinos under its existing registration?
No. A PayFac registered for ordinary merchants that starts boarding casinos without high-integrity risk registration puts its acquirer outside §5.3.1.3 and §1.9.5.1 from the first transaction. Coding those casinos under a non-gambling MCC doesn't change what they are: §5.8.18.1 ties the code to the activity, and Visa's glossary counts funding an account set up for the purpose of gambling as online gambling.
Visa's rules also cover a casino's deposits being presented through some other merchant on the platform. Visa calls that laundering (transactions that don't result from an act between the cardholder and the merchant presenting them), and §1.9.1.4 lists it among the grounds on which Visa may permanently prohibit a merchant, a PayFac or a sponsored merchant, along with their principals. An acquirer already carrying the registration exposure described above has every reason to look for it.
Building a PayFac or using PayFac-as-a-Service
A platform has two broad routes: register and operate as a PayFac itself, carrying every obligation above, or offer payments under its own brand through a provider's program without building a payment facilitator. VyaPay's PayFac-as-a-Service is the second kind. You offer payments under your brand and share revenue, and VyaFac handles sub-merchant boarding, funding and reporting, including split deposits that divide a sale among merchant, platform and agent.
Whether a gambling program fits that model is an underwriting question, decided per platform, per operator and per state. VyaPay runs its own processor and makes its own risk decisions, so the team that answers the question is the team that reviews the book afterwards, with no separate processor upstream applying its own appetite to your sub-merchants. That stacked chain, and why casino accounts get cut off inside it, is the subject of why online casinos get cut off by processors they've never met. If you run a casino platform, talk to us about your program.
Frequently asked questions
What is the difference between a PayFac and an ISO?
An ISO sells merchant accounts that each merchant signs with the acquirer. A PayFac signs merchants itself, as sponsored merchants under its own acquirer relationship, and handles their boarding and funding. For gambling, Visa's rules require the acquirer to register both: the PayFac as a high-integrity risk PayFac and the ISO or agent as a high-risk agent.
Does 3D Secure protect a PayFac's casino sub-merchants from fraud chargebacks?
Not in the US. §5.8.4.6 says 3-D Secure authenticated transactions at MCCs 7801, 7802 and 7995 aren't eligible for protection from Dispute Condition 10.4 (Other Fraud – Card-Absent), so a cardholder can still raise a fraud dispute on an authenticated deposit.
Can Visa take a casino away from its PayFac?
Visa acts through the acquirer. In two stated cases, a sponsored merchant with excessive exception items (disputes and credits) over 12 months or one that takes action to evade responsibility for compliance with the Visa Rules, §10.4.6.2 lets Visa require the acquirer to contract with the casino directly, which in our reading would end the PayFac's sponsorship of it. Separately, Visa may disqualify the casino or the PayFac under VAMP.
Is a sweepstakes casino a gambling merchant for a PayFac?
For coding, yes: Visa's merchant manual lists sweepstakes under MCC 7995. State-law trackers list several states that now ban online sweepstakes casinos, and New York's ban names payment processors outright, so a platform should treat them as a separate decision from licensed operators.
Sources
- Visa, Visa Core Rules and Visa Product and Service Rules, 24 October 2026 (sections 1.5.1.12, 1.9.1.4, 1.9.5.1, 5.3.1.3, 5.8.4.6, 5.8.18.1, 7.4.5.1, 10.4.5.2, 10.4.5.4, 10.4.6.1, 10.4.6.2, 12.3.1.1)
- Visa, Visa Merchant Data Standards Manual, October 2026 (MCCs 7801, 7802, 7995)
- 12 CFR Part 233, Regulation GG (Prohibition on Funding of Unlawful Internet Gambling), via Cornell LII
- Mastercard, Specialty Merchant Registration program, as described in acquirer notices (US effective date July 24, 2026)
