Enforcing Gambling Deposit Limits and Credit-Card Bans in Your Cashier: Colorado SB 26-131
Colorado now writes part of a sportsbook cashier's logic: how deposits are counted, how credit funding is caught and what players are told, with the open questions marked.
Under Colorado SB 26-131, as reporting on the law describes it, a sportsbook cashier has to refuse credit-card funding on every deposit, including money from an account that was itself funded by a credit card, and stop a player at six deposits in a 24-hour period. There is no dollar cap. Both checks belong before authorization, and both should be keyed to the player rather than to a single card.
Responsible gambling tools are the limits and controls an operator builds into its product to keep play within legal and player-chosen bounds, such as deposit limits, cool-off periods, self-exclusion and blocks on credit funding. Some, like the six-deposit limit reported in Colorado's sports betting law, are now set by statute rather than chosen by the operator.
What SB 26-131 asks of a sportsbook cashier
As reported in trade and legal coverage, the law was signed June 2, 2026 and took effect August 12, 2026. We haven't read the enrolled text, so every item below is attributed to that reporting. Confirm the details with counsel; this is a build guide, not legal advice.
- No credit-card deposits, including funds from an account funded by a credit card, according to reports.
- Six deposits per 24-hour period, as reported, with no dollar cap.
- Marketing limits, as reported: no texts or push notifications soliciting bets or deposits, and no targeting of people under 21.
- Penalties, as reported: credit-card violations are a class 2 misdemeanor, with commission fines of up to $25,000 per violation.
Treat each of those as a rule in configuration, keyed by jurisdiction, with a version number. When the regulator issues guidance that changes how a rule is read, you change a value and keep a record of when it changed.
Counting six deposits across every method
Count per player, across every stored card, bank account and wallet, not per instrument. A per-card counter lets a player with three cards make eighteen deposits, which is hard to square with a limit reported as six per 24-hour period.
The reporting says "per 24-hour period" without, as far as we've seen, defining the window. Our reading is that a rolling window is the conservative build: it never lets seven deposits fall inside any 24 hours, whereas a calendar-day reset allows six before midnight and six more just after.
-- inside the deposit transaction, before calling the processor
SELECT 1 FROM player_limits WHERE player_id = $1 FOR UPDATE; -- serialize this player's deposits
SELECT count(*) FROM deposits
WHERE player_id = $1
AND jurisdiction = 'CO'
AND status IN ('pending', 'authorized', 'captured', 'settled') -- which statuses count is an open question (below)
AND created_at > now() - interval '24 hours';
The row lock matters. Without it, two deposits submitted at the same moment each see five prior deposits and both go through. Count pending deposits too, for the same reason.
Three questions aren't answered by the reporting we have, and you should settle them with counsel rather than in code review:
- Does a declined attempt count toward the six, or only a completed deposit?
- Does a deposit that is later reversed or returned still count?
- Is the player's location at the time of the deposit what decides whether Colorado's rule applies, or the account's registered state?
Make each answer a configuration flag. If the answer changes, the code doesn't have to.
Blocking credit cards and credit-funded accounts
Use the card's funding type from BIN data, and check it at card-add and again at every deposit. BIN tables change and cards get reissued, so a card that was debit when it was saved may not be debit now.
def funding_decision(instrument, rules):
if instrument.kind == "card":
ft = bin_lookup(instrument.bin).funding_type # 'credit', 'debit', 'prepaid' or None
if ft is None:
return block("funding type unknown")
if ft not in rules.allowed_card_funding:
return block(f"{ft} cards not accepted in {rules.jurisdiction}")
return allow()
if instrument.kind == "wallet":
src = instrument.underlying_funding_type # None if the wallet doesn't say
if src is None and rules.block_unknown_wallet_funding:
return block("wallet funding source unknown")
...
Block on "unknown". A cashier that allows deposits when the BIN lookup fails has turned a vendor outage into a compliance event.
Wallets are the harder case, because the reported text reaches "an account funded by a credit card". Ask your provider exactly what funding-source data reaches you for each wallet. Where you can't see the underlying funding source, our reading is that you can't show you've excluded credit. According to reports, FanDuel's exit from credit cards on March 2, 2026 included cards linked through PayPal, Venmo and Apple Pay.
Prepaid cards need a policy decision, since BIN data tells you a card is prepaid but not how it was loaded. Debit cards remain available, and a debit deposit is still a gambling transaction: it carries MCC 7995 (or 7801 for a registered US government-licensed operator) and the quasi-cash/online gambling indicator under Visa's rules. Why issuers treat those deposits the way they do is in what a quasi-cash transaction is and why issuers treat gambling deposits like cash.
Walk through deposit controls and payment methods with the people who run VyaPay’s processor.
Talk to VyaPayShowing limits to players
Tell players what the limit is before they hit it, and tell them which rule stopped them when they do. A generic "card declined" invites the player to try another card, which fails the same way and tells them nothing about why.
- Show what's left. "4 of 6 deposits used in the last 24 hours" beside the deposit button.
- Show when the next one frees up. With a rolling window, that's 24 hours after the oldest deposit still being counted.
- Decline in the cashier, not at the network. A limit block is your decision; don't send an authorization you already know you'll refuse.
- Explain credit blocks at card-add. "Colorado law doesn't allow credit cards for sports betting deposits" is clearer than a failure at the first deposit.
- Keep marketing out of the deposit flow. SB 26-131 is reported to bar texts and push notifications soliciting bets or deposits, so a "top up now" nudge triggered by the cashier needs the player's jurisdiction checked first.
Audit logs a regulator or acquirer can read
Log every decision the rules engine makes, allow and block alike, in a form someone outside engineering can follow. When a regulator asks why a player got a seventh deposit, or an acquirer asks how you exclude credit, the answer should be a query, not an investigation.
| Field | Why it's there |
|---|---|
| Player id, jurisdiction and how it was determined | Shows which rule set applied |
| Instrument reference and BIN funding type, with the BIN table version | Shows the credit check ran on current data |
| Deposit count in the window at decision time | Shows the limit check saw the right number |
| Rule id and rule version | Ties the decision to the configuration in force that day |
| Outcome and message shown to the player | Shows what the player was told |
| Timestamp from a single clock source | Makes rolling-window arithmetic reproducible |
Write the log append-only, and reconcile it against your deposit ledger. If you're building that ledger, our guide to idempotency keys and a double-entry cashier ledger covers the schema.
What's settled and what isn't, as of November 2026
As of November 15, 2026. Reported and consistent across coverage: the August 12, 2026 effective date, the credit-card ban including credit-funded accounts, six deposits per 24 hours, no dollar cap, and the marketing limits. Open in the reporting we have: how the window is measured, whether declined or reversed deposits count, how wallet funding must be evidenced, and how prepaid cards are treated.
Colorado isn't the only pressure on credit cards. The Massachusetts Gaming Commission fined DraftKings $450,000 for accepting credit cards where they were prohibited, and DraftKings, FanDuel, BetMGM and bet365 have since ended or begun phasing out credit-card deposits, according to press reports. That shift, and what replaced cards, is covered in sportsbook payment processing after the credit-card exit. This post covers Colorado only; check each state regulator where you're licensed.
VyaPay runs its own processor and underwriting, with card, ACH and eCheck acceptance on VyaLynk. If you're a licensed sportsbook working through these controls, talk to us about your program.
Frequently asked questions
Does Colorado cap how much a player can deposit?
Not in dollars, according to reporting on SB 26-131. The reported limit is on the number of deposits, six in a 24-hour period, alongside the credit-card ban.
Can Colorado bettors still deposit with a debit card?
Reporting describes the ban as covering credit cards and accounts funded by credit cards, and nothing in the coverage we've seen extends it to debit. Each debit deposit would still count toward the reported six.
Does the six-deposit limit apply to online casinos?
SB 26-131 is a sports betting law. Colorado isn't among the seven states reported to have live legal online casinos as of November 2026, so the question doesn't arise there for casino games.
What happens if a sportsbook accepts a credit card in Colorado?
According to reports, it is a class 2 misdemeanor, and the commission can fine up to $25,000 for each violation.
Sources
- Colorado General Assembly, SB 26-131, signed June 2, 2026, effective August 12, 2026 (requirements as summarised in trade and legal reporting)
- Visa, Visa Core Rules and Visa Product and Service Rules, 24 October 2026 (sections 5.8.18.1, 7.4.5.1; decline reattempt limits)
- Visa, Visa Merchant Data Standards Manual, October 2026 (MCCs 7801, 7995)
- Massachusetts Gaming Commission, $450,000 penalty against DraftKings for accepting credit-card deposits where prohibited (as reported in trade press)
