Crypto payments for SaaS and iGaming: the structure, the bank and the countries that work.
Every crypto processor will tell you how to integrate. None of them will tell you which company should sign the contract, in which country, with which bank, so the settlements don't close your account six months in. That's this guide. It names no processor; we introduce a licensed one we've vetted once we know your situation.
SaaS and iGaming want crypto for different reasons, and that changes everything after.
A SaaS business
Wants crypto as one more way to get paid: customers in countries where cards fail, teams that hold stablecoins, or lower fees on large invoices. Cards stay the main rail. The questions are recurring billing (crypto can't be pulled), VAT and revenue recognition, and keeping the bank comfortable with a second kind of inflow.
An iGaming operator
Often wants crypto as the main rail, because card acquiring is the hardest thing to get. Here the licence decides everything: which processors will onboard you, which markets you may serve, how player funds are held and reported. The crypto rail is built into the licence application, not bolted on after.
Four pieces, and which company holds each.
- The processor is the regulated party: licensed where your customers are (CASP under MiCA in the EU, VARA in Dubai, the equivalents elsewhere). It takes the customer's crypto, does the KYC and travel-rule work, and settles to you.
- The operating company signs with the processor and owns the customer contracts. It lives where the customers or the team are, and it has the bank account the settlements go to. For iGaming it's also the licensed entity.
- The bank or e-money account, in the operating company's name, told in writing what's coming and from whom. This is the piece people skip and the one that ends the business when it goes wrong.
- The holding or IP company, if there is one, sits above, paid by dividend or licence fee. It never touches a settlement and it isn't the one applying to the processor.
The same shape as any payment set-up for an international business; crypto only changes which processor and what the bank needs to be told.
Customer pays in USDT / BTC / ETH
│
▼
Licensed crypto processor ── KYC, travel rule, conversion
│
fiat ─┤─ or ─ stablecoin
▼ ▼
Operating company bank Company custody wallet
(UK/EU/UAE/GE/MT/CW) (+ an agreed fiat off-ramp)
│
dividend / licence fee
▼
Holding or IP company (optional, never receives settlements)Fiat or stablecoin: the choice that decides your books and your bank.
A licensed crypto processor settling to you in fiat
Customers pay in crypto or stablecoins; the processor converts and settles fiat to the company's bank account. Simplest books, calmest bank, and the processor carries the conversion.
A licensed crypto processor settling in stablecoins, with a treasury plan
You receive stablecoins into a company wallet and convert on your own schedule. Needs a bank that accepts the eventual fiat, a custody arrangement, and records of every receipt and conversion.
The jurisdictions that work, and what the bank says in each.
For the operating company that receives payments. Judged on three things: is there a regime the processor is licensed under, will a bank there accept the settlements, and is the tax treatment of the receipts clear.
United Arab Emirates
SaaS and e-commerce selling worldwide; iGaming only in the specific regulated set-up, not generally.
- Regime
- Virtual-asset activity is licensed (VARA in Dubai, plus the federal and ADGM regimes); a business that only receives crypto through a licensed processor is a customer of that processor, not a licensee.
- Bank
- Workable with the right bank and a licensed processor settling in fiat; stablecoin settlement into a UAE account needs the bank's written position first.
- Tax
- 9% corporate tax above the threshold; free-zone qualifying income rules apply, so where the customers are matters.
- Watch
- Many global aggregators still restrict UAE entities; the crypto processor must be one the UAE bank recognises as licensed.
Georgia
Founders based there or willing to be; SaaS and services with crypto-paying customers.
- Regime
- Virtual-asset service providers register with the National Bank; receiving crypto for your own sales through a registered processor doesn't make you one.
- Bank
- Cautious: local banks accept fiat settlements from recognised processors and are uneasy about direct stablecoin inflows. Keep the processor's registration and the sales records ready.
- Tax
- Company profit is taxed on distribution (the Estonian model); individual entrepreneurs have the small-business regime for qualifying turnover.
- Watch
- Crypto-related turnover can be excluded from the small-business regime; the company route is cleaner for a crypto-heavy business.
EU under MiCA (Lithuania, Estonia, Ireland, others)
SaaS and e-commerce with EU customers; the processor is passported across the EU.
- Regime
- MiCA: crypto-asset service providers are authorised in one member state and passported; stablecoin issuers are regulated. Your processor should hold a CASP authorisation.
- Bank
- Best of the lot once the processor is authorised; EU banks have a framework to point to. Some still decline on sector, so ask before opening.
- Tax
- Standard corporate tax; VAT applies to the sale regardless of how it's paid.
- Watch
- Pre-MiCA 'VASP registrations' are being phased out; a processor that hasn't moved to CASP authorisation is a risk to your settlements.
Malta
iGaming operators who want an EU licence and crypto as one rail among several.
- Regime
- The MGA licenses gaming; crypto activity sits under MiCA via the MFSA. The MGA has a framework for operators accepting crypto deposits.
- Bank
- Malta's banks are selective with gaming; most operators settle through EMIs and specialist acquirers, with crypto processors alongside.
- Tax
- Headline corporate tax with the refund system for shareholders; gaming tax on top.
- Watch
- Cost and timeline are the highest in this list; the licence is the asset, the crypto rail is secondary.
Curaçao (and Anjouan)
iGaming operators starting out or serving markets outside the EU; crypto is the usual first rail.
- Regime
- Curaçao's new gaming authority licenses operators directly (the sub-licence era is over); Anjouan is cheaper and faster, with less recognition.
- Bank
- The weak point. Banks and card acquirers are harder to get than the licence; many operators run crypto-first precisely because of that, which the regulator and the processor will both ask about.
- Tax
- Low local tax; the real cost is the substance the licence now requires and the payment providers' fees.
- Watch
- A licence that acquirers don't recognise doesn't open card acquiring. Plan the crypto rail and the card rail as separate projects.
Singapore and Hong Kong
Larger SaaS and platform businesses with Asian customers; not iGaming.
- Regime
- Singapore licenses digital payment token services under the Payment Services Act; Hong Kong licenses VA trading platforms and is building a stablecoin regime. Strict, slow, respected.
- Bank
- Strong once the processor is licensed locally; banks are used to it.
- Tax
- Territorial elements and low headline rates; stablecoin receipts are revenue like any other.
- Watch
- Onboarding cost and compliance effort are the price of the credibility.
BVI, Cayman, Seychelles
Holding or IP company above the operating company; not the entity that receives payments.
- Regime
- BVI and Cayman have VASP laws for providers; they don't make a merchant's bank problem go away.
- Bank
- Direct settlements to an offshore company are refused by almost every processor and bank. Put the payments in an onshore operating company.
- Tax
- Nil at the company level; the taxing happens where the owners and the substance are.
- Watch
- Applying with the offshore entity first leaves a refusal on file.
Regimes and thresholds change; this is the shape as we work to it, checked case by case before anything is set up.
Recurring billing, VAT and the customer who wants to pay in USDT.
A wallet can't be charged
Recurring billing is a pull payment; crypto is push-only. The patterns that work: annual or multi-month plans, prepaid credits that the subscription draws down, and an invoice link each period for the few who insist on monthly. Keep cards for everyone else.
Price in fiat, quote in crypto
Set the plan price in your billing currency and let the processor quote the crypto amount at payment time. Revenue, VAT and refunds then work exactly as for a card payment, and you aren't carrying exchange-rate risk on receivables.
VAT doesn't care how they paid
Digital services VAT (UK, EU OSS, and the sales-tax equivalents) applies by where the customer is, not by the rail. The processor's settlement report has to carry the customer country or your returns can't be done.
Licence first; then the crypto rail; then, separately, cards.
The licence decides the processors
Reputable crypto processors onboard licensed operators only, and ask which markets the licence covers. Malta for the EU; Curaçao's direct licence or Anjouan to start outside it. The payments plan is written into the application.
Player funds are separate
Deposits are held apart from the company's own funds, in a wallet or account the regulator can see, with the processor reporting on them. One shared treasury wallet is how licences get suspended.
KYC and the travel rule are shared work
The processor does the transaction-level checks; the operator still does player KYC, affordability where the market requires it, and source-of-funds on large wins. Agree who holds which records before launch.
Cards are a second project
A Curaçao or Anjouan licence doesn't open card acquiring by itself. Plan the crypto rail to launch and the card rail as its own application, with the specialist acquirers that take gaming, and don't promise cards on the site until one has said yes.
Where crypto-paying businesses get it wrong.
None of these is advice to do it. Each is here because it comes up on the first call, so you know why not and what to do instead.
Going crypto-only to avoid the gaming licence
Why it's greyNo card acquirer means no acquirer asking for a licence, so some operators launch on crypto alone and plan to license later.
What it meansThe reputable processors ask for the licence anyway; the ones that don't are the ones that disappear with the float. The markets you sell into block the domain, and the licence you apply for later asks about the history. The licence is step one.
Treating stablecoin receipts as 'not revenue until converted'
Why it's greyBecause nothing hits the bank, the receipts sit in a wallet and out of the books until a conversion forces the question.
What it meansEverywhere we work the receipt is a sale on the day, at that day's value; the conversion is a second event with its own gain or loss. Two ledgers, kept from day one, are what the bank and the tax office both ask for.
Mixing player funds with the company's own stablecoins
Why it's greyOne treasury wallet is simpler than two.
What it meansEvery gaming regime requires segregation, and the processor's terms do too. Mixed funds are the fastest route from a licence to a suspended one.
Taking crypto straight to a company wallet, no processor
Why it's greyIt saves the processor's fee and feels like the point of crypto.
What it meansIt also puts the KYC, the travel-rule reporting and the source-of-funds work on you, and gives the bank a stream of unexplained inflows. A licensed processor is what makes the bank conversation possible.
Settling to a personal wallet or a related company
Why it's greyThe company can't get a bank account yet, so the founder's wallet or a sister company receives the settlements 'for now'.
What it meansProviders call it a mismatch and freeze; later, moving the money back into the company is its own problem. Fix the company's banking first (that's usually a structure question, not a crypto one).
General information, not advice. Licensing, the treatment of crypto receipts and bank policy differ by country and change; what applies to you is set out in writing after a call.
Can your business accept crypto? Check in a minute.
Six questions. You get the route, the steps in order, the countries where it's routine, and what not to do. No processor is named.
What people ask on the first call.
Do I need a crypto licence to accept crypto payments?
Not to receive payment for your own goods or services through a licensed processor: the processor is the regulated party. You would need one if you held or exchanged crypto for other people, which is a different business.
Will my bank close the account if I receive crypto-processor settlements?
Some will, usually without warning, if they weren't asked. Fiat settlements from a licensed processor are accepted by many banks when the licence and the sales records are on file; stablecoin inflows are the harder conversation. Ask in writing before the first payment.
Can a SaaS do recurring billing in crypto?
Not as a pull payment: a wallet can't be charged. The working patterns are annual or prepaid plans, credits, and an invoice link each period, with cards kept for customers who want monthly.
Can an iGaming operator run crypto-only without a licence?
Some do, and it's the most common way to lose the business: processors drop them, the domain gets blocked in the markets they sell into, and the licence they later apply for asks about the history. The licence comes first.
Which country is best for a crypto-paying business?
The one where the company can get a bank that accepts the settlements, under a regime the processor is licensed in: the EU under MiCA and the UAE are the usual answers for SaaS and e-commerce, Malta or Curaçao for iGaming, Georgia for founders based there. An offshore company is for holding, not for receiving payments.
Tell us the business, the company and the bank.
We set up the operating company and the banking, write the payments plan into any licence application, and introduce a licensed processor we've vetted when one fits. Free, in writing, within a working day.