How to accept crypto payments for igaming
iGaming operators accept crypto payments by integrating either a Bitcoin / Lightning processor or a stablecoin gateway, replacing card processing with rails that have no chargebacks, settle in seconds, and price around 0.5% to 1% of volume. The savings come from avoiding interchange, scheme, and high-risk surcharges layered on top of card processing. The cost is mostly operational: player wallet adoption, compliance, and treasury work that the card stack hides.
Why do card processors charge iGaming operators more than other businesses?
Card processors classify iGaming as a high-risk merchant category. The classification triggers extra fees on top of the standard interchange-plus-scheme-plus-markup stack that applies to every card transaction. The premium reflects two real costs to the processor: high chargeback ratios (player disputes settle differently from regular consumer disputes), and the regulatory burden of iGaming acceptance across jurisdictions. The result is an effective rate that lands meaningfully higher than the headline rates published for general e-commerce.
The base of the card cost is the same as it is for any other merchant. As the Federal Reserve documents:
The Electronic Fund Transfer Act requires the Federal Reserve Board to biennially publish data on costs incurred, and interchange fees charged or received, by debit card issuers and payment card networks.
Interchange is a floor the merchant cannot negotiate. iGaming operators pay that floor plus the scheme fee plus the processor markup plus the high-risk surcharge. The standard published rate, before that surcharge, is already material: Stripe's pricing page lists 2.9% + $0.30 per online card transaction for domestic cards (Stripe pricing). For high-risk verticals, processors add on top of that or quote interchange++ pricing with significantly wider markups.
What does it actually cost to accept cards as an iGaming operator?
The all-in cost for card-accepting iGaming operators stacks several layers that do not all show up on one invoice. The headline rate is the most visible. The chargeback and reserve costs eat margin quietly. The structural delay in settlement (T+1 to T+2, sometimes longer for high-risk merchants) costs working capital. Together these numbers explain why iGaming acceptance via cards is the most expensive payment method most operators run.
| Cost component | What it is | Magnitude |
|---|---|---|
| Interchange + scheme + processor markup | The standard card-acceptance stack (Visa) | Comparable to the published 2.9% + $0.30 e-commerce rate (Stripe pricing) before any risk adjustment |
| High-risk surcharge | Premium for iGaming MCC codes, layered on top of the standard stack | Multiple percentage points above the standard rate, varies by processor |
| Chargeback fees | Per-dispute fee on top of the refunded amount | $15 to $25 per chargeback per Visa and Mastercard scheme rules |
| Rolling reserve | Percentage of volume the processor holds for 6 to 12 months against future disputes | 5% to 10% of monthly volume, locked |
| Settlement delay | Days between transaction and funds arriving | T+1 to T+2 standard, often longer for high-risk merchants |
| Geographic restrictions | Some issuing banks block iGaming MCC codes outright | A material slice of attempted deposits get declined at the issuer |
The reserve and the settlement delay are the parts most operators underestimate. A 7% rolling reserve on $10M monthly volume is $700,000 of working capital tied up at any moment. Card processing is not just expensive on a per-transaction basis. It is also slow money.
How does accepting crypto change the cost structure for iGaming?
Crypto payment rails remove the entire card stack: there is no interchange, no scheme fee, and no chargeback protocol. The processor still charges a fee (typically 0.4% to 1% of volume on managed gateways, per public pricing pages), but the floor that interchange creates on cards does not exist. The structural absence of chargebacks is the second large saving. Settlement is in seconds rather than days, which releases the working capital that rolling reserves trap.
The savings split into three buckets:
- Processing fee compression: Card all-in cost lands in the high single digits for high-risk iGaming. Crypto gateways generally land between 0.5% and 1.5% before any vertical adjustment, and most do not surcharge iGaming.
- Zero chargebacks: Lightning and on-chain payments are non-reversible by protocol design. No chargeback fee, no reserve, no dispute team. The trade-off, which is worth naming honestly, is that the player loses the chargeback right too. Operators handle player complaints out of band the same way they handle any non-card refund.
- Instant settlement: A Lightning payment settles in seconds. Live network metrics across thousands of nodes are tracked publicly on the Amboss Space Lightning explorer. Funds land in the merchant's wallet immediately, releasing the working capital that card reserves lock up.
Visa documents the card pricing structure clearly:
Merchants negotiate and pay a "merchant discount" to their financial institution that is typically calculated as a percentage per transaction.
Crypto rails do not have a merchant discount of that shape. There is a published per-transaction fee and a network fee, both of which are visible upfront.
Which crypto rails make sense for iGaming today?
Three rails dominate iGaming crypto acceptance: Bitcoin on Lightning, stablecoins on Lightning, and stablecoins on faster L1s like Tron or Solana. The choice depends on the geographic mix of the player base and the operator's preference for volatility exposure.
Bitcoin on Lightning gives the lowest fees and the strongest finality guarantees, but requires the player base to hold bitcoin. Stablecoin acceptance (USDT, USDC) on Lightning is the largest growth area: it gives players the dollar-denominated stability they expect at checkout, with Lightning's settlement speed and cost (Tether overview of USDT issuance shows the scale of the stablecoin market the operator is plugging into). Stablecoins on Tron or Solana are still popular for purely consumer-facing flows because of existing wallet penetration, but multi-chain support multiplies the operator's custody and compliance surface.
A practical pattern is to start with one rail for an MVP launch, observe deposit and withdrawal patterns from real players, then add a second rail when the data justifies it. Starting with two rails simultaneously doubles the integration and compliance work for no real customer benefit until traffic confirms it.
How do you handle KYC, sanctions screening, and AML for crypto payments in iGaming?
iGaming has compliance obligations whether the rails are cards or crypto. The KYC obligation on player onboarding does not change. The sanctions screening obligation on individual transactions does change: card networks screen issuing banks; crypto rails require the operator (or the operator's payment provider) to screen the source address against OFAC and equivalent lists at the time of acceptance.
The screening is automatable. Major stablecoin issuers like Circle publish the regulatory framework they operate under (Circle transparency), and a similar shape applies to iGaming operators accepting crypto: every incoming address is screened against sanctions lists, every flagged address triggers manual review or auto-refusal. The right altitude is to handle this once at the payment processor layer rather than build it per operator.
Amboss offers Reflex as a compliance layer that screens incoming Bitcoin and stablecoin addresses against OFAC and equivalent lists at the time of payment acceptance. For operators in regulated jurisdictions, pairing the payments API with a compliance product like Reflex is the difference between a workable production deployment and an audit-finding waiting to happen.
What does the player experience look like for crypto deposits and withdrawals?
The player flow is simpler than card flows: scan a QR code, approve in the wallet, see the deposit credited within seconds. There is no 3D Secure step, no issuer-side decline, no holding period. Withdrawals run in the opposite direction with the same characteristics: the player provides an invoice or address, the operator pays it, the funds arrive in seconds.
The friction shifts from the payment moment to wallet ownership. Players who already hold crypto have a fast checkout. Players who do not need an on-ramp step that the operator either provides directly, partners with, or leaves to the player. The on-ramp share of deposits used to be near 100% (every crypto deposit started from a fiat-to-crypto conversion); for many iGaming player bases today that share has fallen meaningfully as crypto-native players bring their own balances. The exact mix depends on jurisdiction and player demographic.
The withdrawal experience is where crypto's advantage compounds. Card withdrawals (payouts back to the player's card) often take 3 to 5 business days, vary by issuer, and have their own fee schedule. Crypto payouts land in seconds, with no holdback. Player satisfaction surveys at large iGaming operators consistently cite withdrawal speed as a top driver of retention; crypto rails win that comparison structurally.
Where does Amboss Rails fit for an iGaming operator?
Amboss Rails is the payments and yield infrastructure most directly built for the iGaming use case described above: 0.5% on payment volume, no chargebacks by protocol, instant settlement on the Bitcoin payment network, and pairing with Reflex for sanctions screening at acceptance time. The Rails product also lets operators who hold bitcoin in treasury deploy that capital to earn fees from the same payment flow the business is processing, which can offset part of the gateway fee for operators willing to hold native bitcoin. Rails is not the right pick if you only want a multi-chain stablecoin processor with embedded fiat off-ramp. For operators whose payment volume justifies a single-rail consolidation and whose treasury can absorb bitcoin exposure, Rails is one of the two or three places worth comparing against your current acquirer.
Frequently asked questions
Are crypto payments legal for iGaming operators?
Crypto payment acceptance for iGaming is legal in most jurisdictions where iGaming itself is licensed, but the rules vary widely by country and US state. The operator's existing iGaming license usually permits any payment method that meets the same KYC and AML obligations. Some regulators have specific crypto-payment guidance; some do not. Confirm with counsel in each jurisdiction before launch.
What is the realistic cost saving versus cards?
The honest answer is that the saving depends entirely on how high-risk your current card processor classifies you and what reserve they hold. For typical iGaming operators paying high single-digit effective rates on cards, the cost saving of switching the chargeable portion of volume to crypto is several percentage points of revenue. The released reserve and the absence of chargeback fees can compound that further.
How do players actually pay in crypto?
The player opens a Lightning wallet (a self-custodial app or a custodial account at an exchange), scans the QR code or pastes the invoice the operator generates, and approves the payment. The whole flow is comparable in steps to a wallet pay flow on cards. Operator-side, the payment confirmation arrives within seconds via webhook or API event.
Do you need to hold bitcoin or stablecoin to accept crypto payments?
No. Most operators receive crypto and convert to fiat through a partner conversion service, or auto-convert at acceptance time via the gateway. The operator's treasury can hold zero crypto at any given moment. Operators who choose to hold bitcoin natively can additionally deploy it in products like Amboss Rails to earn fees on the same payment network they accept on.
What happens if a player claims they did not authorize a deposit?
Crypto payments are non-reversible by protocol. The operator handles the complaint the same way it would handle a complaint about a non-card payment method (bank transfer, voucher): investigation, KYC review, partial or full refund issued as a new outbound payment if warranted. The chargeback channel that cards expose does not exist on crypto rails, which is both the saving and the customer-protection trade-off.
Can you run crypto and card payments side by side?
Yes, and most operators do during the transition. Players choose their preferred method at deposit; the operator routes accordingly. Over time the card-vs-crypto mix shifts based on incentives (some operators offer a small bonus for crypto deposits to accelerate adoption) and player demographics. There is no operational requirement to deprecate cards on day one of crypto launch.