Online Casino Payment Gateway Guide 2026: What Operators Actually Need to Know Before They Sign Anything

What exactly is an online casino payment gateway, and how does it differ from a standard gateway?

An online casino payment gateway is a payment processing layer built or configured specifically to handle gambling transactions — meaning it works with banking partners that accept MCC code 7995, supports the fraud and chargeback patterns unique to gaming, and can route through acquiring banks in jurisdictions where gambling is licensed. A standard Stripe or Braintree account will simply decline or terminate you.

The core technical function is the same as any gateway: it tokenizes card data, routes authorization requests to an acquirer, and returns an approval or decline in real time. What makes the casino version different is everything around that core. The acquiring bank behind the gateway must explicitly approve gambling merchants, which means a much shorter list of available banks, higher interchange costs, and rolling reserves that can lock up 5–10% of your monthly volume for 90–180 days while the bank builds confidence in your chargeback ratio.

The fraud profile of a gambling merchant is genuinely different from an e-commerce merchant. Chargebacks on casino deposits tend to come from players who lost money and disputed the charge as unauthorized — so-called friendly fraud. A good casino-specific gateway will have built-in velocity checks, 3DS2 mandates, and BIN-level blocking tools that a generic gateway simply doesn't offer out of the box. Providers like Payvision (now part of ING's wind-down but historically important), Praxis Tech, and PaymentIQ by Devcode were built specifically around these use cases.

There's also the aggregation layer to understand. Most operators don't connect to a single PSP — they use a payment orchestration platform that sits above multiple PSPs and routes each transaction to the best available acquirer based on BIN country, card type, and real-time success rates. PaymentIQ and Praxis are both orchestration layers as much as they are gateways. This matters because a single PSP going down or losing its acquiring relationship — which happens more than vendors admit — shouldn't take your entire cashier offline.

Which payment gateway providers actually work for online casinos in 2026?

The shortlist of payment gateway providers that reliably serve online casino operators in 2026 includes PaymentIQ (Devcode/Everymatrix), Praxis Tech, Nuvei, Paysafe, Skrill/Neteller, and a growing roster of crypto-native processors. The right choice depends on your license jurisdiction, target player geography, and monthly volume — there is no single universal answer.

PaymentIQ remains the dominant orchestration layer in the EU and offshore markets. It's white-labeled by several platform providers including EveryMatrix, and it connects to 250+ PSPs and APMs out of the box. The appeal for operators is speed — you're not negotiating 15 separate PSP contracts, you're connecting to one orchestration layer that already has those relationships. The trade-off is that you're dependent on PaymentIQ's acquirer relationships, and their pricing adds a layer on top of the underlying PSP fees. Budget roughly $0.10–$0.25 per transaction on top of the PSP cost, plus a monthly platform fee that varies by volume tier.

Nuvei has made a deliberate push into regulated gambling markets and now holds acquiring licenses in multiple jurisdictions. They're particularly strong for operators targeting North America and the EU, and they support ACH, Interac, cards, and a range of APMs from a single integration. Their onboarding is more rigorous than offshore-focused PSPs — expect 4–8 weeks and a detailed risk review — but the acquiring stability is considerably better. Paysafe similarly covers the EU and US regulated markets well, especially through their Skrill and Neteller wallets which remain popular in the UK, Germany and parts of LATAM.

For crypto, CoinsPaid is the market leader by volume in iGaming, processing for hundreds of operators and integrating directly with platforms like SoftSwiss (which owns them). NOWPayments and TripleA are solid alternatives with faster onboarding. The practical advantage of crypto gateways isn't just fees — it's that they're not subject to MCC 7995 restrictions and don't carry chargeback risk, which dramatically simplifies your banking situation for the card stack by keeping your dispute ratios clean.

What does a casino payment gateway actually cost, and what fees are operators missing?

Total payment processing cost for a newly launched online casino typically runs 4–9% of gross deposits when you add up MDR, rolling reserves, setup fees, monthly minimums, and chargeback management costs. Most operators budget for the MDR and miss everything else — that gap kills margin in the first year.

The merchant discount rate (MDR) is what vendors quote in sales calls — typically 3–6% for a new offshore operator accepting Visa/Mastercard. But the MDR is only part of the story. Rolling reserves are a silent cost: acquirers typically hold 5–10% of monthly processing volume in a reserve account for 90–180 days. This isn't a fee, but it's real capital tied up. If you're processing $300K/month, you could have $15–30K locked in reserves at any given time. For early-stage operators, that's meaningful working capital.

Chargeback fees are another line item that compounds fast. A single chargeback typically costs $25–50 in fees from the acquirer, on top of losing the transaction amount. If your dispute rate creeps above 1% (Visa's threshold) or 1.5% (Mastercard's), you enter monitoring programs that add surcharges and can ultimately result in account termination. Casino operators are disproportionately exposed here because of friendly fraud — a player losing $500 at slots has a strong incentive to dispute the charge. Investing in 3DS2, transaction velocity limits, and a clear responsible gambling policy isn't just compliance theater; it directly protects your processing relationship.

Setup fees, monthly minimums, and integration costs add another layer. Expect a one-time setup fee of $500–$5,000 depending on the PSP, monthly minimums of $1,000–$3,000 if you don't hit volume thresholds, and integration costs that vary wildly depending on whether you're using a pre-built platform connector or building a custom API integration. If you're on SoftSwiss or EveryMatrix, many PSP integrations are already built — you're paying for the commercial relationship, not the technical work. If you're on a custom build, budget 40–80 developer hours per PSP integration.

Currency conversion fees are easy to overlook if you're targeting multiple markets. A LATAM operator processing BRL or COP through a USD-denominated gateway is eating 1–3% in FX spread on every transaction. Local payment method (LPM) integrations — PIX in Brazil, PSE in Colombia, OXXO in Mexico — solve this but require separate commercial agreements or a well-connected orchestration layer.

How does MCC code 7995 affect your ability to accept card payments?

MCC 7995 is the Merchant Category Code assigned to gambling transactions. It's the reason your Stripe account gets terminated the moment you go live — most card-accepting banks explicitly exclude this MCC from their merchant agreements. Getting card acceptance as a casino operator means finding an acquirer that explicitly approves 7995, which is a short list and a rigorous process.

Visa and Mastercard don't process gambling transactions directly — they set the rules, and acquiring banks decide whether to accept 7995 merchants within those rules. Many banks don't, because the chargeback rates are higher and the regulatory scrutiny is intense. The ones that do — typically banks in Malta, Gibraltar, Isle of Man, Cyprus, and a handful of offshore jurisdictions — charge a premium for it and require upfront documentation: your gaming license, AML policy, responsible gambling procedures, and often 3–6 months of processing history from another acquirer.

The practical implication for a new operator is that you cannot simply apply to a gateway and expect card processing to be available on day one. The acquirer approval process runs in parallel with your license application and can take 4–12 weeks. Some platform providers (SoftSwiss, EveryMatrix) have pre-negotiated acquiring relationships that can accelerate this — you're essentially inheriting their merchant history and risk profile. This is one of the underappreciated advantages of a white-label platform over a custom build for a first-time operator.

Geoblocking at the BIN level is another 7995 consequence. Even if your acquirer approves gambling, individual issuing banks can block their cardholders from making gambling transactions. This is common for US-issued cards on offshore sites, UK banks following GamStop integrations, and increasingly German banks following the GlüNeuRStV reforms. A payment orchestration layer with real-time BIN intelligence can route around some of this by attempting alternative payment flows, but there's no technical fix for an issuer that has categorically blocked 7995 at the card level.

What payment methods should a new online casino offer at launch?

At minimum, launch with Visa/Mastercard, one or two e-wallets (Skrill, Neteller, or MiFinity depending on your market), and a crypto gateway. Add local payment methods within 60–90 days of launch based on where your actual player traffic is coming from. Trying to integrate 20 payment methods before launch is a common mistake that delays your go-live for no conversion benefit.

The 80/20 rule applies hard to payment methods. In most markets, 2–3 methods account for 80%+ of deposit volume. For EU operators, that's typically cards plus PayPal or Skrill. For LATAM, it's cards plus a dominant local method — PIX in Brazil, PSE in Colombia, SPEI in Mexico. For crypto-focused offshore operators, Bitcoin and USDT via a gateway like CoinsPaid can account for the majority of deposits. Launching with every possible method creates integration debt, compliance surface area, and support complexity without proportional revenue benefit.

E-wallets deserve special attention because they solve a specific problem: players who want to keep their gambling activity separate from their bank statement. Skrill and Neteller remain the market standard in Europe, though both have tightened their merchant onboarding since the Paysafe acquisition. MiFinity has gained traction as an alternative, particularly for operators who find Skrill/Neteller onboarding slow. PayPal is available for gambling in select regulated markets (UK, some EU states, certain US states) but is notoriously difficult to obtain and maintain — they can and do terminate casino merchants without much notice.

For US-regulated operators, the payment stack looks completely different. ACH bank transfer is the dominant method in most states. PayNearMe handles cash-at-retail deposits, which remain popular in lower-income demographics. Sightline's Play+ prepaid card is approved in multiple states and solves the card-decline problem elegantly. Venmo and PayPal are available in a handful of states. Apple Pay and Google Pay are slowly gaining traction where the underlying card networks allow it. The key point: US-licensed operators must work with state-approved payment providers, and that list is defined by the regulator, not by you.

How does payment gateway choice differ by jurisdiction — Curaçao, MGA, and US states?

Jurisdiction determines which acquirers will work with you, which payment methods are legally permitted, and how much compliance documentation you need to provide. A Curaçao-licensed operator and a New Jersey-licensed operator are operating in completely different payment ecosystems — the PSP relationships, the permitted methods, and the regulatory oversight are all different.

Curaçao remains the most accessible jurisdiction for new operators, and the payment gateway landscape reflects that. The new Curaçao Gaming Authority (CGA) framework — which replaced the sub-license model in 2023–2024 — requires operators to demonstrate AML-compliant payment processing, but the acquirer pool is broader than for MGA or UKGC licensees. You'll find offshore-focused PSPs willing to onboard Curaçao operators with 2–4 weeks of due diligence. The trade-off is that major card schemes are increasingly scrutinizing Curaçao merchants, and some EU-issued cards will decline. Crypto gateways are particularly well-suited to this market for that reason.

MGA (Malta Gaming Authority) licensees operate in a more structured environment. The MGA requires operators to maintain segregated player funds and to use payment providers that comply with EU AML directives. This actually opens doors with better acquirers — European banks are more comfortable with MGA licensees than with Curaçao operators, which translates to lower MDRs and better card acceptance rates over time. The onboarding process is slower and more document-intensive, but the long-term payment economics are meaningfully better. Expect 6–10 weeks for PSP onboarding alongside an MGA application.

US state-licensed operators are in their own category entirely. Each state (NJ, PA, MI, CT, WV, etc.) has its own approved vendor list for payment processing. The iGaming license application in most states includes a payment processing component, and you cannot simply choose your PSP — you work with what's approved. This is why established US operators like DraftKings and BetMGM have invested heavily in their own payment infrastructure. For a new entrant, the realistic path is partnering with a state-approved processor like Sightline, Everi, or PayNearMe from day one and building the relationship as your license application progresses.

What is payment orchestration, and do online casinos actually need it?

Payment orchestration is a middleware layer that sits between your casino platform and multiple PSPs, routing each transaction to the best available acquirer in real time based on BIN, card type, geography, and success rate data. For operators processing above roughly $200K/month or targeting more than one geography, it's not optional — it's the difference between a 60% card acceptance rate and an 85% one.

The core value of orchestration is redundancy and optimization. Without it, you have a single PSP relationship. When that PSP's acquiring bank has a technical issue — which happens — your cashier goes down. When their acceptance rate drops for UK Visa cards on a Tuesday afternoon, you have no fallback. Orchestration platforms like PaymentIQ, Praxis, and Spreedly (more common in US regulated markets) maintain live success rate data across all connected acquirers and route accordingly. The improvement in acceptance rates is real and measurable: operators typically see 5–15 percentage point improvements in card authorization rates after moving from a single PSP to an orchestration layer.

The second function of orchestration is cascading — if the primary acquirer declines a transaction, the platform automatically retries with a secondary acquirer before showing the player a decline message. This is particularly valuable for cross-border transactions where BIN-level restrictions vary by acquirer. A German Visa card declined by Acquirer A might be approved by Acquirer B who has a different relationship with the issuing bank. Players never see the retry; they just see an approved transaction. The revenue impact of a 5–10% improvement in acceptance rates on a $500K/month processing volume is $25–50K in recovered deposits per month.

The cost of orchestration is real, though. You're paying a per-transaction fee on top of the underlying PSP costs, plus a monthly platform fee. For very small operators (under $100K/month in deposits), the economics may not justify it — a single well-chosen PSP with good acceptance rates in your target market is fine. But the moment you're targeting multiple geographies or processing meaningful volume, the orchestration layer pays for itself quickly. Most white-label platform providers include orchestration as part of their stack, which is one reason the all-in-one platform model makes financial sense for operators who aren't yet at enterprise scale.

How do crypto payment gateways work for online casinos, and what are the real risks?

Crypto payment gateways for online casinos convert player deposits in BTC, ETH, USDT and other assets into a stablecoin or fiat equivalent, crediting the player's account in real time. They eliminate chargebacks and MCC 7995 restrictions, but they introduce AML obligations, blockchain analytics requirements, and player volatility risk that operators underestimate.

The mechanics are straightforward: the player sends crypto to a unique deposit address generated by the gateway, the gateway detects the on-chain transaction, and credits the player's casino wallet — typically in USD or EUR equivalent at the moment of deposit. CoinsPaid, the market leader, handles this flow for hundreds of iGaming operators and processes billions of dollars annually. The settlement to the operator can be in crypto or fiat depending on your preference and the gateway's capabilities. Most operators prefer fiat settlement to avoid balance sheet exposure to crypto price movements.

The AML risk is where operators get caught out. Accepting crypto doesn't exempt you from AML obligations — it adds to them. Your license (Curaçao, MGA, Anjouan, or wherever) requires you to screen incoming transactions for links to sanctioned addresses, mixers, and darknet markets. Blockchain analytics tools like Chainalysis or Elliptic integrate with most major crypto gateways to provide this screening. If you're using CoinsPaid within the SoftSwiss ecosystem, this is largely handled at the platform level. If you're integrating a crypto gateway independently, you need to budget for blockchain analytics — typically $500–$2,000/month depending on transaction volume — and build it into your compliance workflow from day one, not as an afterthought.

Player experience is another consideration. Crypto deposits are fast and cheap, but crypto withdrawals can create friction. Players who deposited in BTC may want to withdraw in a different asset, or may have lost access to their original wallet. Your cashier needs to handle these edge cases gracefully, and your support team needs to be trained on crypto-specific issues like stuck transactions, wrong-network deposits, and gas fee failures. These are solvable problems, but they require preparation that many first-time operators skip.

What does the PSP onboarding process look like, and how long does it take?

PSP onboarding for a casino operator typically takes 2–8 weeks and requires your gaming license, AML policy, corporate structure documents, a processing history if you have one, and a working demo of your cashier. The timeline is directly tied to how complete your documentation is on day one — incomplete applications routinely add 3–4 weeks.

The onboarding process starts with a merchant application that looks similar to a bank account opening. You'll provide certificate of incorporation, shareholder structure, UBO declarations, your gaming license, an AML/KYC policy document, a responsible gambling policy, and often a website review. The PSP's risk team will assess your license jurisdiction, target markets, expected monthly volume, and business model. Some PSPs have automated pre-screening that will reject Curaçao operators targeting US or Australian players outright — knowing this before you apply saves time.

After the initial review, expect a technical integration phase. If you're using a platform with pre-built connectors (SoftSwiss, EveryMatrix, Softgamings), this is largely configuration rather than development — days, not weeks. For custom builds, a full API integration takes 2–4 weeks of developer time depending on complexity. The PSP will then run a technical certification to confirm your integration handles edge cases correctly: partial approvals, timeout handling, refund flows, and webhook reliability. Skipping thorough testing here creates production incidents that are embarrassing and expensive.

Rolling reserves are negotiated during onboarding. The standard offer is 5–10% held for 90–180 days. If you have processing history from another PSP, bring it — 6 months of clean statements with a sub-1% chargeback rate is the single most effective negotiating tool for reducing reserve percentages and MDR. For brand new operators with no history, there's limited room to negotiate on reserves, but you can sometimes get a release schedule tied to milestones (e.g., reserve releases after 90 days if chargeback rate stays below 0.5%).

What are the biggest payment gateway mistakes online casino operators make at launch?

The most common and costly payment mistakes at casino launch are: relying on a single PSP with no fallback, underestimating how long card acceptance approval takes, launching without local payment methods in your primary market, and ignoring chargeback management until you're already in a monitoring program. All four are avoidable with planning.

Single-PSP dependency is the mistake I see most often from operators coming from non-gaming backgrounds. They get one PSP approved, integrate it, and launch. Three months later the PSP loses its acquiring relationship, or the acquirer tightens its gambling policy, and the operator's cashier is down for two weeks while they scramble for an alternative. The fix is simple: have at least two PSPs approved and integrated before you go live, even if you're routing 90% of traffic through the primary one. The second PSP is insurance, and the cost of maintaining it is trivial compared to the revenue impact of a cashier outage.

Chargeback management is the slow-burn mistake. Operators launch, focus on acquisition, and don't monitor their dispute ratio until they get a warning letter from their acquirer. By that point, the ratio is already above 1% and they're in a Visa monitoring program that adds fees and puts the account at risk. The right approach is to implement 3DS2 on all card transactions from day one (yes, it adds friction, but it shifts liability and reduces disputes), set velocity limits on deposits, and review your dispute ratio weekly. Some PSPs provide dispute management tools; others require you to integrate a third-party like Chargebacks911 or Kount.

Neglecting local payment methods is a conversion killer that shows up in the analytics within weeks of launch. If you're targeting Brazil and you don't have PIX integrated, you're losing a significant share of deposit attempts from players who don't have international credit cards or don't want to use them. The same applies to iDEAL in the Netherlands, Trustly in Scandinavia, and UPI in India. The research on which LPMs matter in your target market should happen during platform selection, not after you've already launched and noticed a high payment-failure rate.