Payments and withdrawals

How to Choose a Payment Service Provider for iGaming

A practical framework for selecting and managing payment service providers in regulated gambling: what to ask, what to measure, and how to avoid single points of failure.

12 min readPart of payments and withdrawals

On this page
  1. What does a PSP do for an online gambling operator?
  2. What should operators ask a PSP before signing?
  3. How do regulators affect PSP choice?
  4. How do you run PSP selection step by step?
  5. Which metrics show whether a PSP is working?
  6. What should a PSP contract cover?
  7. How should routing between providers work?
  8. How do PSP issues show up in support?
  9. What should due diligence on a PSP cover?
  10. How should a new PSP be tested before launch?
  11. How does PSP onboarding work, step by step?
  12. Which regulators affect PSP choice in each market?
  13. What does a well-run payments stack look like?
  14. Worked example 2: adding Interac for Ontario
  15. Which local PSP capabilities matter in each market?
  16. Worked example: replacing a failing provider
  17. What mistakes do operators commonly make?
  18. Checklist
  19. Frequently asked questions
  20. Sources
  21. More guides

Choose a payment service provider on five things: whether it covers the local methods players use in each market, whether it is licensed and acceptable to your regulator, its approval and payout performance for the gambling category, the fraud and compliance data it returns, and its commercial terms including reserves. Most operators run two or more PSPs per critical method, with routing between them, so no single outage stops deposits or payouts.

Key takeaways

  • Method coverage per market matters more than the total number of methods a PSP lists.
  • Ask for approval rates for gambling merchants by method and issuer, not a blended figure.
  • Payout capability and payout status data are as important as deposits, because payouts drive complaints.
  • Regulators expect payment flows to stay inside the licensed system; providers that serve unlicensed sites face blocking orders.
  • Run at least two providers for each critical method and measure them monthly.
2+providers per critical method
MCC 7995card category for betting and casino
24 hoursBrazil blocking deadline for illegal operators’ accounts

What does a PSP do for an online gambling operator?

A payment service provider connects the operator’s cashier to the payment methods players use. Depending on the provider, that includes card acquiring, local bank rails, e-wallets, vouchers and payouts, plus fraud screening, 3-D Secure authentication, name matching and reporting. Some operators also use a payment orchestration layer that sits above several PSPs and routes each transaction to the best one.

What should operators ask a PSP before signing?

PSP due diligence questions
Area Question to ask Why it matters
Coverage Which methods do you support in each of our markets, for deposits and for payouts? Coverage drives first deposit conversion and payout speed.
Licensing Are you authorised where required, and do you serve unlicensed gambling sites? Regulators can order providers to stop serving illegal operators; your own licence depends on clean flows.
Performance What are approval rates for gambling by method, country and issuer? Gambling approval rates are lower than for general ecommerce.
Payouts How fast are payouts, what are the failure rates, and is there a status API? Status data lets support answer “where is my money” automatically.
Compliance data Do you return the account holder name, card country, and 3-D Secure result? Needed for own-name rules, closed loop and chargeback evidence.
Fraud tools What screening and velocity rules are included, and can we tune them? Reduces fraud losses and chargebacks.
Commercials What are fees, rolling reserves, settlement times and minimums? Reserves tie up working capital.
Operations What is your incident process and how do you notify outages? Outages hit deposits and payouts at the same time.

How do regulators affect PSP choice?

Gambling regulators do not usually license PSPs directly, but they shape the choice in three ways. First, payment rules: Brazil’s Ordinance 615/2024 lists allowed methods and requires accounts at institutions authorised by the Central Bank [1]; Germany’s anti-money laundering law limits deposits and payouts to own-name payment accounts [2]. Second, enforcement against providers: Germany’s GGL issues payment blocking orders to providers serving unlicensed operators, and Brazil’s Ordinance 2,750/2026 requires institutions to block illegal operators’ accounts within 24 hours of notice [3]. Third, licence conditions: operators must show they control their payment flows and can evidence AML checks.

How do you run PSP selection step by step?

  1. Define requirements per marketList required methods, legal restrictions, payout needs, currencies and expected volumes for each market.
  2. Build a long listUse your platform’s existing integrations first; each new integration costs engineering time.
  3. Send a structured questionnaireUse the questions above and ask for references from licensed operators in the same market.
  4. Test in production with small volumeRoute 5 to 10% of traffic to the new provider and compare approval and payout data.
  5. Set routing rulesRoute by method, country, issuer and recent performance. Keep a fallback for every critical method.
  6. Review monthlyTrack approval rate, payout time, failure rate, chargeback rate and cost per successful transaction.

Which metrics show whether a PSP is working?

PSP performance metrics
Metric Definition What good looks like
Approval rate Successful deposits divided by attempts Stable or rising by method and issuer
Payout success rate Payouts settled without failure Failures caught and rerouted the same day
Time to settle Time from payout approval to funds received Matches the method’s normal range
Chargeback ratio Disputes divided by transactions Well below scheme thresholds; see chargebacks
Cost per successful deposit All fees divided by successful deposits Compared across providers for the same method
Support contacts per 1,000 transactions Payment-related contacts relative to volume Falls as status data reaches support

Payment data is also support data. When the payout status API feeds support tools, most “where is my money” contacts can be resolved automatically; see withdrawal support automation guide on igamingsupportai.com and Cevro on how to automate withdrawal support in online casinos.

What should a PSP contract cover?

PSP contract checklist
Clause What to look for
Service levels Uptime, incident response times, payout processing times
Reserves Size, duration, release conditions
Fees Per transaction, per method, FX, chargebacks, refunds, payouts
Data Access to transaction-level data, account holder name, status APIs
Compliance Their licences, AML programme, cooperation with your audits and regulators
Termination Notice, data return, migration support
Market scope Which markets and methods are covered, and whether they serve unlicensed operators there

How should routing between providers work?

  1. Define primary and fallback per methodEvery critical method has a second provider configured and tested.
  2. Route on live performanceShift traffic when approval rates or latency fall below thresholds.
  3. Respect compliance constraintsSome markets need locally authorised institutions; routing must not break own-name or closed loop rules.
  4. Log decisionsRecord which provider handled each transaction for disputes and audits.
  5. Test failover quarterlySimulate an outage and confirm deposits and payouts keep working.

How do PSP issues show up in support?

Players rarely know which provider failed; they see a declined deposit or a late payout. Tagging payment contacts by method and provider shows patterns early, often before the provider reports an incident. Connecting provider status to support tools lets agents and AI agents answer accurately. See withdrawal support automation guide and recovering failed deposits.

What should due diligence on a PSP cover?

PSP due diligence
Area What to check
Licensing Authorisation as a payment or e-money institution where required
Safeguarding How player funds in transit are protected
Security PCI DSS compliance for card data
Sanctions and AML The PSP’s own controls and screening
Financial health Accounts, ownership, reserves
Gambling experience Acquiring for gambling in your markets
Incident history Outages, data breaches, regulatory actions

How should a new PSP be tested before launch?

  1. SandboxTest every method, currency and error path.
  2. Production pilotSmall live volume with staff accounts, then a share of real traffic.
  3. ReconciliationMatch PSP settlement reports to the operator’s ledger daily.
  4. Payout testsTest payouts, refunds and reversals, not only deposits.
  5. FailoverTest routing to a backup provider.
  6. Support readinessBrief support on new decline messages and timings.

How does PSP onboarding work, step by step?

  1. ApplicationThe operator supplies company documents, licences and ownership details.
  2. UnderwritingThe PSP and its acquiring banks assess the gambling risk, markets, volumes and chargeback history.
  3. Merchant setupMerchant accounts are created, typically under the gambling merchant category code 7995, with separate MIDs by market or brand where needed.
  4. IntegrationThe cashier is connected through the PSP’s API or hosted pages; payouts, refunds and webhooks are built as well as deposits.
  5. Certification and testingTest transactions in sandbox and production, including declines and payouts.
  6. Go-liveTraffic is ramped up gradually with monitoring of approval rates and errors.
  7. Ongoing reviewMonthly performance reviews and annual due diligence on both sides.

Which regulators affect PSP choice in each market?

Regulators that affect PSP choice
Market Regulator What it covers for this topic Official source
Great Britain Gambling Commission No credit cards for gambling [4] Credit card ban
Brazil SPA Payments through authorised institutions to accounts in the bettor’s name [1] Secretaria de Prêmios e Apostas
Germany GGL Own-name payment accounts [2]; the GGL also uses payment blocking against unlicensed operators GwG section 16, GGL
Ontario AGCO and FINTRAC Registrar’s Standards and casino AML duties [5] [6] Registrar’s Standards, FINTRAC casino guidance
Mexico SEGOB Permit regime and AML thresholds under the LFPIORPI [7] SEGOB
New Jersey Division of Gaming Enforcement Account and payout rules in N.J.A.C. 13:69O [8] N.J.A.C. 13:69O-1.3, New Jersey DGE

What does a well-run payments stack look like?

Payments stack playbook
Area What good looks like
Coverage At least two providers per key method in each major market
Routing Smart routing by method, BIN and market, with automatic failover
Data Approval, decline and payout times visible daily by provider
Reconciliation Daily matching of settlements to the ledger
Contracts Clear service levels, reserves, fees and exit terms
Support link Agents see payment status and decline reasons in real time

Worked example 2: adding Interac for Ontario

  1. The operator shortlists PSPs that support Interac e-Transfer for Ontario-registered gaming.
  2. Due diligence covers licensing, Interac support for gaming, payout speed and FINTRAC-related reporting support.
  3. Integration is complete in sandbox, including payouts.
  4. Production pilot with staff accounts, then 10% of Ontario traffic.
  5. Approval rates and payout times meet targets; the PSP becomes primary for Interac, with the previous provider as backup.

See Interac for iGaming in Canada.

Which local PSP capabilities matter in each market?

PSP capabilities by market
Market Capability that matters most Rule to check Source
Great Britain Pay-by-bank and debit; credit blocking including e-wallets funded by credit Credit card ban [4]
Ontario Interac e-Transfer pay-ins and payouts AGCO standards; FINTRAC reporting [5] [6]
Germany Own-name account checks and payment reference on payouts GwG section 16 [2]
Brazil Pix with CPF name matching; authorised institution status Ordinances 615/2024 and 2,750/2026 [1] [3]
Mexico SPEI and cash voucher networks; AML threshold tracking LFPIORPI [7]
New Jersey ACH, prepaid and cage cash-out integration; failed deposit lockouts N.J.A.C. 13:69O-1.3 [8]

Worked example: replacing a failing provider

An illustrative case: an operator’s main card provider in one market sees approval rates fall over two weeks.

  1. Monthly review shows debit approval down from the usual range; contacts about declined deposits up 40%.
  2. Routing moves 20% of card traffic to the backup provider. Its approval rate on the same issuers is higher.
  3. Pay-by-bank promoted above cards in the cashier for returning players.
  4. Main provider explains an issuer-side rule change; fix applied. Traffic split rebalanced by performance.
  5. Declined-deposit contacts back to normal. Lesson: without a second provider, the operator would have lost deposits for three weeks.

What mistakes do operators commonly make?

Choosing on headline method count

A provider with 300 methods may have none of the three your market needs.

Single provider for a critical method

Outages stop deposits and payouts together.

Ignoring payouts in testing

Deposit tests pass while payout failures surface weeks later as complaints.

No name data returned

Without the account holder name, own-name and third-party checks become manual.

Not checking who else they serve

Providers serving unlicensed sites in your market can be ordered to stop processing [3].

Untested failover

Backups that have never carried traffic fail when needed.

Ignoring reserve terms

Reserves can lock up significant cash.

Testing deposits only

Payout and refund paths fail in production.

Checklist

  • Method coverage confirmed per market for deposits and payouts.
  • Provider authorisation status checked where required.
  • Approval data by method and issuer received before signing.
  • Payout status API available and connected to support.
  • Account holder name and 3-D Secure result returned.
  • Backup provider live for every critical method.
  • Reserves and settlement terms modelled in cash flow.
  • Monthly PSP scorecard in place.
  • Contract covers SLAs, reserves, data and termination.
  • Failover tested quarterly.
  • Routing decisions logged.
  • Payment contacts tagged by provider.
  • PCI DSS evidence from PSP.
  • Daily reconciliation.
  • Failover tested.

Frequently asked questions

What is a PSP in online gambling?

A payment service provider that processes deposits and withdrawals for the operator, often with many local methods behind one integration.

How many PSPs does an operator need?

At least two for each critical method in each market, so traffic can be rerouted during outages or approval drops.

What is payment orchestration?

Software that connects to several PSPs and routes each transaction to the best provider based on rules and live performance.

Why are gambling approval rates lower?

Card issuers treat the gambling merchant category as higher risk, and some block it entirely.

Do gambling regulators approve PSPs?

Usually not directly, but payment rules, own-name requirements and blocking orders shape which providers can be used.

What is a rolling reserve?

A share of processed funds held back by the provider for a period to cover chargebacks and other liabilities.

What data should a PSP return?

Transaction status, account holder name, card country, authentication result and payout status.

How do PSPs affect customer support?

Payment failures and slow payouts are major contact drivers; payout status data lets support answer them quickly.

What is failover in payments?

Automatically switching to a backup provider when the primary one fails.

Should operators share routing data with support?

Yes, provider and status data help agents answer payment questions accurately.

How often should PSPs be reviewed?

Monthly on performance, and annually on contract and compliance.

What is a MID?

A merchant ID assigned by an acquirer; operators may need separate MIDs by market or brand.

Should payouts be tested before launch?

Yes. Payout failures cause more complaints than deposit failures.

What is MCC 7995?

The merchant category code for betting and gambling, used by issuers to recognise gambling transactions.

Why do operators need separate MIDs?

Acquirers and regulators often expect separate merchant accounts by market or brand, which also helps reporting.

Sources

  1. iGaming Business: Brazil betting payment methods (Ordinance 615/2024)
  2. Geldwäschegesetz section 16
  3. Agência Gov: SPA ordinance against the illegal betting market (September 2026)
  4. Gambling Commission: credit card ban
  5. AGCO: Registrar’s Standards for Internet Gaming
  6. FINTRAC: casinos
  7. KYC Systems: LFPIORPI for games and raffles
  8. N.J.A.C. 13:69O-1.3 (Justia)

Payment methods by market

Which deposit and payout methods players use in each regulated market, and which are restricted.

Open banking and pay-by-bank

How pay-by-bank deposits and payouts work, why they suit gambling, and the risks to manage.

Chargebacks in iGaming

How card disputes work for gambling merchants, why they happen and how to reduce them.

How casino withdrawals work

The payout process step by step, the real reasons withdrawals are held, and what regulators expect.

KYC and payment events in CRM

How failed deposits, pending withdrawals and verification triggers should feed CRM.

Further reading elsewhere