The licence is not the last gate. It is the second to last. Operators budget for the application, the incorporation and the policy pack, get the certificate, and then discover that the payment provider they assumed would onboard them wants four things they do not have and declines them for a fifth they did not know was disqualifying. The platform sits finished, the domain is live, and nothing can be deposited.
This is a practitioner's guide to how a licensed crypto casino actually gets paid: the three rails available to you, what a payment provider tests at onboarding, the reasons applications get declined, and where your choice of licence quietly decides which providers will speak to you at all. It assumes you are licensed or close to it, as set out in how to start a crypto casino in 2026.
Three rails, and they fail for different reasons
Most operators think of payments as one problem. It is three, with almost nothing in common between them.
- Direct on-chain. Players send to an address you control. No intermediary, no onboarding, no one who can decline you. In exchange you carry custody, key management, address monitoring, accounting and the entire compliance burden yourself. The rail nobody can take away is also the rail nobody helps you run.
- Custodial crypto gateway. A processor generates addresses, confirms deposits, handles conversion and settles to you. Faster to launch and it removes the custody problem, but it is an onboarding relationship, which means diligence, which means you can be declined and you can be offboarded later.
- Fiat card acquiring. Visa and Mastercard deposits through a high risk acquirer. The hardest to obtain, the most expensive to run, and still the reason a meaningful share of players deposit at all. This is where applications die.
A crypto-only operator can launch on the first two and never touch the third. Most operators who want volume outside crypto-native audiences eventually need all three, and the sequencing matters, because the diligence for the third is far heavier than for the second.
Why card acquiring is the hard one
Online gambling sits under merchant category code 7995, which the card schemes classify as high risk. That classification is not a judgement about you. It is a statement that the acquirer carries the liability if you fail, and it drives everything that follows.
- Rolling reserve. A percentage of settlement withheld against future chargebacks, commonly in the region of five to ten percent held for six months. Model this before you sign. An operator who has not planned for it discovers that a meaningful slice of their first two quarters of revenue is not available to them.
- Chargeback exposure. Scheme monitoring programmes trigger when your chargeback ratio crosses roughly one percent, and the consequences escalate from fines to termination. Gambling attracts friendly fraud at higher rates than most sectors, because a losing player has an obvious incentive.
- Scheme registration. Gambling merchants require registration with the card schemes through your acquirer, which is a separate step from acquirer approval and adds time.
- Geographic restriction. Your acquirer will restrict which player countries you may accept, and it will not be the same list your licence permits.
What onboarding actually tests
Business diligence for a gaming merchant is not a form. Providers ask for a file, and the completeness of that file is the single largest determinant of whether you are approved and how long it takes.
- The licence and its conditions. Not the certificate alone. Providers read the conditions attached to it, because those conditions define what you are permitted to offer and to whom.
- The AML programme and a named MLRO. The first document requested and the most common point of failure. What it has to contain is set out in the policy pack an operator actually needs.
- Corporate structure and UBO documentation. Certified passports, proof of address, a clean structure chart. An opaque chain of holding companies reads as concealment even when it is ordinary tax planning.
- Domain ownership and a live site. Providers check that the domain is licensed, that terms and responsible gaming pages are published, and increasingly that the site matches what you described.
- Processing history. Statements from a prior provider if you have them. A first-time operator without history is not disqualified, but is priced and reserved accordingly.
- Source of funds and a business plan. Where the operating capital came from, and volume projections a provider can sanity check against your traffic.
The six reasons applications get declined
In practice, declines cluster. Almost every one traces to something on this list, and every item is fixable before you apply.
- The licence does not carry weight with that provider. Not every regime is accepted by every processor, and the acceptance list is rarely published.
- The policy pack is a template. Documents that name no MLRO, describe no risk assessment, or contain another operator's jurisdiction are read in seconds and rejected in seconds.
- The target markets include restricted countries. Naming a market your provider cannot serve ends the application even if that market was a small part of the plan.
- UBO disclosure is incomplete or evasive. Nominee structures are lawful and common, and they still require the beneficial owner to be disclosed to the provider.
- The site is not live or not consistent. A placeholder page, missing terms, or games listed that you have no agreement to offer.
- Projections do not match reality. Volume forecasts far above what the traffic supports read as either inexperience or something worse.
Your licence choice is a payments decision
This is the part most operators learn too late. The cheapest licence that satisfies a regulator is not automatically the licence that satisfies a payment provider, and the gap between those two standards is where budgets get rewritten.
Anjouan and Tuvalu clear regulatory requirements at a fraction of the cost and issue in weeks. Curacao costs several times more and takes longer, and its value is largely reputational: it is the name payment providers, banks and game suppliers recognise, which converts directly into onboarding acceptance. Whether that premium is worth paying depends entirely on which rails you intend to run. An operator building crypto-only on direct settlement rarely needs it. An operator who wants card deposits from day one often does.
Decide the payments question before the licensing question, not after. The five regimes are set out side by side on the licence comparison, and if card acquiring is in your plan, weight recognition more heavily than headline cost.
Crypto brings its own layer of diligence
A crypto gateway applies everything above and then adds a second set of tests that fiat processors never run.
- Deposit screening. Incoming funds are screened against sanctions lists and risk-scored by chain analytics providers such as Chainalysis, Elliptic or TRM Labs. Deposits traced to mixers, sanctioned addresses or darknet markets are frozen, and repeated exposure ends the relationship.
- Travel Rule obligations. Originator and beneficiary information must accompany transfers above jurisdictional thresholds, and those thresholds differ materially between the EU, the US and offshore regimes. Your provider will expect you to know which apply to you.
- Withdrawal controls. Paying out to a different address than the deposit came from is a standard laundering pattern. Your policies need a documented position on it before a provider asks.
- Stablecoin and network policy. Which assets and which chains you accept is a risk decision, not a product decision, and providers will ask you to justify it.
Sequence it properly
The order below removes most of the delay operators experience, because it front-loads the work that payment providers gate on rather than discovering it at application.
- Choose the licence against your payments plan, not only against cost and speed.
- Draft the policy pack to your specific licence conditions while the application is running, not after it.
- Publish terms, responsible gaming and privacy pages before you approach any provider. Curacao licensees have a hard terms deadline covered in the LOK deadlines piece.
- Open crypto rails first. Lighter diligence, faster approval, and a processing history you can show the card acquirer later.
- Approach card acquiring with three months of history and a complete file. Apply to more than one, because approval is not guaranteed anywhere.
- Plan the reserve into cash flow from the first projection, not the first settlement.
Payments is not a step that happens after licensing. It is the constraint that should shape the licence, the structure and the policy pack from the beginning. Operators who treat it that way launch. Operators who treat it as an afterthought spend a quarter with a finished casino nobody can deposit into.
Rakemont structures licensing and formation with the payments outcome in mind, and issues a fixed written quote before any work begins. If you are weighing jurisdictions and card acquiring matters to you, tell us that at the first conversation rather than the third.
Frequently asked questions
Why do crypto casinos get declined by payment providers?
Most declines trace to an incomplete file rather than the business itself: a template AML programme with no named MLRO, undisclosed or opaque beneficial ownership, target markets the provider cannot serve, a site that is not live or does not match the application, or a licence that particular provider does not accept. Every one of these is fixable before applying.
Do I need a licence to get a crypto payment gateway?
For gambling merchants, yes in practice. Custodial gateways serving iGaming require a valid gaming licence and read the conditions attached to it, not just the certificate. Direct on-chain settlement to a wallet you control involves no onboarding, but leaves you carrying custody, screening and compliance yourself.
What is a rolling reserve on a gaming merchant account?
A percentage of each settlement withheld by the acquirer against future chargebacks and released on a delay, commonly in the region of five to ten percent held for six months. It is standard for merchant category code 7995 and should be modelled into cash flow before you sign, because it materially affects available revenue in the first two quarters.
Which gaming licence do payment providers accept most readily?
Curacao carries the strongest name recognition with payment providers, banks and game suppliers, which is the main argument for its higher cost. Anjouan, Tuvalu, Vanuatu and Tobique satisfy regulators at a fraction of the price and suit crypto-first operators well, but acceptance varies by provider and is rarely published. If card acquiring is central to your plan, weight recognition more heavily than headline cost.
Can I run a crypto casino without card payments?
Yes, and many do. A crypto-only operator running direct on-chain settlement or a custodial gateway avoids merchant category code 7995 entirely, along with chargebacks, rolling reserves and scheme registration. The trade-off is reach, since it limits you to players who already hold crypto.
What does a payment provider ask for at onboarding?
The licence and its conditions, an AML programme with a named MLRO, KYC procedures, corporate and UBO documentation, proof of domain ownership with a live compliant site, processing history where it exists, source of funds, and volume projections that match your traffic. Completeness of the file is the single largest factor in both approval and timeline.