SEPA Countries List: What It Means for USDC to EUR Payouts

SEPA is the Single Euro Payments Area, and the European Central Bank counts 41 countries in it as of May 22, 2025. Twenty-six use the euro at home. The other 15 keep a national currency and use SEPA for euro payments. The split is 27 EU states plus 14 others, including the United Kingdom and Switzerland, cross-checked on Wikipedia.

The full SEPA countries list

The rules are the SEPA schemes, written and administered by the European Payments Council (EPC), an association of payment service providers. The last column adds what the SEPA list cannot say: the tier each country holds on Lumx's supported countries page, which is where Lumx onboards customers, not where a payout can land.

The 41 SEPA countries, by group, by the currency each uses at home, and by Lumx's onboarding tier (membership status May 22, 2025; Lumx tier as of November 2026)

The count of 41 and its status date come from the ECB's SEPA page, read on November 1, 2026. The split into 27 EU entries and 14 others was cross-checked against Wikipedia, because the EPC's register of SEPA scheme countries, the primary list, is bot-blocked and was not read. It is cited by name and not linked.

The ECB adds that the region also includes "several territories with historical ties" to member countries, which the table leaves out; the EPC register is the source to check.

Which SEPA countries use the euro, and which keep their own currency?

Twenty-six use the euro and 15 do not. Among EU members, 21 use it: the ECB's page shows Croatia joined the euro in 2023 and Bulgaria in 2026. Six EU members keep their own money. Outside the EU, the EU's own page on the euro abroad names Andorra, Monaco, Montenegro, San Marino and Vatican City among the non-EU countries that use it, and all five are in SEPA. Kosovo also uses the euro, per the same page, but it is not in the 41, so a euro payment to Kosovo is not a SEPA payment.

SEPA countries by currency group

SEPA fixes the currency of the transfer at the euro and says nothing about the currency of the recipient's account. A Polish company can receive a SEPA transfer, and its bank decides whether the euros stay in a euro account or are converted into zloty at its own rate.

On Lumx, a EUR payout goes out by SEPA to an IBAN and a BIC. The IBAN is the international bank account number that identifies the recipient's account, and the BIC identifies the bank. Lumx charges a flat fee on SEPA, as on any rail, and what the recipient's bank charges depends partly on where it sits, as the next section explains.

SEPA is not the same as the EU, the euro area or the EEA

The euro area is the 21 EU members that use the euro. The EU has 27 members, and the European Economic Area adds Iceland, Liechtenstein and Norway. SEPA adds 11 more countries on top of the EEA's 30: Switzerland, the United Kingdom, Andorra, Monaco, San Marino, Vatican City, Albania, Moldova, Montenegro, North Macedonia and Serbia.

The ECB draws one practical line. The scheme rules apply in every SEPA country, but EU-law rules such as equal charges for euro transactions do not apply outside the EU and the EEA, so a euro transfer to Zurich or London follows the scheme without that rule behind it.

The list is young at its edge: Wikipedia's accession timeline has Serbia joining on May 22, 2025. A new member's banks join over time, so test a destination there first.

Two other boundaries are easy to cross by mistake. A sterling payment is not a SEPA payment: the pound runs on Faster Payments, the UK's real-time bank transfer network. And SEPA membership says nothing about how crypto-assets are regulated, which is a separate question under MiCA, Regulation (EU) 2023/1114, covered in the MiCA explainer for payment companies.

On Lumx, EUR payouts go over SEPA and GBP payouts over Faster Payments, each enabled by requesting the currency when the customer is created. Which countries a payout can reach is set by the coverage page and the customer's compliance review, not by the SEPA list.

How a SEPA payment moves: two schemes and a 100k window

SEPA has two credit transfer schemes that matter for payouts. The fast one is SCT Inst, the scheme the ECB describes as making funds available in the payee's account within ten seconds of the payment order. The ordinary SEPA Credit Transfer is slower and runs on business days. The ECB welcomes Regulation (EU) 2024/886 of March 13, 2024, which aims to speed up the fast scheme's uptake, and notes it is not available to the same degree across all SEPA jurisdictions, so how much of a country's volume runs on it depends on its banks.

The two SEPA credit transfer schemes and how Lumx routes between them

On Lumx, the sender always asks for rail SEPA and cannot pick the scheme. Lumx routes each payment to one or the other, and the docs publish the €100k window above, so a large payout sent overnight should be planned as a same-day or next-day payment. For a euro payout that has to reach a bank today, the amount and the clock are the two inputs.

How does a USDC to EUR payout reach a SEPA bank account?

The stablecoin converts to euros and is sent by SEPA to the recipient's IBAN, so the recipient sees an ordinary euro bank transfer. This is the stablecoin off-ramp with the euro as destination, the same shape as any stablecoin corridor.

1. The paying company is an approved customer with the EUR account requested, because each currency has to be requested before a payout or collection.

2. The company registers the recipient as a destination: rail SEPA, currency EUR, the IBAN and BIC, the recipient's bank, and the account holder with a declared relationship to the customer, such as supplier or employee. For SEPA the addresses need only the country. Destinations go through verification, and a webhook tells the app when one is approved.

3. The company quotes the payout. A floating rate is a reference with no fee. A locked rate fixes the conversion for 30 seconds, 1 minute or 5 minutes, with a fee only on the longer locks.

4. The company requests the payout from its balance in USDC, the dollar stablecoin, naming the destination, the amount and the purpose of the payment. A webhook fires at each status step.

On Lumx, USDC converts to EUR on Ethereum, Polygon and Base, and USDT on Ethereum, Polygon and Tron. The price for the pair is on the USDC to EUR page, and the way in, from euros to a stablecoin balance, is on the EUR to USDC page.

<!-- OPERATOR PARAGRAPH --> I recommend that a team paying Europe sorts its payee list by the currency of the recipient's account before it sorts by country. The SEPA list says nothing about what the receiving bank does with the euros. For the 15 countries that keep their own currency, I would ask each recipient whether the account holds euros, and I would quote the amount the recipient should receive in euros, so that nobody finds the conversion on a statement a week later.

When a SEPA payout is the wrong tool

A SEPA payout is the wrong tool when the recipient needs local money. A supplier in Warsaw who must receive zloty gets euros and a conversion at its own bank. A euro payout on Lumx pays euros, so ask that recipient for a euro account or pay another way.

It is also the wrong tool for a recipient outside the 41 countries, who on Lumx receives USD by SWIFT, and for a sterling recipient, who is paid over Faster Payments.

What this looks like on a SEPA payout with Lumx

Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

For Europe, there are two directions on one customer. A EUR account moves to active right after the customer is approved, and an autoconversion rule on it returns an IBAN and a BIC to give the sender: every euro that arrives by SEPA converts to the stablecoin and network the rule names, such as USDC, in the customer's custodial wallet, and a customer can have one active EUR rule at a time. Going out, the payout in the section above runs from the same wallet. Lumx counts the payout complete once the funds leave its banking partner, and the receiving bank can still hold them for its own review. A compliance hold on the way surfaces as an RFI (request for information).

The supported countries page tiers where Lumx onboards customers, and says a Restricted country means no transactions with parties based there. Customers in the United Kingdom are onboarded by reverse solicitation, as Lumx holds no FCA license. Read against the 41, 36 are Supported, Bulgaria, Croatia and Monaco are High-Risk with Enhanced Due Diligence for customers, North Macedonia is Restricted, and Vatican City does not appear on the page.

Before the first EUR payout, run one check on the payee list: take each recipient's country, find its tier on the supported countries page, and ask the compliance team about any that is not Supported. Then confirm the pair on the coverage page.

The corridor is on the global payments product page, and the coverage page lists the supported pairs and rails. See how Lumx compares with BVNK, and the operator map for who operates where.

Methodology and sources

Checked on November 1, 2026. The ECB supplies only the count of 41 (status May 22, 2025), the euro dates, the territories line and the limit of EU charges rules, from its SEPA page, and the ten-second definition from its page on fast payments. The euro users outside the EU, Kosovo included, come from the EU's page on the euro internationally. The European Payments Council register of SEPA scheme countries is the primary list of members and is cited by name; the 27 EU members and the 14 others come from Wikipedia's SEPA article, a secondary source, and add up to the ECB's 41. Lumx product facts come from docs.lumx.io pages read that day: coverage, cut-off times, accounts, destinations, transactions, autoconversion rules and supported countries.

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Willy the Wizard on Unsplash.