Stablecoin payouts to Europe and the UK: SEPA and Faster Payments side by side

A stablecoin payout reaches a euro bank account over SEPA and a pound account over Faster Payments. SEPA takes about 1 business day and needs at least 50 USDC (or 40 EUR on the receiver side). Faster Payments takes 5 to 30 minutes and needs at least 70 USDC (or 50 GBP). Both quotes can expire in under 5 minutes.

This guide compares the two rails as of October 2026, explains how the minimums work, and adds a short MiCA primer. For the product overview, read what a stablecoin payouts API is. BlindPay publishes this post, so check BlindPay-specific claims in the linked docs.

Key takeaways

• SEPA settles in about 1 business day and Faster Payments in 5 to 30 minutes, per BlindPay's bank accounts docs.
• Minimums depend on which side you denominate: 50 USDC or 40 EUR for SEPA, 70 USDC or 50 GBP for Faster Payments.
• SEPA and Faster Payments quotes may expire sooner than the default 5 minutes, so always read expires_at.
• MiCA's e-money token rules have applied since 30 June 2024 and put obligations on issuers and service providers, not on a business that only sends payouts.

How do SEPA and Faster Payments compare for payouts?

SEPA is the euro rail across Europe and Faster Payments is the UK's real-time pound rail. They share a pattern (bank account, quote, execute) but differ in currency, speed, minimums and account fields.

Pay.UK says Faster Payments has run since 2008, is available day and night, 365 days a year, and supports real-time payments of up to 1 million pounds, with banks setting lower limits of their own. SEPA has an instant variant too: the EPC's SCT Inst rulebook sets a 5 second target and a 10 second timeout. BlindPay's own estimate for SEPA is still about 1 business day for the whole payout, so plan around that number.

For step-by-step setup, see how to off-ramp USDC to euros over SEPA and how to off-ramp USDC to pounds over Faster Payments. For the country list, see SEPA countries and BlindPay's payment methods reference.

How does the minimum amount calculator work?

Each minimum applies to the amount you request, in the currency of the side you denominate. Quote by sender and you compare against the USDC minimum. Quote by receiver and you compare against the EUR or GBP minimum.

A payout quote takes currency_type and request_amount. With currency_type: sender, request_amount is the stablecoin leaving the funding source. With currency_type: receiver, it is the fiat the bank account receives. The payout quotes docs define both, and the payouts docs list the minimums and error codes.

Use this check in your own code before you call the API. The examples are illustrative.

Which side should you denominate? Quote by receiver when the recipient is owed an exact amount, such as an invoice in euros. Quote by sender when you hold a fixed stablecoin amount. Then enforce the matching minimum in your form, so the user sees "minimum 40 EUR" instead of an API error.

Mind cover_fees. With cover_fees: false (the common case) fees come out of the fiat received, so the recipient gets less than the requested amount when you quote by sender. With true, fees are added on top and the recipient gets the full quoted amount, the usual choice for payroll. A quote by receiver with cover_fees: true is the cleanest way to deliver an exact euro or pound figure.

Every other BlindPay rail has a 10 USD minimum sender amount, rejected with LIMITS_AMOUNT_OUT_OF_RANGE. SWIFT is different again: 100 USD on the requested amount, covered in stablecoin to SWIFT routing.

Why do SEPA and Faster Payments quotes expire sooner?

Because the rail's own deadline can be tighter than BlindPay's default. A payout quote lasts 5 minutes, and BlindPay's cut-off times reference says it may be shorter for SEPA and Faster Payments.

What to do about it:

1. Create the quote as late as possible, after the user confirms the amount, not when they open the form.
2. Read expires_at (epoch milliseconds) from the response and show a countdown or a refresh action based on it, never a hardcoded 5 minutes.
3. Execute the payout straight after the user approves.
4. If the quote expired, request a new one, which re-locks the rate and fees. Do not reuse the old quote ID.
5. Use an idempotency key on the execute call so a retry cannot pay twice. See the idempotency docs.

The rest of the flow is the same as on any rail: add the bank account once, quote, execute, then follow processing, on_hold, completed, failed or refunded through webhooks. See how stablecoin payouts work step by step for that flow, and stablecoin payout API pricing for reading the fee breakdown.

What bank details does each rail need?

SEPA needs an IBAN and the beneficiary's legal name and address. Faster Payments needs a sort code, an account number and the beneficiary's legal name and address.

Per the bank accounts docs:

• SEPA: name, account_class, sepa_iban, sepa_beneficiary_legal_name, address line, city, postal code and country. The IBAN's country code must match the beneficiary country. The BIC is optional and derived from the IBAN when omitted.
• Faster Payments: name, account_class, faster_payments_sort_code (6 digits), faster_payments_account_number (8 digits), legal name, address line, city and country.

SEPA payouts to Austria, Estonia, Finland, France, Lithuania and Norway are currently limited to individual beneficiaries. For both rails, the crypto leg runs on Polygon regardless of the network you funded from, which can affect the on-chain timing you see.

What does MiCA mean for payouts to Europe?

MiCA is the EU's Markets in Crypto-Assets Regulation, Regulation (EU) 2023/1114. As of October 2026, its rules for e-money tokens, the category that covers a single-currency stablecoin such as a euro or dollar token, have applied since 30 June 2024.

The points a payout team needs, from the regulation text on EUR-Lex and ESMA's MiCA page:

• Only authorized credit institutions and electronic money institutions may issue e-money tokens.
• Holders have a claim to redeem at par at any time.
• Issuers may not pay interest on e-money tokens.
• The obligations attach to issuers and to crypto-asset service providers, so a business that only sends payouts is not made a regulated issuer by doing so.

Your risk is practical. Fund payouts with a token that is available to EU users, and check whether your own model, for example holding customer funds, needs authorization. MiCA stablecoin rules explained goes deeper, and Europe to Latin America stablecoin payments covers the reverse corridor.

How does BlindPay handle SEPA and Faster Payments?

BlindPay converts USDC or USDT into EUR for SEPA and GBP for Faster Payments through the same API as its other rails. You add the bank account, create a quote that locks the rate and fees, and execute the payout. KYC, KYB, sanctions screening and the travel rule are part of the API flow. Teams that need to reach other countries add SWIFT (POBO/COBO) from the same API, with UETR tracking and MT103 confirmations.

BlindPay's custody wording: BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.

BlindPay's pricing wording: BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. BlindPay does not publish a static flat rate card; always cite the quote's fee breakdown rather than a fixed bps number. No setup fee, no monthly minimum, and development instances are always free.

On a development instance, payouts complete automatically, request_amount 66600 forces failed and 77700 forces refunded, so you can test every status.

Methodology and sources

External sources: Pay.UK on Faster Payments, the EPC SCT Inst rulebook, Regulation (EU) 2023/1114 on EUR-Lex and ESMA's MiCA page.

BlindPay docs used: bank accounts, payouts, payout quotes, cut-off times, payment methods and billing. The BlindPay settlement figures are estimates from the bank accounts docs, not guarantees.

What to do next

Add the matching minimum to your payout form, then request a USDC to EUR quote on a free development instance with the payout quickstart. Compare the expires_at on a SEPA quote with the default 5 minutes. See USDC to EUR for the corridor page.

This article is general information, not legal advice.