Crypto On/Off-Ramps in Europe: 20 Providers Compared

Last updated Oct 30, 2026

This guide is for wallets, exchanges, fintechs and other platforms that want to embed a crypto on-ramp or off-ramp for users in the EU, the UK, Switzerland, Norway, Iceland, Liechtenstein and the European microstates. It maps which payment rails 12 integrable products from 11 providers document, by country and by direction; nine more providers are covered in notes, for 20 in all. In short, euro bank transfers are well documented and almost everything else is thin. Eleven products document a SEPA-wide buy and eight a SEPA-wide payout. Apart from euro transfers over SEPA, the only bank payouts in the tables are pounds over Faster Payments (four products) and CHAPS (one), and Swiss francs over SIC (one). For the named EU and EEA countries, the breadth on the way out comes from card payouts: Banxa documents them in all 27 EU states and MoonPay's partner widget in 26.

How to read the tables

The tables compare 12 product entries from 11 providers; nine more providers, Bitpanda, Bitso Business, Mercuryo, Revolut, Stripe, Topper, Unlimit, Wert and zerohash, appear in notes below, for 20 in all. We left out pages that describe a merchant's checkout or a consumer account rather than a ramp another business can integrate. Rails were checked on 27 October 2026, and every source behind a Supported or With conditions cell was re-opened on 30 October 2026. This follows the same method as our North America comparison.

Tier identifies the product you would integrate, not the whole company: a partner widget (the provider's hosted or embedded checkout, with its own KYC and pricing) or a B2B API (you build the flow; the provider converts and settles). MoonPay Enterprise's business virtual accounts count as an API. Buy funds a crypto purchase with fiat; Sell pays fiat out. Conditions records the provider's own limitation, quoted or closely summarised. Rail names follow the provider's wording. – means the direction doesn't apply to that rail, for example a card-payout method has no buy side.

A SEPA zone row is a provider statement about SEPA as a whole, not a country-by-country list; where a provider names countries, the table names them too. The Other European countries tab covers Andorra, Monaco, San Marino and Vatican City, with the country named in each row.

European Union: SEPA both ways is common, other EU bank rails are not documented

What to take from it

• Buying with a SEPA transfer is documented by 11 of the 12 products. Coinbase CDP is the exception: its table lists cards, not SEPA. Five products name SEPA Instant for buying: Alchemy Pay, Monerium, MoonPay Enterprise, MoonPay's partner widget and Transak.
• Cashing out over SEPA is documented by eight. Banxa, Bridge, Monerium, MoonPay Enterprise, MoonPay's partner widget, Mt Pelerin, Paybis and Ramp Network have a SEPA payout row. Alchemy Pay, Simplex and Transak document SEPA for buying only, so a payout from them is not documented in these tables.
• SEPA Instant payouts appear at four: Monerium, MoonPay Enterprise, MoonPay's partner widget, and Ramp Network, which says "where available".
• Conditions decide whether a row applies to you. Bridge asks you to contact its sales team "to access EUR and the SEPA payment rail", and its account manager for "3PP deposits from individuals". Simplex offers direct SEPA "based on your location, device and the partner's platform". Ramp Network says buying availability "is based on your location and is displayed during checkout". MoonPay's partner widget limits SEPA to "EUR-denominated transactions in SEPA countries only".
• Card payouts carry the country-by-country breadth. Banxa lists card payouts in all 27 EU states, and MoonPay's Visa Direct Payout list covers 26 of them, all but Malta. Paybis lists Mastercard credit/debit payouts for the EU, and Coinbase CDP lists cards for buying and selling across "US and 90+ additional countries (including EU,UK,CA)" without naming EU states.
• National schemes are nearly empty. The only country-level bank scheme in the tables is Banxa's iDEAL for buying in the Netherlands. No integrable product in this sample documents a payout over a non-euro EU bank rail, such as Swedish, Polish, Danish or Czech domestic transfers.

Ace Werk analysis: if your users hold euros, SEPA in both directions is the baseline you can expect. For anything else, treat each country as a separate integration question. A card payout may be the only documented way back to fiat in a user's own currency, and a card payout is a different product from a bank transfer, with its own limits and failure modes.

United Kingdom: Faster Payments in both directions at four products

What to take from it

• Four products document Faster Payments both ways: Banxa, Bridge, MoonPay Enterprise and MoonPay's partner widget. Bridge requires a sales contact "to access GBP and the FPS payment rail". MoonPay's partner widget limits Faster Payments to "GBP-denominated transactions in the UK only".
• Paybis and Transak document Faster Payments for buying only. A UK bank payout from either is not documented in these tables. Transak also lists Open Banking and card payments for buying in the UK.
• CHAPS appears once, at MoonPay Enterprise, in both directions.
• Card payouts to UK cards are documented by MoonPay's partner widget (Visa Direct) and by Coinbase CDP, whose card row covers buying and selling.
• Euro rails for UK users: Bridge's SEPA country list names the United Kingdom, in both directions. The Transak SEPA buy rows for the UK are our inference: Transak's coverage page lists the UK, and its SEPA methods sit under its euro section. Both are marked with conditions because they move euros, not pounds. Confirm the Transak rows with Transak before relying on them.

Ace Werk analysis: for a UK product, a Faster Payments payout row is the deciding check, because four of the seven products in this table document one. Speed labels here describe how the payment moves. They don't tell you when crypto is delivered or when a payout is final.

Switzerland: one Swiss-franc payout rail, otherwise euros and cards

What to take from it

• Mt Pelerin is the only product that documents a Swiss-franc bank rail: "SIC - For CHF transfers to Switzerland" in its off-ramp list. Its on-ramp list also names SIC "for CHF transfers from Switzerland"; that buy-side line is not yet in our dataset, so the table shows only the payout.
• Bridge's SEPA list names Switzerland, both directions, in euros, with the same sales-contact condition as everywhere else.
• MoonPay's partner widget lists Switzerland for Visa Direct card payouts.

Ace Werk analysis: for Swiss users who want francs back in a Swiss account, the documented choice in this sample is one product. Everyone else's route back to fiat is euros over SEPA or a card payout.

Norway: EEA rules bring SEPA rows, but no krone rail is documented

What to take from it

• MoonPay Enterprise documents SEPA Instant for "Instant EEA transactions sub €100k", which covers Norway as an EEA state. We derived the row from that EEA statement. It shows buying only: the rail table gives no direction, and our extraction rules read it as a funding row. The same page says its EUR rails support "both onramp (fiat to crypto) and offramp", but a payout under the EEA wording is not recorded, so the Sell cell is Not documented (see "How we verified").
• Bridge's SEPA list names Norway (both directions, with conditions), and MoonPay's partner widget lists Norway for Visa Direct payouts.
• No product in the sample documents a Norwegian-krone bank rail.

Iceland: two products, euros only

What to take from it

• Bridge's SEPA list and MoonPay Enterprise's EEA SEPA Instant row are the only Iceland entries.
• Iceland is missing from MoonPay's Visa Direct payout list, although that list includes Norway and Liechtenstein, so a card payout to Icelandic cards is not documented. No Icelandic-krona rail is documented anywhere in the sample.

Liechtenstein: the EEA pattern again

What to take from it

• The same three entries as Norway: Bridge SEPA in both directions, MoonPay Enterprise SEPA Instant buys under its EEA condition, and MoonPay partner card payouts.
• Liechtenstein uses the Swiss franc, and none of the Swiss-franc options above names Liechtenstein: Mt Pelerin's SIC line says "to Switzerland".

Other European countries: Andorra, Monaco, San Marino and Vatican City

What to take from it

• Bridge's SEPA list names all four, in both directions, with conditions.
• **MoonPay's partner widget lists Andorra, Monaco, San Marino and Vatican City for Visa Direct payouts.

Providers outside the tables

Nine more providers were checked but sit outside the tables. For six, the business documentation names no European bank rail by country and direction. For the other three, the only rail evidence is a page that isn't about a ramp. A row would claim more than the source says.

• Bitpanda: the SEPA deposit and withdrawal limits we found are on a help-centre page for Bitpanda account holders. It documents no ramp for another business to embed.
• Bitso Business: its SEPA transfer flow moves euros for a business client from that client's USD stablecoin balance, after "onboarding with a licensed partner". It is a treasury feature, not an end-user ramp, and it names no countries.
• Mercuryo: its business help centre lists bank transfer in the SEPA zone as "Temporarily unavailable" (❌). Its off-ramp pays out to Visa or Mastercard with no countries named. Its other methods are wallets such as Apple Pay and Google Pay.
• Revolut: the Revolut Ramp partner API shows payment methods only in sample responses (Revolut account, Apple Pay, Google Pay, card), with no bank rail tied to a country.
• Stripe: the European methods we found, such as iDEAL, BLIK, TWINT, Bacs and SEPA Direct Debit, come from Stripe's general merchant payment-method matrix. Stripe's Onramp is in private preview, and its EU integration guide covers KYC and MiCA identifiers but names no funding method. As in our North America comparison, merchant payment methods are not counted as ramp rails.
• Topper: its on-ramp flow takes credit or debit cards and its off-ramp pays out to linked debit cards. The API lists "sepa" only as an example network value, with no countries.
• Unlimit: the European methods we found, such as Bancontact, Giropay, Multibanco, Bizum, iDEAL, BLIK and SEPA, are on Unlimit's merchant acquiring coverage page, not a ramp page.
• Wert: its service-availability page lists countries but names no rail.
• zerohash: its supported-regions page is an availability table without rails, and the rails its fiat docs name are US ones: ACH, RTP and FedNow.

BitPay, Gemini and Kraken were dropped before this round. They were not re-checked for Europe.

Bridge also notes that "USDC & EURC are the only stablecoins supported for users in the EEA due to regulatory restrictions". This is a limit on the asset, not the rail, so it isn't in a table cell.

Choosing a provider: six rules from the tables

These rules are Ace Werk analysis. Each one rests on the rows cited with it.

1. Read the Sell column before the Buy column

Nine of the 12 products document at least one payout row. Alchemy Pay, Simplex and Transak document buying only, so cashing out through them is not documented in these tables. If your users need to cash out, shortlist from the nine.

2. Decide which currency your users are paid in

The only non-euro bank payouts in the sample are pounds over Faster Payments (Banxa, Bridge, MoonPay Enterprise, MoonPay's partner widget) or CHAPS (MoonPay Enterprise), and Swiss francs over SIC (Mt Pelerin). For a user in Sweden, Poland, Norway or any other non-euro country, the documented options are a euro SEPA payout or a card payout.

3. Treat conditions as part of the coverage

31 of the 133 dataset rows behind the tables carry a condition, at five products. Bridge gates SEPA and Faster Payments behind a sales contact. MoonPay Enterprise's EEA SEPA Instant row applies "sub €100k". Ramp Network pays out over SEPA "where available". Simplex's SEPA buy depends on "your location, device and the partner's platform". Transak's UK euro rows are our inference from its coverage page.

4. Don't read a SEPA-zone row as a country list

Most SEPA rows are a provider statement about SEPA as a whole. In these tables, named-country rows come from three lists only: Bridge's SEPA country list (used here for the non-EU tabs), and Banxa's and MoonPay's card-payout lists. Before you promise a country, ask the provider whether its "SEPA" claim covers users who live there, not just IBANs issued there.

5. Keep payment speed, crypto delivery and payout finality separate

Providers publish different kinds of timing, and the same provider can publish two. Monerium says SEPA Instant payments "settle within 5 seconds, including the time to mint or burn EURe tokens onchain". Transak says a SEPA bank transfer "May take up to 3-5 Working Days". MoonPay's partner help pages give SEPA payouts as "2 to 4 business days" on one page and "1-3 business days" on another. An instant rail tells you how the bank leg moves. It doesn't tell you when crypto is delivered or when a payout can't be reversed.

6. Decide between a widget and an API

All four B2B APIs in the tables (Bridge, Coinbase CDP, Monerium and MoonPay Enterprise) document payouts, against five of the eight partner widgets. An API typically leaves more of the flow to you to build. A widget brings the provider's own checkout, KYC and pricing.

Where to start

Ace Werk analysis, not provider statements.

Regulatory clock: what is in force and what is still coming

The tables record what providers document about rails. They are not licensing opinions, and we didn't check any provider's authorisation status. These are the dates that shape the rails, as of 30 October 2026.

What this means for the tables, as Ace Werk analysis:

• SEPA Instant is becoming a baseline for euro bank accounts, not a provider feature. Since 9 October 2025, euro-area PSPs must be able to send instant euro transfers, and they have had to receive them since 9 January 2025. A provider that lists only standard SEPA may still pay out more slowly on its own side, so ask about its payout process, not only the rail.
• A fast bank rail is not the same as a final payout. The regulation covers the bank transfer. A provider's compliance checks, its crypto-settlement step and its own payout batching all sit outside it.
• In the EU, ask which entity is the authorised CASP for your users and in which Member State it is authorised. The transition period is over. In the UK, the regime isn't in force yet, so ask what each provider's position will be after 25 October 2027.

Take legal advice on your own structure; this section is not legal advice.

FAQ

Which crypto on-ramps support SEPA Instant in Europe?

For buying, five products document SEPA Instant: Alchemy Pay, Monerium, MoonPay Enterprise, MoonPay's partner widget and Transak. MoonPay Enterprise's row applies to "Instant EEA transactions sub €100k". For payouts, four document it: Monerium, MoonPay Enterprise, MoonPay's partner widget, and Ramp Network "where available". A rail labelled instant tells you how the bank payment moves, not when crypto arrives or when a payout is final. Monerium says its SEPA Instant payments "settle within 5 seconds, including the time to mint or burn EURe tokens onchain". MoonPay's partner pages list SEPA and SEPA Instant payouts together at "2 to 4 business days" on one page and "1-3 business days" on another.

Which crypto off-ramps pay out to UK bank accounts over Faster Payments?

Four products document Faster Payments in both directions: Banxa, Bridge, MoonPay Enterprise and MoonPay's partner widget. Bridge requires you to contact its sales team "to access GBP and the FPS payment rail". Paybis and Transak document Faster Payments for buying only, so a UK payout over Faster Payments is not documented for them. MoonPay Enterprise also lists CHAPS in both directions.

Can users cash out crypto to a debit card in Europe?

Yes, at four products. Banxa documents card payouts in all 27 EU states. MoonPay's partner widget lists Visa Direct payouts in 26 EU states (all but Malta) plus the UK, Switzerland, Norway, Liechtenstein, Monaco, San Marino and Vatican City. Paybis lists Mastercard credit/debit payouts for the EU. Coinbase CDP lists debit and credit cards for buying and selling in "US and 90+ additional countries (including EU,UK,CA)", without naming EU states. Payout timing differs by page: MoonPay gives "1 to 2 business days" for "Visa to direct cards" on one page and "Instant - Up to 1 business day" for Visa Direct Payout on another. Banxa's methods table lists card payouts as "Instant". For Paybis and Coinbase CDP, card payout timing is not documented in these rows.

Do iDEAL, BLIK or other local payment methods work for crypto ramps in Europe?

Barely, in this sample. The only country-level scheme in the tables is Banxa's iDEAL, for buying in the Netherlands. Transak lists Open Banking for buying in the UK. Stripe and Unlimit list many local methods, but on general merchant payment pages rather than ramp documentation, so they are not counted (see "Providers outside the tables"). No table row documents a payout over a local method.

Can my platform earn a fee or revenue share from an embedded ramp in Europe?

Two of the nine providers outside the tables publish partner-fee fields in their API docs. Topper's on-ramp API accepts a partner.fee.percentage field — "Percentage of the total source amount (the maximum allowed value is '5')" — and marks the older partnerFee field deprecated. Revolut's Crypto Ramp API returns feePercentages, an array of numbers such as 0.8 or 1 in its GET /2.0/config response. Neither page describes the fee as a revenue share or specifies how it is calculated beyond the percentage. The other seven providers' partner terms are not public in the pages we checked. Ask each provider for its partner terms before you compare on price.

What does "not documented" mean in these tables?

It means the official pages we checked on 27 October 2026 don't state that rail, country and direction together. It isn't a refusal: the provider may support it and not publish it. Mentions that name a method without a country are kept in notes, not rows. Examples are Mercuryo's card off-ramp with no countries named and Ramp Network's card payouts in "supported locations". When a provider marks a method unavailable, as Mercuryo does for SEPA bank transfer, that also goes in the notes. Ask the provider before relying on a blank cell.

How we verified, and what we couldn't

On 27 October 2026 we fetched 45 official pages from 20 providers: docs, help centres, API guides and coverage pages. No search results, comparison sites or blog posts were used as evidence. Each page was split into sections, and every section was read twice by a language model under fixed rules. A deterministic script then rebuilt the dataset. It kept a row only where the page names the rail, the country or group, and the direction, and it quotes the exact line. An auditor running a different model then checked a sample of 98 rows against the saved pages: 75 base rows and all 23 rows derived from country lists. All passed. For this article, an editor matched every row behind the tables against its saved page and re-opened each live source on 30 October 2026. Two of MoonPay's help pages turned out to quote different payout times, so both are cited where timing comes up. We didn't open accounts or run test transactions, so these tables describe documentation, not observed behaviour.

Known gaps:

• MoonPay Enterprise payouts in Norway, Iceland and Liechtenstein. The page says its EUR rails support "both onramp (fiat to crypto) and offramp (crypto to fiat)", and that SEPA Instant covers "Instant EEA transactions sub €100k". The rows we derived for the three non-EU EEA states cover buying only. A SEPA payout there is likely but is shown as Not documented until MoonPay confirms it.
• Bridge's country coverage. Bridge's SEPA rows rest on the IBAN country list in its EUR integration guide. Bridge also publishes a separate supported-countries compliance list, which grades each jurisdiction by risk. Our extraction of that list stopped partway through the alphabet, so we didn't use it to confirm which countries Bridge onboards. Read the Bridge rows as "SEPA payments to and from IBANs in these countries", and check the compliance list yourself before relying on them.
• Monerium. Monerium's rows describe euros moving in and out of its EURe token ("Euros sent to the IBAN, via SEPA, are automatically minted as EURe"), not purchases of any crypto asset, and the page names no countries beyond SEPA.
• Ramp Network UK bank rail. Ramp's help page shows a GBP bank-transfer option in a browser-rendered table that our capture of the page didn't include, so the UK table shows no Ramp bank rail. Ask Ramp before ruling it out.
• Mt Pelerin SIC buy. Mt Pelerin's on-ramp list names SIC "for CHF transfers from Switzerland", but the extraction missed that line, so the Switzerland table shows only the payout. The quote is in the saved snapshot.
• Page dates. Most pages show no publication date. Where a page gives a relative date ("2 weeks ago"), we report the check date instead.

The dataset behind this edition has 159 rows. The 26 rows from Stripe's and Unlimit's merchant payment pages and Bitpanda's account limits page are excluded from the tables for the reasons given above. That leaves 133 rows in 53 provider-rail table rows.

Building ramps for European users?

If you're adding on- and off-ramps to a wallet, exchange or fintech product, we can shortlist providers for your countries and directions, check the conditions behind each row with the providers, and design the integration around the gaps.

Talk to Ace Werk about your ramp integration

Sources

Provider pages were fetched on 27 October 2026 and re-opened on 30 October 2026. Regulatory pages were opened on 30 October 2026. Page dates are the publishers' own where the page shows a fixed date; where it shows none, or only a relative one, we say "no date shown". Grouped by provider, with regulators last. Numbers match the source links in the tables.

Alchemy Pay

1. EU (SEPA zone): What payment methods and currencies are supported on Alchemy Pay? (16 Jun 2026)

Banxa

1. EU, UK, Netherlands, card-payout countries: Supported Payment Methods (no date shown)

Bridge

1. UK: GBP integration guide (no date shown)
2. EU, UK, Switzerland, Norway, Iceland, Liechtenstein, Andorra, Monaco, San Marino, Vatican City: EUR integration guide (no date shown)

Coinbase Developer Platform

1. EU, UK: Onramp Supported Payment Methods (no date shown)

Monerium

1. EU (SEPA zone): Move Euros Between Banks and Blockchains Instantly (no date shown)

MoonPay Enterprise

1. EU, EEA, UK: Currencies and Rails ("Coverage snapshot: September 2026")

MoonPay (partner widget)

1. EU, UK (SEPA, Faster Payments, payout timing): Payment methods, settlement times, and limits (28 Jul 2026)
2. Card-payout countries (Visa Direct), payout timing: MoonPay's supported payment methods (26 Aug 2026)
3. EU (Visa card payouts): Supported withdrawal methods for selling cryptocurrency (14 Oct 2025)

Mt Pelerin

1. EU (SEPA zone), Switzerland: Payment methods (no date shown)

Paybis

1. EU, UK (buying): Payment Methods (no date shown)
2. EU (payouts): Payout Methods (no date shown)

Ramp Network

1. EU (buying): Buy Crypto with SEPA Transfer (no date shown)
2. EU (payouts): Which payout methods can I use when selling crypto? (no date shown)

Simplex

1. EU (SEPA zone): What are your supported payment methods? (no date shown)

Transak

1. EU, UK: Payment Methods & Processing Time (no date shown)

Regulators and legislation

1. EU: Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA), Articles 143 and 149 (EUR-Lex, 31 May 2023, published 9 Jun 2023)
2. EU: List of grandfathering periods decided by Member States under Article 143 of MiCA (ESMA)
3. EU: Regulation (EU) 2024/886 on instant credit transfers in euro (EUR-Lex, 13 Mar 2024)
4. EU: Instant Payments Regulation, implementation deadlines (ECB)
5. UK: The Financial Services and Markets Act 2000 (Cryptoassets) Regulations 2026 (SI 2026/102)
6. UK: A new regime for cryptoasset regulation (FCA)
7. UK: FCA opens the gateway to regulated crypto (FCA, 30 Sep 2026)

Pages checked for the providers outside the tables (not cited for any table cell): Bitpanda help centre, Bitso Business SEPA transfer flow, Mercuryo business help centre, Revolut Ramp API, Stripe payment-method support and Onramp EU KYC guide, Topper on-ramp and off-ramp flows, Unlimit Europe and UK coverage, Wert service availability, zerohash supported regions and fiat docs. URLs are in the dataset's source list (sources-v6.json).