Payments Guide · 2026
iGaming payments in 2026: PSPs, the cashier, payouts and payment API integration
Casino payments run through three layers: the cashier the player sees, an orchestration layer that routes each transaction, and the payment service providers and acquirers that move the money. Gambling is a high-risk category for card networks, so what matters is not one gateway but approval, routing, payouts and reconciliation working together in every market. The rules moved again in 2026: Ireland’s credit card ban arrived with the Gambling Regulation Act from 5 February 2026, and Brazil’s provisional measure of 25 September 2026 barred banks and payment institutions from processing bets.
The short version
- The stack is cashier, orchestration, PSPs and acquirers; each fails in a different way.
- Card transactions for gambling carry MCC 7995, which networks and issuers treat as high-risk.
- Credit cards are banned for gambling in Great Britain, Ireland and for online wagering in Australia.
- Regulators expect closed-loop payouts: winnings go back to the method used to deposit.
- A payment API integration lives or dies on webhooks, idempotency and daily reconciliation.
The payment stack: cashier, orchestration, PSPs and acquirers
An acquirer is the institution that processes a merchant’s card payments through the card networks. A payment service provider collects the transaction data and passes it on; one company can be both. On top of them, casino operators add two layers of their own.
| Layer | Its job | What goes wrong |
|---|---|---|
| Cashier | The deposit and withdrawal screens players use, with methods per market | Methods players do not use, unclear decline messages |
| Orchestration | Decides which provider gets each transaction, with retries and failover | One provider down takes all deposits with it |
| PSPs and acquirers | Authorise and settle the money | Declines, holds, slow payouts |
| Wallet and ledger | Credits the balance and records every movement | Balances that do not match provider reports |
The cashier and the wallet sit in the iGaming platform; orchestration can be part of it or a separate service.
Why casino payments are high-risk: MCC 7995, underwriting and 3-D Secure
Card transactions for betting and casino gaming carry merchant category code 7995, which Visa defines as betting, including casino gaming chips and wagers. Card networks run integrity programmes that place gambling among high-risk categories, and some card issuers decline 7995 transactions by default. That is why approval rates differ so much between providers and markets.
In the European Economic Area, strong customer authentication has applied to most online card payments since 14 September 2019, usually through 3-D Secure. A successfully authenticated payment shifts liability for fraud chargebacks to the card issuer, which matters in a category with high dispute rates. Card networks also monitor merchants’ chargeback and fraud ratios through their own programmes, so dispute handling is part of keeping a merchant account.
Payment providers underwrite the operator, not the platform. Expect questions about your licence, markets, ownership and anti-money-laundering controls before any account goes live.
Who can pay how: market rules in 2026
| Market | Rule | Since |
|---|---|---|
| Great Britain | Credit cards banned for gambling, including e-wallets funded by credit card unless blocked | 14 April 2020 |
| Ireland | Credit cards banned under the Gambling Regulation Act 2024 | Commencement from 5 February 2026 |
| Australia | Online wagering providers may not accept credit cards, credit-linked products or digital currency | 11 June 2024 |
| Brazil | Betting banned by provisional measure; banks and payment institutions barred from processing bets | 25 September 2026 |
| India | The Promotion and Regulation of Online Gaming Act 2025 bars banks and payment processors from facilitating online money games | 2025 Act |
Before the ban, Brazil’s 2024 rules allowed only Pix, bank transfers and debit or prepaid cards, with withdrawals to the bettor’s own registered account. We covered the shutdown in Brazil bans online betting and casino. The lesson for any market: payment rules change faster than platforms, so methods must be switchable per jurisdiction.
Payouts, closed loop and identity checks
The UK Gambling Commission calls closed-loop payments best practice: withdrawals and winnings go back to the method used to deposit. It describes open-loop systems as a known money laundering risk and rates crypto as a high-risk payment method. In practice, a cashier splits each withdrawal back across the player’s funding methods, up to what was deposited through each.
Identity checks belong before the money moves, not at withdrawal. In Great Britain, operators must verify identity before customers gamble and may not ask at withdrawal for information they could reasonably have requested earlier. In the EU, the anti-money-laundering directive requires customer due diligence when a player collects winnings or wagers EUR 2,000 or more in a single or linked transaction. Our crypto casino payments analysis covers digital currency in more detail.
Integrating a payment API: webhooks, idempotency and reconciliation
- Idempotency: send a unique key with every payment request, so a retry after a timeout never creates a second charge or payout.
- Webhooks: acknowledge quickly, verify the signature, store the event before processing it, and deduplicate on the provider’s reference. Adyen, for example, retries notifications that are not acknowledged within ten seconds.
- Status mapping: translate every provider status into one set of wallet states, so pending, settled, refunded and charged back mean the same thing everywhere.
- Reconciliation: match each provider’s report against your ledger every day; every PSP reports in its own format.
- Failover: route to a second provider when the first declines or goes down, without double-charging.
The same discipline applies to game wallets; our reporting and reconciliation guide covers the casino side.
Seven questions for a payment provider
- Which of my markets and licence types do you accept?
- Which local methods can you offer in each market, for deposits and for payouts?
- How do routing, retries and failover work when a transaction is declined?
- Do you support closed-loop payouts across several funding methods?
- How are chargebacks and fraud alerts reported, and how fast?
- Which KYC and AML checks do you run, and which do you expect from me?
- In what format and how often do I get settlement reports?
Sources: Visa Merchant Data Standards Manual (April 2026); UK Gambling Commission (April 2025); GamCare (2020); Australian Government (2024); Law Society Gazette (4 February 2026); Agência Gov (25 September 2026); EU Directive 2015/849, Article 11 (2015); Adyen docs (2026).
Frequently asked questions
A cashier built for each market
IGP’s casino platform includes a cashier with local payment methods, routing and retries per market, on one wallet with 18,000+ games.
See the casino platform →
