Online gambling payments

UIGEA and Regulation GG: What Payment Processors Must Do, and What They Don't

The federal rule behind many gambling declines asks payment companies for written policies, not case-by-case verdicts. Who it covers, what it asks of card systems, and why lawful operators still get turned away.

By VyaPayPublished 7 min read

Regulation GG, the rule that implements UIGEA, requires non-exempt participants in five designated payment systems to keep written policies reasonably designed to identify and block restricted transactions. Card systems get two ways to comply. A participant that blocks a transaction it reasonably believes is restricted is protected from liability, and nothing in the rule requires blocking lawful intrastate, intratribal or horseracing activity. That combination is why lawful operators can still be declined.

Regulation GG is the federal rule that implements the Unlawful Internet Gambling Enforcement Act of 2006 (UIGEA). Issued by the Federal Reserve (12 CFR part 233) and the Treasury (31 CFR part 132) in a final rule of November 18, 2008, it sets what payment systems and their participants must do about restricted transactions. Compliance has been required since 2010.

Who does Regulation GG apply to?

It applies to non-exempt participants in the payment systems the regulation designates, and §233.3 designates five. Restricted transactions, UIGEA's term for the payments a betting business may not accept in connection with unlawful internet gambling, can move through any of them, so the policy duty follows the money into each one.

Designated payment system (§233.3)Where a gambling payment can show up
Card systemsCard deposits into a player account
Automated clearing house (ACH) systemsBank-account deposits and withdrawals
Check collection systemsPaper checks
Money transmitting businessesTransfers and wallet funding
Wire transfer systemsWires to or from an operator

The regulation exempts some participants, and those exemptions aren't covered here; a payment company should read them against its own role rather than assume it is in or out. For the card side, the participants an online casino deals with directly are its acquirer and, through the network, the issuers its players use.

What does §233.5 require?

Written policies and procedures, reasonably designed to identify and block, or otherwise prevent or prohibit, restricted transactions. That is §233.5(a), and the rest of the section shapes how far the duty goes.

  • §233.5(a) sets the duty: establish and implement the policies.
  • §233.5(b) lets a participant rely on the payment system's own policies and procedures, if those comply with the regulation.
  • §233.5(d) protects a participant from liability for blocking a transaction it reasonably believes is restricted.

The standard is "reasonably designed". Our reading is that this measures the design of the program, not its results: a policy doesn't fail because a single restricted payment got through, and it can fail if it was never built to catch them. That reading is ours, not the regulation's wording, and how an examiner applies it to a given company is a question for that company's counsel. This post describes the rule; it isn't legal advice.

The two routes for card systems in §233.6(d)

For card systems, §233.6(d) describes two ways a policy can meet the standard. One relies on knowing the merchant; the other relies on codes in the transaction.

Route 1: due diligence at account openingRoute 2: a code system
What it doesChecks the merchant's legal authority before it can accept cardsLets the network or the issuer recognize and deny possibly restricted transactions as they happen
For a gambling customerEvidence of legal authority (a license that expressly authorizes internet gambling, or a reasoned legal opinion); a written commitment to report changes; a third-party certification that systems keep activity within licensed limits, including age and location verificationMerchant or business category codes and transaction codes on authorizations
Across the bookNotice to all commercial customers that restricted transactions are prohibitedOngoing monitoring that merchants are coded correctly, and of suspicious volume patterns

In practice the two can run side by side. Visa's rules require online gambling to carry MCC 7995 and, in the US, the quasi-cash/online gambling indicator, which is the kind of code Route 2 describes, and an acquirer boarding a gambling merchant can collect the documents Route 1 lists. How issuers act on the codes is in our explainer on quasi-cash transactions and gambling deposits.

What the due-diligence route asks of an online casino

Three documents, and each one is more specific than it first looks.

  1. Evidence of legal authority. The regulation's first example is a license that expressly authorizes internet gambling. A land-based license, or a license for a different product, doesn't say that on its face. The alternative is a reasoned legal opinion explaining why the activity is lawful.
  2. A written commitment to report changes. If the license lapses, narrows or is suspended, the acquirer is supposed to hear it from the merchant.
  3. A third-party certification. Someone other than the operator certifies that its systems keep activity within licensed limits, and the regulation names age and location verification specifically.

That list maps onto what an acquirer can ask for when it underwrites a casino, which is set out document by document in our guide to the online casino underwriting file. The age and location piece, and what underwriters want to see behind a certification, is in our guide to KYC, age and geolocation checks.

Questions about your legal-authority file?

VyaPay underwrites risk in-house, so you talk to the team that makes the underwriting call. Tell us about your program.

Talk to VyaPay

What Regulation GG doesn't require

It doesn't require anyone to block lawful intrastate gaming, lawful intratribal gaming, or activity under the Interstate Horseracing Act of 1978. Nothing in the regulation requires or suggests blocking transactions from those excluded activities. On our reading, a player located in a state with licensed online casinos, depositing with a casino licensed there, is the kind of activity the exclusion covers.

The duty itself is met through policies: diligence on the merchant, codes in the transaction, or reliance on the payment system's own compliant policies. And participants remain free to decline gambling, lawful or not.

Why do lawful operators still get declined?

Because the regulation protects blocking and leaves approval to each participant. Put §233.5(d) next to the exclusions: a participant that declines a transaction it reasonably believes is restricted has no liability for it, and the regulation leaves it free to decline the lawful activity it excludes. Our reading is that a cautious participant can therefore decline gambling as a category without sorting lawful from unlawful. An issuer working from the code route sees a betting code and an indicator, not a license, and can decide on that basis alone.

For an operator, the practical consequences are three:

  • The acquirer relationship is where your legal authority gets recognized. Make the Route 1 file complete.
  • Correct coding is what lets issuers that do accept lawful gambling approve you. Anything that obscures the code makes the category look worse to everyone.
  • Other designated systems carry the same duty. ACH, for instance, is a designated payment system too, so a bank-funded deposit faces its own participants' policies rather than none.

What this means for a payment processor

A processor needs a written program that it can show was designed to keep restricted transactions out, and a file for each gambling merchant that supports the choices it made. In our reading, that comes to four things: due diligence at boarding that collects the Route 1 documents; correct coding and the indicator on every online gambling transaction; monitoring for miscoding and volume patterns that don't fit the merchant's license; and notice to every commercial customer that restricted transactions are prohibited.

VyaPay runs its own processor and underwrites risk in-house, so the diligence file and the processing decisions sit with one risk team. If you're a licensed operator and want to talk through what your legal-authority documents need to show, talk to us about your program.

Frequently asked questions

Is state-licensed online gambling a restricted transaction under Regulation GG?

The regulation excludes lawful intrastate gaming, lawful intratribal gaming and Interstate Horseracing Act activity, and says nothing in it requires or suggests blocking them. Whether a given operator's activity is lawful intrastate gaming is a legal question about its license and its players' locations.

Which agencies issued Regulation GG?

The Federal Reserve Board, as 12 CFR part 233, and the Treasury Department, as 31 CFR part 132. The joint final rule appeared at 73 FR 69405 on November 18, 2008.

Can a bank refuse a licensed online casino's transactions?

Yes. Regulation GG protects a participant that blocks a transaction it reasonably believes is restricted and leaves participants free to decline lawful gambling. Acceptance is each participant's own policy.

Who does the age checks under Regulation GG's due-diligence route?

The merchant. The participant collects a third-party certification that the gambling merchant's own systems keep activity within licensed limits, including age and location verification.

Sources

Talk to the team that underwrites you

Tell us about your licenses, your markets and your volume. You'll be talking to the people who run VyaPay's processor and make its risk decisions.

or call 833-4-VYAPAY

Let’s meet up!

Tell us about your business and someone from our team will reach out.