iGaming PSP integration: how to connect payments to an online casino

Short answer: iGaming PSP integration is a compliance project first and an API project second. Before writing code, a licensed operator needs an acquiring bank or payment service provider that accepts gambling (card transactions coded as MCC 7995), a cashier that handles deposits and withdrawals, local payment methods for each market, and a reconciliation process that ties every payment to a player account. The typical sequence is: licence and risk appetite check, provider shortlist, onboarding (KYB), cashier and API integration, payout set-up, testing, and a controlled go-live.

This guide explains each step for operators of online casinos and sportsbooks, and for the teams that integrate payments for them. It covers only licensed gambling in markets where it is lawful.

Who does what in a casino payment stack

Many integration problems come from mixing up roles. In a typical set-up:

• Operator (merchant): holds the gambling licence, owns the player relationship, decides who may deposit and withdraw.
• Acquiring bank: the regulated institution that contracts with the card schemes and settles card payments to the operator. Not every acquirer accepts gambling. The acquiring banks section lists institutions by profile.
• PSP or payment gateway: connects the operator to one or more acquirers and alternative methods through a single API. Many PSPs are themselves licensed payment or e-money institutions.
• Cashier or orchestration layer: the deposit and withdrawal interface inside the casino, which routes each transaction to the right provider and retries on decline. See cashier platforms and payment orchestration.
• Local method providers: wallets, bank transfer and open-banking providers, mobile money and vouchers that players in each country actually use.

Step 1. Start with the licence and the acquirer's risk appetite

Card schemes treat gambling as a high-risk category. Gambling transactions must be identified with merchant category code 7995 (betting, including lottery tickets, casino gaming chips and off-track betting), and both Visa and Mastercard run registration and monitoring programmes for high-risk merchants. In practice the acquirer will ask for:

• the gambling licence and the list of countries where you accept players;
• a list of countries you block, and how you block them (geolocation, KYC address, BIN country);
• your responsible-gambling and AML policies;
• historical processing statements and chargeback ratios, if you have them;
• ownership structure and ultimate beneficial owners.

A frequent reason for rejection is a mismatch between the licence and the target markets. An acquirer cannot process for players in a country where the operator is not allowed to offer gambling, regardless of the operator's licence elsewhere.

Step 2. Shortlist providers by market, not by brand

The "best" iGaming PSP depends on where your players are. Build the shortlist market by market:

• Cards: which acquirers accept MCC 7995 for your licence and player countries, and what approval rates issuers in those countries show for gambling.
• Local methods: bank transfers, open banking, wallets and mobile money. In many markets these convert better than cards and carry no chargeback risk. Browse local payment method providers.
• Payouts: how winnings reach players, including push-to-card, bank transfer and wallet payouts. See payout providers.
• Settlement: currencies, settlement frequency, rolling reserve and minimum volumes.

Ask each provider for a written list of supported countries for gambling specifically. A general coverage map is not enough.

Step 3. Onboarding (KYB) and the risk file

Expect a longer onboarding than for ordinary e-commerce. Prepare corporate documents, licence certificates, website and cashier screenshots, terms and conditions, responsible-gambling tools and sample marketing. Providers may also run test transactions and a website review. Our article on betting merchant onboarding covers how account ownership and withdrawal funding are assessed.

Negotiate the commercial terms at this stage: processing rates, fixed fees, refund and chargeback fees, rolling reserve percentage and release period, and settlement timing. A rolling reserve can tie up a meaningful share of turnover; model its cash-flow effect before signing (see rolling reserves).

Step 4. Choose the integration pattern

There are three common patterns:

1. 1.Hosted payment page (HPP): the player is redirected to the provider's page. Fastest to launch and keeps card data out of your systems, but offers less control over the user experience.
2. 2.Embedded fields or SDK: the provider's fields sit inside your cashier. Better UX with limited PCI DSS scope.
3. 3.Host-to-host (H2H) API: your server talks directly to the provider. Maximum control, but if you handle raw card data you take on full PCI DSS obligations. Explore H2H processing providers.

Most operators with several markets put a cashier or orchestration platform in front of multiple PSPs. This lets you route by country, method and amount, and fail over when a provider is down (see safe routing and failover).

Step 5. Build deposits correctly

Key technical requirements for deposits:

• Idempotency: every deposit request carries a unique key so a retry never creates a double charge.
• Webhooks as the source of truth: credit the player balance only after a confirmed status from the provider, not on browser redirect.
• 3-D Secure: apply strong customer authentication where required (for example under PSD2 in the EEA and UK) and use it to shift fraud liability.
• Name and account matching: where possible, check that the payer's name matches the player profile to reduce third-party funding.
• Limits and responsible gambling: enforce deposit limits and self-exclusion before the request reaches the provider.

Step 6. Payouts: where most complaints start

Withdrawals are where players judge an operator. Design them as carefully as deposits:

• Closed loop where possible: many operators return funds to the method used for deposit, which reduces fraud and money-laundering risk.
• Push-to-card: card schemes offer push payment services (such as Visa Direct and Mastercard Send) that some acquirers support for gaming payouts where rules and local law allow.
• Bank and wallet payouts: needed for players who deposited with methods that cannot receive funds.
• Liquidity: make sure each payout channel is funded in time; deposits and withdrawals rarely happen through the same rails at the same hour.
• Status tracking: players and support must see whether a withdrawal is pending review, sent or completed.

Step 7. Test, then go live in stages

Testing in a sandbox is necessary but not sufficient. Your test matrix should include declines, timeouts, duplicate webhooks, partial refunds, chargebacks, payout returns and a provider outage (see the payment integration test matrix). Go live with one market and a volume cap, review approval rates and reconciliation daily, and only then open further markets.

Launch checklist

• Licence covers every country in the cashier; all other countries are blocked.
• Each card provider confirmed MCC 7995 acceptance for your licence and markets in writing.
• At least two providers per key market, routed by the cashier.
• Webhooks verified by signature, processed idempotently, reconciled daily.
• Payout channels funded and tested end to end.
• AML monitoring, anti-fraud tools and responsible-gambling limits active before the first live deposit.
• Support has a runbook for pending deposits, failed withdrawals and chargebacks.

FAQ

What is an iGaming acquiring bank?

It is an acquiring bank that is willing to process card payments for licensed gambling merchants under MCC 7995 and is registered with the card schemes for high-risk processing. Many operators reach such banks through a PSP rather than directly.

How long does iGaming PSP integration take?

Onboarding and risk review often take longer than the technical work. A hosted page can be integrated in days; a full cashier with several providers and payouts usually takes weeks. Timelines depend on the provider's review and on how complete your documents are.

Can an unlicensed casino get a PSP?

Legitimate acquirers and PSPs require a valid gambling licence for the markets served. Offers to process without a licence or with a disguised merchant category are a serious red flag; see our article on payment processing without a licence.

Do I need a payment orchestration platform?

Not on day one, but once you work with several PSPs across markets, an orchestration or cashier layer simplifies routing, retries and reporting.

Where can I compare iGaming payment providers?

The Nominal hub catalog lists PSPs, acquirers and cashier platforms with their methods and regions, and the gambling merchants section shows operators' requests. Nominal hub is a directory, not an intermediary: contract directly with providers after your own due diligence.