How to Choose an iGaming Payment Gateway in 2026

“Payment gateway” gets used loosely. Someone shopping for an iGaming payment gateway in 2026 might mean three different things: a PSP to handle card processing, a hosted cashier with payment processing bundled, or a full payment orchestration layer. They have different price points, different lock-in implications, and different integration timelines.

This guide is for operators who want to make an informed pick — whether you’re greenfield, replacing a legacy PaymentIQ-style hosted product, or adding a second gateway to a single-PSP setup that’s now too risky.

Step 1 — get clear on what you’re shopping for

If you’re early in the buying process, the first thing to settle is which layer of the stack you’re picking from:

• A processor (PSP gateway). This is the actual payment-processing service: card authorisation, alternative-payment-method (APM) settlement, KYC checks at processor level, chargeback handling. Examples: Adyen, Worldpay, Nuvei, Praxis, Worldline.
• An orchestrator. Sits above one or more PSPs, routes transactions, handles retries. Examples: IXOPAY, Spreedly, BR-DGE, Primer.
• A cashier. What the player sees: deposit form, payment-method picker, validation, confirmation. Can be hosted (PSP-supplied) or operator-controlled.

The word “gateway” in iGaming most often refers to the processor, occasionally to a bundled cashier+processor product. Knowing which sense the conversation is using saves you from comparing apples to electric kettles.

Step 2 — list your hard requirements

These are the criteria that disqualify a gateway outright if they’re not met. Get them on paper before you start vendor calls.

License and jurisdiction coverage

Every gateway has a list of licensed-operator jurisdictions it’ll serve. Some PSPs won’t process for MGA-licensed operators, others won’t touch the UK without UKGC paperwork on file, others quietly avoid Sweden post-2024 advertising restrictions. Always ask for the explicit list before going further. A “yes, we can serve you” without the list is meaningless.

Payment method coverage

Three buckets:

• Card — Visa, Mastercard, sometimes Amex. Every PSP handles cards. Differentiation is in approval rates, 3DS handling, and merchant-category-code (MCC) routing.
• Alternative payment methods (APMs). This is where geographies diverge fast. UK = Pay-by-bank (Trustly, TrueLayer, Volt), Apple/Google Pay. Sweden = Trustly, Swish. Germany = giropay (now retired, replaced by EPI/Wero), Klarna. LatAm = Pix in Brazil, OXXO in Mexico, PSE in Colombia. North America = ACH, Interac. Make sure your buyer-target geographies are first-class supported.
• Crypto — selectively relevant. Ask about USDC/USDT support, wallet integrations (MetaMask, Phantom, Trust), and fiat off-ramp.

Approval rate / acceptance rate

The single most important commercial KPI on a payment gateway is its approval rate on your transaction profile. Card-not-present in iGaming has a higher decline rate than e-commerce — issuers see the MCC and apply tighter risk rules. A gateway that delivers 78% approval where another delivers 86% is going to cost you the difference in 8% of transaction volume. Always ask for benchmarks on comparable iGaming operators in your geography.

Settlement timing

Vendor terms vary from T+1 to T+5. For iGaming operators with significant withdrawal volumes, slow settlement is a working-capital problem. Match the settlement profile to your withdrawal patterns.

Fraud and chargeback tooling

iGaming has higher chargeback exposure than retail e-commerce. Look for: rules-based blocking, behavioural analytics, device fingerprinting, 3DS enforcement, and an integration story for third-party fraud tools (Sift, Forter, Riskified, Featurespace).

Step 3 — evaluate the integration model

This is where weeks of project time get won or lost. Three common models:

Hosted iframe / redirect

The PSP supplies a cashier UI that you embed via iframe or redirect the player to. Fastest integration (often days), worst player UX (visible vendor seam, brand discontinuity, mobile keyboard issues). Good for early-stage launches and pilots; bad for scale operators.

REST API

The PSP exposes endpoints you call. You build the cashier yourself. Maximum flexibility, maximum engineering work. Typical integration: 8-12 weeks for a competent in-house team. Suitable for operators with a payments engineering team; misery for operators without.

Web component / SDK

A middle ground. The PSP (or a separate cashier vendor) ships a JavaScript component you drop into your operator UI. It renders inside your DOM, picks up your design system’s CSS variables, and exposes events you can hook into. 2-4 weeks integration for the first market, faster after.

This middle ground is where Fluid sits, by the way — we ship a web-component cashier that talks to whichever PSP gateway you’ve chosen.

Step 4 — compare commercials beyond the rate card

Public rate cards are negotiable for everyone except small operators. Real-world commercials depend on:

• Volume tiers. Most PSPs have 3-4 tier breakpoints. Get all of them, not just the one you’d land in today.
• Interchange-plus vs blended pricing. Interchange-plus is more transparent and usually cheaper at scale; blended is simpler. Larger operators always end up on interchange-plus.
• Chargeback fees. $15-50 per chargeback is normal; some PSPs charge $100+. Multiply by your chargeback rate to compare.
• Reserve requirements. New operators or higher-risk MCCs may face reserves of 5-15% of monthly volume held for 6-9 months. This is a working-capital line item, not a fee.
• Currency conversion fees. Material in multi-currency operators. 1.0-2.5% spread on FX is normal; below 1% is a strong sign of a flexible PSP.
• Implementation fees. Should be zero or refundable on launch. Anything above $10K up-front is a vendor positioning itself for hard renegotiation later.
• Termination clauses. A 60-day notice on a 12-month contract is standard. Anything longer is a leverage play.

Step 5 — talk to two reference customers, not their suggested ones

Every PSP has marquee logos they’ll point you at. Those references will tell you the polished version. Two ways to get the unvarnished view:

1. Ask the PSP for two references in your geography and at your volume tier that are not in their case-study collateral.
2. Find operators on LinkedIn who’ve publicly mentioned the vendor and reach out cold.

Reference questions worth asking, in order:

• “What was the worst week with this vendor in the past year?”
• “How long does a feature request take from ask to ship?”
• “Have you considered switching, and if so why didn’t you?”
• “What did you under-estimate during the integration?”

If three references give the same answer to question 4, that’s your real buying-decision input.

Step 6 — pilot, don’t bet

If your traffic allows, pilot the new gateway on a sub-segment first: one geography, one game vertical, or 10-20% of traffic via a feature flag. Two outcomes:

• The gateway under-performs the existing one: you exit cleanly. Few PSPs will block this if you can prove the data.
• The gateway out-performs the existing one: you’ve already de-risked the migration plan and have a real internal benchmark to negotiate with.

Operators who skip the pilot tend to discover at month 4 that the new gateway has a 3% lower approval rate than promised, and now they’re stuck.

What we’d push back on

Several “best practices” that show up in iGaming gateway content are wrong or oversimplified:

• “Pick the cheapest rate.” Approval-rate delta dwarfs basis-point savings on processing fees. A gateway that’s 10 bps cheaper but 2% lower on approvals is a worse deal at scale.
• “Use only one gateway.” Single-gateway dependence is the biggest single risk in iGaming payments. Have a second one even if you don’t route material traffic through it day-to-day.
• “Hosted cashiers are simpler so they’re better.” Simpler to integrate, harder to scale. Most operators who started on a hosted cashier and grew past €100K monthly volume end up replacing it within 3 years.

Where this fits with the broader stack

A payment gateway is one piece. Above it sits orchestration (which gateway to use for this transaction), and above that sits the cashier UX (what the player actually interacts with). Read iGaming Cashier vs Payment Gateway for the explainer on the full stack, or our iGaming Payment Solutions Comparison for the buyer’s guide on the cashier layer.

If your operator team is mid-evaluation and wants a second pair of eyes — we’re operators ourselves, not salespeople. Talk to us.