Converting USDC to EUR in a SEPA bank account: which networks work, the IBAN details you need, SEPA vs SEPA Instant timing, limits, and what MiCA changes.
To off-ramp USDC to euros, verify with a provider that pays out over SEPA, add the recipient's IBAN, BIC, legal name, and address, quote the payout, and send native USDC on a supported network. The provider converts it and sends EUR as a SEPA credit transfer, which reaches the bank by the next business day, or in seconds on SEPA Instant.
Three things trip people up here: the token, the name on the account, and which SEPA scheme the provider uses.
It's a crypto off-ramp whose fiat leg is a SEPA credit transfer in euros. You send stablecoins to the provider, it converts them to EUR at a quoted rate, and the euros land in an IBAN anywhere the provider covers in the Single Euro Payments Area.
SEPA isn't only the eurozone. The scheme covers 41 countries, including non-euro members such as the UK, Switzerland, Sweden, and Norway, as long as the account receives euros. For dollar payouts, the US off-ramp guide covers ACH, RTP, and wire the same way.
USDC, on a network the provider accepts for SEPA.
Why USDC. MiCA, the EU's crypto rulebook, only lets regulated service providers offer stablecoins whose issuer is authorized in the EU. Circle issues USDC and EURC under a French e-money license. In January 2025, ESMA told national regulators to make sure providers restricted non-compliant stablecoins by the end of Q1 2025. The MiCA explainer covers why USDT ended up delisted for EU users, and USDC vs USDT for payments covers the wider trade-off.
Which network. On BlindPay, SEPA payouts accept native USDC from these networks, per the SEPA launch notes:
| Network | SEPA payouts (quote and execute) | Offramp wallets on a SEPA account |
|---|---|---|
| Polygon | Yes | Yes |
| Ethereum | Yes | Yes |
| Base | Yes | Yes |
| Arbitrum | Yes | Yes |
| Solana | Yes | Yes |
| Stellar | Yes | No |
| Tron | No | No |
"Native" matters. A bridged version of USDC on the same chain is a different token and won't be accepted.
SEPA payouts run on the IBAN. These are BlindPay's required fields for a sepa bank account, per the bank accounts reference, and most providers ask for the same.
| Field | Example | Watch out for |
|---|---|---|
| IBAN | DE89 3704 0044 0532 0130 00 | The country prefix must match the beneficiary's country |
| BIC | COBADEFFXXX | The bank's SWIFT code. Some banks have several |
| Beneficiary legal name | Müller Logistik GmbH | The exact name on the account |
| Address, city, postal code | Hauptstraße 1, Berlin, 10115 | Required for compliance screening |
| Country | DE | Must match the IBAN |
| Account class | Individual or business | Decides which use cases are allowed in some countries |
The name is the field that causes the most trouble now. Since 9 October 2025, euro-area banks must offer Verification of Payee under the Instant Payments Regulation. It compares the name you send with the account holder's name and returns a match, a close match, or no match. A trading name instead of the legal name is the classic mismatch.
Two schemes, two very different clocks.
| SEPA Credit Transfer (SCT) | SEPA Instant (SCT Inst) | |
|---|---|---|
| Settlement | By the end of the next business day (PSD2, Art. 83) | Seconds: 5-second target, 10-second timeout (EPC rulebook) |
| Weekends and holidays | No, business days only | Yes, 24/7/365 |
| Amount limit | Set by banks | No scheme maximum since October 2025. Banks set their own |
| Price | Bank-set | Can't cost more than a standard transfer, under the Instant Payments Regulation |
Since 9 October 2025, euro-area payment providers that offer standard credit transfers must also send and receive instant ones. That doesn't mean every off-ramp uses SEPA Instant for payouts. Ask.
On BlindPay, the bank accounts reference plans for about one business day on SEPA, and the launch notes put euros in the IBAN 5 to 30 minutes after the USDC is received. Build your ETA copy on the business-day figure and treat faster as a bonus. Payout quotes on SEPA can also expire sooner than the usual five minutes, so read expires_at and execute promptly. The settlement times by rail put SEPA next to Pix, SPEI, ACH, and SWIFT.
Three layers, and the lowest one wins.
Country rules sit on top. BlindPay pays out to 40 SEPA countries, listed in payment methods. Seven of them, Austria, Estonia, Finland, France, Lithuania, Norway, and Portugal, are limited to payouts between individuals for now, so a business can't pay a French supplier over this rail yet. Check the recipient's country before you build the flow around it.
| Problem | Cause | How to avoid it |
|---|---|---|
| Bank account rejected | IBAN country doesn't match the beneficiary's country | Check the two-letter IBAN prefix against the address |
| Payout not allowed | Business sender or business recipient in an individual-only country | Check the country rules before onboarding the recipient |
| Name check fails | Trading name sent instead of the legal name | Collect the exact account holder name |
| Quote rejected | Below 11 USDC, or below 10 EUR on a receiver-amount quote | Quote above the minimum, or batch small amounts |
| Quote expired | SEPA quotes can expire faster than five minutes | Execute right after quoting, and read expires_at |
| Funds sent but not accepted | USDT, a bridged token, or a network SEPA doesn't take | Send native USDC on a listed network |
Most of these fail at account creation or quote time, before any money moves. That's the point of validating early. The last one doesn't, which is why the network check belongs in your own UI, next to the address.
Four lines, same as any off-ramp: network gas on the USDC transfer, the USD to EUR spread, the provider's percentage fee, and a flat payout fee. SEPA transfers themselves are cheap, and the Instant Payments Regulation stops banks from charging more for instant than for standard.
The spread is where the money goes. Compare the live rate on USDC to EUR against the mid-market rate at the same minute. Quoting by EUR amount, with fees covered by the sender, lets the recipient get an exact invoice amount. The quotes explainer covers fee direction and minor units.
BlindPay converts native USDC and pays out EUR over SEPA through the same payout API it uses for Pix, SPEI, ACH, and wire. Add a sepa bank account, quote by USDC or EUR amount, authorize the USDC from your wallet, and create the payout. For USDC that arrives from third parties, link an offramp wallet to the SEPA account and every USDC deposit pays out on its own. KYB, KYC, and sanctions screening run inside the flow.
Start in the sandbox with the payout quickstart.
This article is for general information only and is not legal, tax, or financial advice.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.
Seven stablecoin payment platforms compared for US fintechs in 2026: what makes an API production-ready, how each provider handles compliance, settlement speed against ACH, and how to run the evaluation.
How to choose a stablecoin payment provider in 2026: the four provider types, a comparison of 10 options, and the questions that decide the fit.