iGaming payment gateway: how operators choose one (and why one is rarely enough)

iGaming payment setups compared

What is an iGaming payment gateway?

In iGaming, the gateway is the link between the operator's cashier and the networks that move money: card schemes, bank transfer and open banking rails, e-wallets and local methods. It collects the payment request, passes it to the acquirer or method operator, returns the result and later handles refunds and payouts.

The difference from an ordinary e-commerce gateway is risk appetite. Gambling payments are coded as gambling (card schemes use a dedicated merchant category code, 7995), they attract more chargebacks and bonus abuse, and they are only legal where the operator holds a valid licence. Many gateways therefore exclude gambling entirely or accept it only for specific licences and countries.

iGaming payment provider, gateway, platform or system: what do the terms mean?

Vendors use these words loosely, and the same company can be several of them. What matters for an operator is who holds the licence, who holds the funds and who you sign the contract with. The table shows how the terms are usually meant.

What should you check before signing with a gateway?

Ask for written answers on each point below, for your licence and each target country. A general claim of iGaming support says little about whether your traffic will be approved.

• Licence and country acceptance: which regulators' licences the provider and its acquirers accept, and which player countries are excluded
• Deposit methods per market: cards, open banking, e-wallets and local methods such as iDEAL, BLIK, Przelewy24, Bizum or Pix where your players use them
• Withdrawals: which methods can pay out, how fast, and whether payouts go back to the method used for the deposit
• Approval rates and decline data: per country and method, with raw decline codes available to your team
• Fees, reserves and settlement: transaction fees, rolling reserve, settlement currency and frequency, and how a reserve is released
• Risk and compliance hand-offs: how KYC, age and source-of-funds checks connect to payments, and which party runs AML monitoring
• Chargeback handling: dispute notifications, deadlines and the chargeback ratio that triggers a review
• Integration: API quality, webhooks, sandbox, and whether a hosted cashier page is available

How do local deposit methods affect gateway choice?

Players deposit with what they already trust. In the Netherlands that is usually iDEAL, in Poland BLIK and Przelewy24, in Spain Bizum and cards, in Brazil Pix. A gateway that is strong on cards in one region may not offer the local method that dominates another, or may not accept gambling traffic for it.

Regulators also shape the mix. The UK Gambling Commission banned gambling on credit cards from 14 April 2020, so UK-licensed operators take debit cards but not credit cards. Check each market's rules before switching a method on, rather than copying one cashier configuration across countries.

Why do iGaming operators use more than one gateway?

One gateway is a single point of failure. A provider can change its risk appetite, cap volumes or close a gambling account with little notice, and deposits stop until a replacement is integrated. Several gateways also widen market and method coverage and let you send each payment to the provider most likely to approve it.

• Resilience: traffic can move to another contracted provider that has approved your business
• Coverage: different providers are strong in different countries and methods
• Approval rates: a declined payment can be retried on another provider when the decline reason allows it
• Negotiating position: volume can be shifted between providers

Gateway, payment orchestration or in-house integrations?

There are three common setups. A single gateway is fastest to launch but leaves the cashier exposed. Building several gateway integrations in-house gives control but costs engineering time for every new provider, each API change and each reporting format. A payment orchestration platform sits between the cashier and the gateways: the operator integrates once, connects its own provider accounts and applies routing rules across them.

Orchestration does not replace provider underwriting. Each gateway still decides whether to accept your licence and traffic, and holds and settles the funds under its own licence.

What does an iGaming payment integration involve?

Whether you integrate one PSP or several, the technical work is similar. The cashier creates a deposit session, the player completes it on a hosted page or through an API flow, and your back office credits the balance only after a confirmed result. Withdrawals run the other way and usually depend on the player's verification status.

Integration services offered by providers or orchestration platforms mostly cover these pieces. Ask which of them are included and which your team still has to build. The player-facing side is shown in our iGaming cashier preview, and the operator overview is on iGaming payment solutions.

• Deposit sessions with idempotency keys, so a double click or retry never credits a player twice
• Signed webhooks as the source of truth for deposit and payout status, not the browser return
• A payout flow gated by KYC and your withdrawal rules, with the method each provider allows
• Decline codes and routing data per provider, for approval-rate reviews
• Settlement and reconciliation reports that match provider fees and reserves to player transactions
• Chargeback and dispute notifications routed to the team that handles them

How do you launch a gateway setup for a new market?

Work from players back to providers.

1. Map player methods List the top deposit and withdrawal methods players use in the market and the regulator's restrictions.
2. Shortlist providers Keep gateways that accept your licence for that country and offer those methods.
3. Get terms in writing Collect written answers on fees, reserves, settlement, payouts and chargeback thresholds.
4. Pilot real scenarios Test deposits, withdrawals, declines and refunds with real cases before launch.
5. Add a second provider Connect a backup provider for the main methods before scaling marketing spend.
6. Route and review Set routing and retry rules, then review approval rates per method every week.

How does OrsunPay fit iGaming operators?

OrsunPay is a payment orchestration platform that connects you to licensed PSPs; it does not process or hold funds itself. Licensed operators connect their own accounts with providers that accept their licence and markets through one API and hosted checkout. Smart routing and retries work across the connected providers, local methods such as BLIK, Przelewy24, Bizum, iDEAL and Pay by Bank can be offered through providers that support them, and every deposit status appears in one view. The RiskCogs anti-fraud module adds risk scoring before authorisation. Talk to us about your licences, markets and current providers.