Euro payments, unified
topropay is the orchestration layer that puts SEPA credit transfer, SEPA instant payments and SEPA direct debit behind a single connection — alongside cards, wallets and the local methods your customers already trust. One integration, every SEPA account in scope, with smart rail selection that lands each payment as fast and as cheaply as the scheme allows.
The short version
The Single Euro Payments Area collapsed dozens of national bank schemes into one set of rules for moving euros. For a business selling, billing or paying out in Europe, that means a SEPA bank transfer to a customer in Lisbon clears the same way as one to a customer in Helsinki, with one set of files and one set of error codes. The reach is enormous and the per-payment cost is tiny — but to actually use it, you still need IBAN validation, mandate storage, rail selection, R-message handling and reconciliation glue that most teams do not want to build.
topropay gives you all of that out of the box. A single integration covers SEPA credit transfer, SEPA instant payments and SEPA direct debit, sits next to cards and wallets in the same routing layer, and reconciles every leg into one ledger. You add a SEPA account collection, a new SEPA zone country or a mandate-based subscription as configuration, never as a new integration — and your finance team gets one consistent view across every rail.
Why teams choose us
Merchants and PSPs move to a unified euro layer to cut cost, speed up settlement and stop maintaining a separate stack just for the SEPA region.
SEPA instant moves funds in under ten seconds, 24/7. Recurring renewals, marketplace payouts and one-off SEPA transfer pay-ins land before the customer has closed the tab.
From Ireland to Cyprus, Norway to Malta, the same SEPA bank transfer flow works wherever your customers hold an IBAN — no per-market provider rebuild.
Account-to-account moves bypass card interchange and the chargeback surface that comes with it. For high-ticket and B2B flows, a SEPA payment is often the cheapest authorised route.
SEPA sits alongside Visa, Mastercard, wallets and local methods behind one API. Routing decides per-transaction which rail to use, so SEPA is a first-class option, not a bolt-on.
Two rails, one API
Both rails live behind the same integration. The platform picks the right one per transaction based on the payer's SEPA bank reachability and your policy.
The bedrock of euro payments — bank-business-day batched credit transfers, low cost, high reach.
The 24/7 instant rail — irrevocable euro transfers settled in under ten seconds, any day of the year.
How it works
Four stages, one API. The platform handles each one whether the payment is a one-off SEPA bank transfer, a recurring SEPA mandate collection or an instant payout.
Your application calls a single endpoint with the payer's IBAN, the amount in euro and a reference. Either a SEPA credit transfer or a SEPA instant payment is selected based on policy and bank reachability.
Where the flow requires it, the payer authenticates through their bank — open banking redirect, app confirmation or a SEPA mandate already held on file for recurring debits.
The payment moves through the SEPA scheme rails (SCT, SCT Inst, SDD Core or SDD B2B) and is debited from the payer's SEPA account.
Funds settle to your designated account — within seconds on SEPA instant, next business day on standard SEPA credit transfer — and are reconciled into the unified ledger.
Where it fits
The flows where moving from cards to SEPA — or adding SEPA alongside them — shifts the economics most visibly.
Move five- and six-figure invoices over SEPA bank transfer without paying card interchange. The SEPA credit transfer leg is the cheapest authorised route for a high-value payment between two euro accounts.
Run recurring billing on a signed SEPA direct debit mandate. The mandate is stored once and reused for every collection, with cascading retries when a payer's bank returns a temporary R-message.
Pay out sellers and creators on SEPA instant the moment funds clear. A payout that used to wait for the next bank-business-day batch now lands in seconds, every day of the year.
Reverse a payment over SEPA instant payments in under ten seconds — a powerful retention move when a card refund would have taken a week to credit.
Move euro liquidity between corporate SEPA accounts across providers and countries using one API, with a single normalised ledger of every leg.
These flows overlap in practice. A SaaS business expanding from the UK into the euro area needs mandate-based subscriptions and instant refunds at the same time; a marketplace serving creators needs instant payouts on SCT Inst and treasury sweeps on standard SCT in the same operation. Because every rail sits on one integration, you can run them together without adding vendors.
Capabilities
Everything you need to initiate, authenticate, clear and reconcile a SEPA payment lives in the platform — no extra mandate vault, IBAN tool or reconciliation script bolted on around the edges.
A single REST endpoint covers SCT, SCT Inst and SDD. Pick the variant in a parameter or let policy decide automatically.
If the payer's SEPA bank is reachable on SCT Inst, the routing engine prefers it; otherwise it falls back to standard SEPA credit transfer.
SEPA mandates are stored, versioned and reusable — collect a debit weeks or months after the first signature without re-prompting.
Each IBAN is validated at the structural and check-digit level before the call leaves your servers, and routed to the right scheme on submission.
Returns, rejects and refunds (R-transactions) are normalised into a single reason-code taxonomy, so finance does not need to learn each bank's quirks.
Every state change emits a webhook, and every settlement reconciles into one ledger that exports cleanly to your ERP.
The same engine that runs SEPA also runs cards, wallets and account-to-account rails elsewhere, so the SEPA region is one capability inside a broader payment fabric — not a side project.
Coverage
The SEPA zone covers the EU, EEA and a handful of additional markets — 36 SEPA zone countries and territories at the time of writing. Reach them all from the same API.
You do not pick a SEPA bank per market. The platform speaks to the scheme directly, so any IBAN issued in the SEPA region is a valid destination or source for a SEPA bank transfer the moment you switch the rail on.
Industry relevance
Wherever euro revenue flows or euro payouts go out, the same SEPA layer applies.
Offer SEPA bank transfer at checkout next to cards and wallets. For higher-ticket orders, SEPA often clears at a cost cards cannot match.
Collect monthly fees against a stored SEPA mandate. R-message retries and account updater logic recover most temporary failures automatically.
Pay sellers out instantly on SCT Inst, run treasury sweeps on standard SCT, and keep one reconciled ledger across both.
High-ticket bookings settle over SEPA bank transfer at low cost, with instant refunds on cancellation through SEPA instant.
Replace card-on-file collection with SEPA mandates for recurring B2B billing — better economics, fewer disputes.
Resell SEPA capacity to your own merchants from one connection, with white-labelled reconciliation and a stable scheme-level API.
Trust & compliance
Moving euros under SEPA rules involves more than the scheme itself. The platform sits inside the relevant compliance frameworks so your team does not have to assemble them piece by piece.
Strong Customer Authentication and 3DS2 apply per payment where the SEPA region requires them, so card legs and account-to-account legs both stay compliant.
Where SEPA sits next to cards, raw card numbers never touch your stack — they are vaulted and tokenised on capture.
Payer data is processed under EU rules, with residency options for merchants that need them.
Scheme participation follows the European Payments Council rulebooks for SCT, SCT Inst, SDD Core and SDD B2B.
Together, these frameworks cover the bulk of what a finance, risk or compliance reviewer asks about when they hear "payment SEPA": who holds the data, where it sits, who authenticated the payer, and how the scheme rulebooks are followed. The honest answer for every one of those is inside the platform.
Common questions
SEPA — the Single Euro Payments Area — is the bank-to-bank framework that lets euro payments move between accounts across Europe under one common set of rules. A SEPA payment is any euro transfer initiated under those rules, whether a one-off SEPA credit transfer, a SEPA instant payments transfer, or a SEPA direct debit collected under a SEPA mandate. With topropay, every variant runs through the same API.
The SEPA zone covers all 27 EU member states plus EEA countries (Iceland, Norway, Liechtenstein), the United Kingdom, Switzerland, Monaco, San Marino, Andorra and Vatican City — 36 SEPA zone countries in total at the time of writing. A payer with an IBAN issued in any of these markets can send or receive a SEPA transfer through the platform.
SEPA credit transfer (SCT) is the standard batched euro payment, settled the next bank business day with no scheme-wide per-payment cap. SEPA instant payments (SCT Inst) settle in under ten seconds, 24/7/365, with a current scheme ceiling of €100,000 per transaction. The platform picks the right rail automatically based on the payer's SEPA bank reachability and your policy.
A SEPA mandate is the authorisation a payer gives you to debit their SEPA account by direct debit. It can be signed on paper or electronically and is then stored against that payer for every future collection. The platform vaults mandates, tracks their unique mandate reference and amendment history, and submits them with every SEPA direct debit instruction so the payer's bank can validate the collection.
Yes — every SEPA payment relies on the IBAN identifier. To accept a SEPA bank transfer you provide your collection IBAN; to send one, the payer's IBAN goes into the request. The platform validates each IBAN SEPA structurally and at the check-digit before the message leaves your servers, so malformed payments are caught before they reach the scheme.
Yes. The routing engine treats a SEPA bank transfer as one route among many. You can offer SEPA next to Visa, Mastercard, Apple Pay, Google Pay and local methods, and let policy decide which to lead with by market, ticket size or currency. The same integration powers all of them.
Settlements, fees and adjustments from every rail — SEPA included — are normalised into one ledger regardless of which bank or scheme handled the payment. You export one consistent dataset to your ERP rather than merging a file per provider, which is usually the slowest part of running SEPA at scale.
Coverage of SEPA instant is expanding rapidly under the EU Instant Payments Regulation, which requires euro-area banks to send and receive instant credit transfers. If a payer's bank is not yet on the SCT Inst scheme, the platform automatically routes the SEPA transfer over standard SCT instead — your integration does not change.
SEPA is a euro-only scheme: a SEPA account, by definition, sends and receives in euro. For pound, dollar and other currency flows, the platform routes through the right local rail — Faster Payments in the UK, ACH in the US, and equivalent schemes elsewhere — under the same API.
It is built for scale. Mandate handling, R-message normalisation, rail selection and reconciliation are designed for merchants and payment service providers processing serious euro volume across many banks and SEPA zone countries. PSPs can resell the SEPA layer to their own customers from the same integration.
Book a discovery call. We map your euro flows today, score where SEPA instant or a mandate-based collection would unlock cost and speed, and scope a single-API rollout across the SEPA zone countries you sell into. No scheme rebuild, no per-country provider.