iGaming Payment Solutions & Providers: 2026 Guide

If you are evaluating iGaming payment solutions, the first job is not building a vendor shortlist. It is working out which of three separate things you are buying. Licensed operators lose more money to this confusion than to any single pricing decision: a hosted cashier and a pure gateway end up on the same spreadsheet, get compared on headline rate, and the winner turns out to solve a problem the operator did not have.

A payment stack does three jobs. Processing moves the money. Aggregation — usually sold as orchestration — decides which processor handles which transaction. The cashier is the screen the player actually sees. Different vendors bundle these differently, and the bundling is where the commercial trade-offs hide. This guide separates the three, sets out what to ask providers at each layer, and covers where operators most often get it wrong.

The three layers of an iGaming payment stack

Layer	What it does	Who sells it	What you’re really buying
Cashier	The player-facing deposit screen: method ordering, retries, in-flow KYC	Fluid, PaymentIQ, Praxis, Finteqhub	Deposit completion rate
Aggregation / orchestration	Routes each transaction, cascades on decline, fails over between providers	IXOPAY, Spreedly, BR-DGE, Primer, and the bundled cashier platforms	Approval rate and provider independence
Processing	Authorises and settles: acquiring, scheme rails, local methods	Trustly, Brite, Zimpler, Skrill, Neteller, Nuvei, Worldpay, CoinsPaid	Cost per transaction and settlement terms

Read that table bottom-up and it describes how money moves. Read it top-down and it describes where deposits get lost. Most operators discover their problem is in the top row while their vendor conversations are all about the bottom one.

Payment processing: who moves the money

Processing is the layer everyone quotes on, and it is the one where the quoted number tells you least.

iGaming sits in a high-risk merchant category. Acquiring banks underwrite it differently, issuers apply tighter risk rules to the gambling merchant category code, and the whole cost base reflects that. Expect a blended rate of roughly 2.5-4.5% on cards, plus a per-transaction fee, plus 1-2.5% FX margin on anything you do not settle in, plus 15-50 per chargeback. Bank rails are materially cheaper — Pay by Bank providers land around 1.5% — and crypto providers cheaper again at roughly 0.5-1%. E-wallets sit between at 1.9-2.9%.

None of that is the number that decides the deal. Two things matter more:

Approval rate beats price, usually by an order of magnitude. In stable European markets with 3DS2 and network tokens in place, 82-90% on cards is realistic. A provider delivering 78% where another delivers 86% costs you the difference on 8% of your volume — which dwarfs any basis-point saving on the processing fee. Below 75% is not a market condition, it is a fixable configuration problem.

Local acquiring is the cheapest approval-rate fix available. Cross-border card routes typically run 5-10 percentage points below locally-acquired ones. The effect is most extreme in Latin America, where international card declines can reach 40-60% — which is why Brazilian Pix, Mexican OXXO and Colombian PSE stop being optional the moment those markets are in scope. Ask which countries a provider has local acquiring in, not which countries it “covers”. Our guide to local payment methods in Latin America maps the rails market by market.

Then there is the line that is not a fee. A rolling reserve of 5-10% of volume held for 90-180 days is standard for gambling merchants. It never appears on a rate card and it is working capital you do not control. Chargebacks compound it: iGaming runs 2-3% against 0.5-1% for general e-commerce, and every dispute carries a fee on top of the reversed amount.

For a provider-by-provider view of this layer, the 13 gateways and PSPs we see most often in operator stacks covers regional fit and coverage for each, and the 2026 operator’s guide to payment gateways goes deeper on auth rates and contract mechanics.

Payment aggregation: who decides where it goes

Aggregation — orchestration in most vendors’ language — is the routing brain. It picks which provider gets a transaction, retries intelligently when one declines, and fails over when one goes down.

The revenue case is straightforward. Routing across more than one provider typically recovers 10-15% of failed transactions and lifts approval rates by 2-4 points, because a decline at one provider is frequently an approval at another. The risk case is stronger still: single-provider dependence is the largest structural weakness in an iGaming payment stack. When your one processor has an outage, tightens its risk appetite, or revises terms mid-contract, deposits stop. Two providers is the floor; three across multiple geographies is where most mature operators land, even when the spare carries little day-to-day traffic.

Orchestration comes in two shapes:

Pure orchestrators — IXOPAY, Spreedly, BR-DGE, Primer — route between providers you bring yourself. Strong on independence and decline recovery, but they ship no player-facing cashier. You either build one, roughly six months of engineering, or pair the orchestrator with a hosted cashier and hand back much of the benefit. Routing rules become an in-house specialty; operators without payments headcount tend to leave the defaults on and never see the value they bought.

Bundled cashier-plus-orchestration platforms — PaymentIQ, Praxis, Finteqhub — give you one contract and one SLA. Faster to launch, and the routing is configured for you. The cost is that the cashier price is not separable from the processing arrangement, so you cannot shop one without the other, and every routing or method improvement is gated by the vendor’s release schedule. Comparing the bundled platforms is a different exercise from comparing pure orchestrators, and mixing the two on one shortlist is how evaluations go wrong.

The cashier: what the player actually sees

The cashier is the layer that decides how many players reach the authorisation attempt at all. It cannot improve an approval rate the provider did not deliver — but the largest single loss in most deposit funnels sits above the authorisation, not at it.

Three things separate a cashier that converts from one that does not:

Whether it looks like your brand. Hosted cashiers render in an iframe or redirect on a third-party domain. At the exact moment a player commits money, the brand they trusted disappears and someone else’s form appears. In the eye-tracking work we have run, that visual seam is worth 4-8% of deposit conversion. A cashier that renders inside your own frontend has no seam.

Whether it knows the player. Method ordering is the single highest-leverage decision in the deposit screen, and it should not be static. Which method to surface first, what amount to suggest, when to retry silently on a soft decline — these are per-player decisions, and a cashier that sees the player’s whole deposit history makes them better than one seeing a single provider’s slice. That is the basis of AI-driven payment personalisation.

Whether KYC happens in-flow. Verification that redirects the player into a separate journey is a couple of years behind the regulated-market standard. Global KYC requirements are not optional, but where they happen in the funnel is a design choice with a measurable conversion cost.

The commercial stakes are high because the traffic is expensive. Player acquisition in licensed iGaming routinely exceeds €900 per player, and roughly a third of bettors abandon a deposit over slow funding while around a quarter leave when their preferred method is missing. A weak cashier wastes the marketing spend that brought the player to the deposit screen in the first place. Across our partner base, operators see +5% deposit conversion, +25% deposit value and +19% deposit frequency once a brand-native cashier sits on top of their existing provider relationships — the PowerPlay case study sets out how that played out for one operator.

If you are weighing a cashier swap specifically, PaymentIQ alternatives compares the four platforms operators most often shortlist, and cashier vs payment gateway draws the line between this layer and the one below it.

How to choose providers at each layer

The evaluation questions are different per layer. Run them separately.

For processing providers: Which countries do you have local acquiring in? What approval rate do comparable operators in my markets see? What are the reserve terms, and for how long? What is the FX margin on my settlement currency? What is the chargeback fee, and who eats the dispute?

For the aggregation layer: How many providers can I route across, and can I add one without your engineering? What is the median time to add a new provider — with dated examples? What happens to routing when a provider is degraded rather than fully down? Do I own the routing rules, or do you?

For the cashier: Does it render inside my DOM or in an iframe? Who owns the player session? Is KYC in-flow? What does the conversion dashboard look like on day 30? Can I change method ordering without a release?

Two questions apply everywhere. Are you actually licensed for my geographies — ask for the regulator reference and check the public registry, then ask whether they have onboarded a licensed operator in your jurisdiction in the last twelve months. And what does the exit look like — twelve months with 60 days’ notice is reasonable; multi-year lock-in on any of the three layers is a red flag. The provider evaluation checklist turns this into a scoreable format.

Where operators get this wrong

Buying a bundle to solve a single-layer problem. The most common pattern we see: deposit conversion is poor, the operator re-tenders the whole payment stack, and replaces three layers to fix one. If approval rates are healthy and completions are not, the problem is the cashier and the providers underneath are fine.

Comparing headline rates across layers. A cashier priced as a percentage of value moved and a gateway priced on interchange-plus are not comparable numbers, and putting them in one column produces a decision that looks rigorous and is not.

Treating regional coverage as a checkbox. “EU + global” on a coverage table means nothing you can plan against. What matters is which specific methods are first-class integrations versus available “via partners”, and which countries have local acquiring behind them. Regional payment habits differ enough that a stack tuned for one market underperforms badly in the next.

Not instrumenting before switching. If you cannot see approval rate by method and geography, decline reason codes, chargeback ratio, deposit completion rate and time-to-settlement today, you will not be able to prove whether the new vendor helped. Fix the measurement first — the eight payment KPIs every operator tracks is the shortest route to a baseline, and Fluid Control gives the same view in real time.

Where Fluid fits

Fluid is the cashier layer, and only the cashier layer. It renders inside the operator’s own frontend rather than in a hosted iframe, personalises method ordering and retry behaviour per player, runs KYC in-flow, and works on top of whichever orchestration and providers an operator already runs — including PaymentIQ’s, Praxis’s or Finteqhub’s. That is a deliberate scope: replacing the cashier is typically days of work and the lift shows up in the first 60 days, where replacing a whole stack is a multi-quarter project with the conversion problem still unsolved at the end of it.

If your approval rates look fine and your deposit completions do not, that is the layer to look at. Our casino cashier and payment solutions pages set out what that involves in practice.

FAQs

What are iGaming payment solutions?

“iGaming payment solutions” is the umbrella term for everything that moves a player’s deposit from intent to settled funds. It covers three distinct jobs. Payment processing is the provider relationship that authorises and settles the transaction. Aggregation, or orchestration, is the routing layer that decides which provider handles which transaction and what happens when one declines. The cashier is the player-facing screen that surfaces methods, runs in-flow KYC, and turns an intent to deposit into a completed one. Vendors bundle these three differently, which is the main reason operator shortlists end up comparing products that are not actually competing.

What is the difference between an iGaming payment provider and a payment gateway?

In practice the terms are used interchangeably, but they describe different scopes. A payment gateway is the technical component that authorises a transaction and returns an approve or decline response. A payment provider is the commercial relationship you sign — which may include the gateway, the acquiring, the settlement account, and the risk terms. When comparing vendors, ask which of those you are actually buying. Two quotes that look similar on the headline rate can differ enormously once acquiring, FX margin, chargeback fees and the rolling reserve are on the table.

How many payment providers should a licensed iGaming operator run?

Two minimum, three or more once you are live across multiple geographies. Single-provider dependence is the largest structural risk in an iGaming payment stack: when your one processor has an outage, changes its risk appetite, or revises terms, deposits stop. Running more than one provider also recovers revenue on ordinary days — routing across multiple providers typically recovers 10-15% of failed transactions and lifts approval rates by 2-4 percentage points, because a decline at one provider is often an approval at another.

What does iGaming payment processing cost?

For card processing under the gambling merchant category, expect a blended rate of roughly 2.5-4.5%, plus a per-transaction fee, plus FX margin of 1-2.5% on non-settlement currencies, plus 15-50 per chargeback. Bank rails are cheaper — Pay by Bank providers run around 1.5% — and crypto providers cheaper still at roughly 0.5-1%. E-wallets sit at 1.9-2.9%. The line that hurts most is not a fee at all: a rolling reserve of 5-10% of volume held for 90-180 days is standard for gambling merchants, and it is working capital you do not control.

What approval rate should a licensed operator expect?

In stable European markets with 3DS2 and network tokens configured, 82-90% on cards is a realistic band. Anything below 75% points at a fixable problem rather than a market condition — usually a missing tokenisation programme, an always-on 3DS challenge flow, or an acquirer whose issuer relationships are weak in your geography. Pay by Bank rails typically clear 90%+ because there is no issuer in the loop to decline. Ask every provider for approval benchmarks on comparable operators in your markets, and treat a refusal to share them as an answer.

Do I need payment orchestration, or is a cashier enough?

They solve different problems and most operators eventually need both. Orchestration decides which provider a transaction goes to and how a decline is retried — it protects revenue on the provider side. A cashier decides how many players reach the authorisation attempt at all — it protects revenue on the player side. An orchestrator with no cashier means building the deposit UI yourself, roughly six months of engineering. A cashier with no orchestration means single-provider dependence. The common mature setup is one cashier, one orchestration layer, and several providers underneath.

How long does it take to integrate an iGaming payment solution?

It depends on which layer and which integration model. A hosted iframe or redirect cashier is fastest to launch — days — and costs the most in conversion afterwards. A component or SDK-based cashier that renders inside your own frontend takes 2-4 weeks for the first market and less for later markets sharing the same providers. A full REST API integration you build against yourself is 8-12 weeks of your own engineering. Adding a further provider to an existing orchestration layer is usually configuration rather than a project — ask any vendor for dated examples of how long their last three provider additions actually took.