How to Compare iGaming Payment Providers: 8-Question Framework

Choosing an iGaming payment provider isn’t a checklist exercise — it’s a stack decision with real conversion consequences. The 8 questions below are the framework we walk operators through when they ask us to weigh in on a stack: which questions matter, which are red flags, and how to score the answers. Use it to filter your shortlist; for the actual provider-by-provider comparison, see our Best iGaming Payment Gateways for 2026 buyer’s guide.

Two notes before we start:

• Cashier and PSP are different layers. A cashier (Fluid, PaymentIQ, Praxis, Finteqhub) is the player-facing UX. A PSP (Trustly, Skrill, Nuvei, Worldpay, etc.) is the money-movement underneath. Operators typically run one cashier and several PSPs. Run this framework on each layer separately — the questions matter at both, but the answers are different.
• The right answer depends on your stack. This isn’t a yes/no scorecard — it’s a way to surface trade-offs. Score each provider 1–5 against your actual context (verticals, geographies, license, current cashier), and the highest-scoring provider wins your shortlist slot.

1. Are they actually iGaming-licensed?

The single biggest filter. Many “fintech” providers will cheerfully list iGaming on their website then get cold feet when their underwriting team sees a gambling MCC application.

What to verify:

• Regulator status in your geos. MGA, UKGC, AGCO Ontario, BMM, regional EEA, US state-by-state, etc. Ask for the regulator’s reference number, then check it on the regulator’s public registry — don’t take a screenshot at face value.
• Actual gambling-MCC underwriting. Ask: “Have you onboarded a licensed sportsbook / casino / sweepstakes operator in [your geo] in the last 12 months?” If they hesitate, you have your answer.
• References in your jurisdiction. Ask for two operator references in the geo you’re licensing in. The conversation you have with those operators tells you more than any sales deck.

Red flags: vague answers about regulator licensing, references only in adjacent verticals, an underwriting timeline that keeps slipping.

2. What’s their merchant-category posture?

Even iGaming-licensed providers vary widely on how they handle the high-risk merchant category that gambling carries. This matters because it determines settlement times, hold-back percentages, and chargeback handling — three things that hit your cash flow directly.

What to ask:

• Reserve and hold-back terms. Some providers hold 5-10% of monthly volume for chargeback risk; some hold none. The math gets material at scale.
• KYC and source-of-funds workflow. Will they push KYC into your deposit funnel, or block transactions until KYC is complete out-of-band? In-flow KYC is the modern standard; out-of-band KYC tanks deposit conversion.
• AML monitoring depth. Real-time transaction monitoring vs end-of-day batch reports. Operators in regulated jurisdictions need real-time.

Red flags: indefinite hold-back terms, manual KYC processes, lack of clarity on AML reporting.

3. Cashier or PSP — and which do you actually need?

Operators often start a payment-provider evaluation without a clear answer to this. The two layers solve different problems and need different vendor relationships.

Pick the right layer for your bottleneck:

• Cashier swap if your players are abandoning at the deposit screen. The cashier UX is the conversion layer — brand-fit, retry logic, in-flow KYC, AI-tuned method ordering. A cashier change can be done in days while keeping the rest of the stack untouched. See our PaymentIQ vs Fluid comparison for an example of how this plays out.
• PSP addition or swap if specific payment methods or regions aren’t performing. Adding a Pay-by-Bank PSP for a Nordic launch, or swapping to a higher-converting card acquirer, is a different project than touching the cashier — and is usually solved without a cashier change.
• Both if you’re greenfielding a new operator. In that case the order is: license → orchestration → PSPs → cashier on top. Most operators we work with land on Fluid for the cashier layer because it’s gateway-agnostic and connects to whatever orchestration the operator picks.

Red flag: a single vendor pitching themselves as the answer to both layers without acknowledging the trade-offs of bundling.

4. What’s the regional fit?

Regional fit is the single biggest determinant of deposit-conversion rate. A globally-strong PSP that’s mediocre in your specific markets is worse for you than a regional specialist that nails the geos you actually serve.

What to evaluate:

• Local acquiring routes for card processing. Cross-border card processing carries 5-10 percentage points lower auth rate than local-acquired routes. Ask the provider explicitly which countries they have local-acquiring in for your card volume.
• Regional payment methods. Brazilian PIX, Mexican OXXO, Colombian PSE, Indian UPI, Argentine Mercado Pago — if these matter for your geos, the provider needs them as first-class methods, not “via partner integrations”.
• Currency support. Multi-currency handling, FX margin, settlement currency. Operators serving multi-region player bases lose meaningful margin on FX if the provider is sloppy here.

5. Settlement times and cash flow

Settlement is the time between a player’s deposit and the operator’s bank balance going up. This number runs your working-capital math.

What to ask:

• Time-to-settlement per method. Trustly and most Pay-by-Bank rails settle instantly or T+0. E-wallets typically T+0 to T+1. Cards are usually T+1 to T+3 depending on acquirer. Crypto is near-instant on most chains.
• Settlement currency vs operator’s holding currency. If you’re settled in USD but operate in EUR, you eat FX every cycle. Get clarity on settlement currency and FX margin.
• Withdrawal speed. This is what your players actually feel. Slow withdrawals are the #1 complaint in iGaming player reviews. Withdrawals on Trustly, Brite, Zimpler are typically instant; e-wallets within hours; cards 1-5 days.

Red flag: a provider that’s vague about settlement times or refers everything to “depends on the bank”.

6. Fraud, chargebacks, and risk handling

Every iGaming provider claims to have advanced fraud tools. The question is whether they actually integrate with what you already run, and whether their economic model puts them on your side or against you.

What to evaluate:

• Fraud-detection integrations. Does it feed your existing risk stack (Featurespace, Sift, Cybersource, etc.) or insist on replacing it? Operators we work with strongly prefer providers that augment their existing risk tooling.
• Chargeback economics. Who eats the chargeback — provider, operator, or both? What’s the dispute-management workflow? How fast does the provider escalate vs auto-accept?
• 3DS handling. Smart 3DS routing (challenge only when fraud signals warrant) vs always-on 3DS. Always-on 3DS is conversion-killer.

Red flag: a provider that pushes their own risk tooling as a paid add-on you can’t decline.

7. Pricing model

Most iGaming providers will not publish list prices for licensed operators. That doesn’t mean the pricing is opaque — it means it’s negotiated, and the negotiation is the entire point.

What to evaluate:

• Pricing structure. Flat percentage, tiered by volume, fixed monthly + per-transaction, or fully custom. Different structures fit different operator types — fixed-percentage hurts low-margin operators; tiered rewards growth.
• The fees that aren’t on the front page. FX margin, chargeback fees, dispute handling fees, refund fees, monthly minimums, integration fees. These can double the headline rate if you’re not paying attention.
• Renegotiation timeline. Initial pricing is rarely the long-term deal. Most providers renegotiate annually based on actual volume. Lock in a renegotiation clause from day one.

Red flags: pricing significantly below market without explanation (usually means hidden gross-up), pricing that’s volume-tiered but with thresholds set absurdly high, or contracts longer than 24 months.

8. Integration time and ongoing support

The fastest provider in the comparison isn’t always the best fit. The slowest isn’t always worth the wait. What matters is the realistic integration timeline for your specific stack and how the support model holds up after go-live.

What to ask:

• Realistic integration timeline. “Days, not weeks” is sometimes true (a JavaScript-only cashier install) and sometimes marketing fiction (a backend orchestration migration with 12 PSPs). Ask for an integration plan signed off by their solutions team, not their salesperson.
• Sandbox quality. A good sandbox lets you test the full deposit/withdrawal lifecycle with realistic fail modes. A bad one is a happy-path-only demo. Test the sandbox during evaluation, not after contract.
• Support model after go-live. Dedicated success manager? Tier-1 support hours? Slack channel? Tickets-only? Most operators we work with strongly prefer providers that assign a named success manager from day one.
• Roadmap visibility. Will you see the product roadmap? Influence it? Or is it a black box?

Red flag: a provider that promises everything during evaluation, then disappears into a generic support queue after contract.

How Fluid scores against this framework

We built Fluid specifically because most cashier providers don’t honestly answer these eight questions. Where Fluid lands:

• iGaming-licensed: Yes. Fluid is built specifically for licensed iGaming operators across regulated jurisdictions; we don’t process anything else.
• Merchant-category posture: In-flow KYC, real-time AML monitoring, gateway-agnostic. Compliance posture stays where the operator already has it; Fluid slots in alongside.
• Cashier vs PSP: Cashier. Fluid replaces the cashier UX layer over your existing orchestration and PSP relationships — it doesn’t replace orchestration or PSPs.
• Regional fit: Global. Multi-currency, multi-language, multi-jurisdictional out of the box. PSP coverage is whatever the operator’s existing relationships provide; Fluid is gateway-agnostic.
• Settlement: Determined by your PSP layer, not by Fluid. The cashier layer doesn’t move money — your PSPs do.
• Fraud/risk: AI-driven anomaly detection layered on top of your existing risk stack. Doesn’t replace Featurespace/Sift/etc.; augments them.
• Pricing: Volume-tiered, tailored to monthly deposit volume and integration scope. No list price; talk to us for a quote against your stack.
• Integration: Two-line JavaScript install on the frontend; most operators are live in days. Fluid Control — the real-time payments dashboard — ships included.

For the actual provider-by-provider comparison covering 13 platforms (4 cashiers + 9 PSPs), see Best iGaming Payment Gateways for 2026: Buyer’s Guide.

What to do next

The framework above is the easy part. The hard part is being honest about your stack’s actual bottleneck and not getting talked into solving the wrong problem.

If your deposit conversion is leaking, the bottleneck is almost always the cashier UX layer — not the PSPs underneath. If your method coverage is the problem, it’s a PSP issue. If your operations team is flying blind on which methods are converting in real time, it’s a dashboard issue. Different problems, different vendors.

Three steps we recommend operators take before signing any provider contract:

1. Run the 8-question framework against the providers on your shortlist. Score each 1–5 honestly. The scorecard above gives you the template.
2. Get two references in your specific jurisdiction. Have a 30-minute call with each — focus on what’s gone wrong, not what’s gone right.
3. Test the sandbox end-to-end before signing. Deposit, withdrawal, decline, retry, KYC failure, chargeback. If the sandbox doesn’t support all six, you’re going to find out the hard way after go-live.

The right provider isn’t the one with the best sales deck. It’s the one whose answers to the 8 questions match what your stack actually needs. That’s a less exciting decision than picking the most-marketed name — but it’s the one that holds up 18 months later when you’re past the honeymoon.

FAQs

How long should iGaming payment provider evaluation take?

For a single new PSP relationship, 2-4 weeks of due diligence is typical: technical review, commercial proposal, reference calls, sandbox integration test, contract negotiation. For a cashier swap, allow 4-8 weeks because the impact on the operator stack is broader. Operators who rush this routinely end up with provider relationships they regret 6 months in. The 8-question framework above is designed to surface the issues you’d otherwise discover post-contract.

What’s the difference between a cashier and a PSP in iGaming?

A cashier is the player-facing UX layer — the screen a player sees when they click “deposit”, which surfaces payment methods, handles retries, runs in-flow KYC, and routes transactions to the orchestration layer. A PSP (payment service provider) is the back-end relationship that actually moves money — Trustly handles a Pay-by-Bank deposit, Skrill processes an e-wallet transaction, etc. Operators typically run one cashier and connect it to several PSPs through an orchestration layer. Fluid is a cashier; PaymentIQ, Praxis, and Finteqhub bundle cashier and orchestration; the rest of the major iGaming payment providers are PSPs. See the buyer’s guide for a side-by-side of all 13.

Why does this framework recommend cross-checking references rather than relying on sales decks?

Because sales decks tell you what the provider wants you to know; references tell you what actually happens after go-live. Operator references in your specific jurisdiction surface integration friction, support-quality drift after contract, hidden fees that emerged during the first quarterly review, and edge cases the sales team didn’t mention. The 30-minute reference call is the single highest-leverage hour you can spend during provider evaluation. Skipping it almost always costs you more than the time saved.