SEPA payments
Eurozone collections and payouts depend on standardised mandates, batch files and return handling. SEPA payments support SDD and SCT flows, with Cardflo standardising mandate storage and batch submission across a single gateway configuration.
- Category
- Methods
- Capabilities
- 6
- Available on
- All plans
Pan-European subscription models and B2B platforms rely on standardised bank transfers to collect funds and disburse payouts across the Eurozone. Managing cross-border direct debit mandates, handling batch XML files and resolving return codes creates operational overhead for finance teams targeting multi-market expansion without relying entirely on card schemes.
Cardflo integrates operators with a regulated acquirer partner network to route standard SEPA payments uniformly. The orchestration layer standardises mandate storage and handles batch submission routing, allowing merchants to consolidate European banking flows through one gateway configuration while reducing manual reconciliation tasks.
Adding a new local method or wallet is a configuration change, not a rebuild, so you can launch in a new market without a fresh integration project. Settlement, reporting and reconciliation stay unified across every method.
SEPA payments overview
Operating across the thirty-six countries of the Single Euro Payments Area demands a unified approach to euro-denominated collections and disbursements. Merchants using standard transfer schemes require precise orchestration to handle the specific ISO 20022 XML messaging formats, manage complex mandate lifecycles for recurring billing, and route batch files accurately.
Cardflo provides gateway infrastructure to automate SEPA Direct Debit pulls and SEPA Credit Transfer pushes through regulated acquirer partners. This environment focuses exclusively on traditional batch clearing mechanisms, while operators seeking immediate clearing times should explore the SEPA-instant page, and those requiring API-initiated flows can review the open banking payments guide.
By routing standard SEPA payments through a single integration, the orchestration platform allows finance teams to control collection schedules, handle R-transactions systematically, and deploy unified euro settlement workflows without maintaining direct connections to multiple regional financial institutions.
How SEPA payments works
Digital mandate capture and storage
Merchants present a compliant digital mandate form during onboarding or checkout to capture the consumer's International Bank Account Number alongside authorisation details. Cardflo tokenises this sensitive information and stores the reference within the orchestration layer. This ensures that all subsequent recurring billing cycles reference the correct creditor identifier and mandate signature when routed to the chosen acquirer partner.
Batch processing and routing
The platform aggregates individual transaction requests into compliant ISO 20022 XML batch files according to the operator's defined collection or payout schedule. Cardflo routes these batches to the appropriate acquirer partner based on the merchant's settlement preferences and geographical setup, triggering standard direct debit pulls or credit transfer pushes across the clearing network.
R-transaction handling and reconciliation
When a transaction cannot be completed, the destination bank returns a specific R-message, such as a refusal, return, or refund request. The orchestration platform maps these complex scheme codes into standardised statuses within the merchant dashboard. This allows automated logic to pause recurring subscriptions or trigger alternative collection workflows while generating unified reconciliation reports for the finance department.
Why SEPA payments matters
Lower payment processing costs
Standard SEPA transfers operate outside traditional card scheme structures, fundamentally reducing the interchange and processing fees associated with high-volume digital transactions. By routing these transactions through efficient acquirer partners, merchants can maintain stable margins on recurring subscription models and high-value invoice settlements without absorbing percentage-based card network costs across different Eurozone territories.
Reduced involuntary customer churn
Bank accounts do not expire or require physical replacement like credit and debit cards. Storing active direct debit mandates allows merchants to collect recurring payments reliably over years. This structural advantage protects revenue streams against the common failure points of lost cards or expired network tokens, maintaining uninterrupted service access for long-term subscribers and enterprise clients.
Regulatory notes for SEPA payments
SEPA mandate compliance and storage
European Payments Council rules dictate strict formatting and data requirements for direct debit mandates. Merchants must capture explicit authorisation containing the creditor identifier, mandate reference, and the payer's International Bank Account Number.
Failure to maintain compliant mandate text can render the collection invalid and expose the merchant to extended refund claims.
Cardflo assists merchants by storing tokenised mandate references securely within the orchestration environment.
While the merchant retains the responsibility for gathering the initial legal consent, the gateway ensures the correct mandate data is systematically injected into subsequent batch submissions routed to the acquirer partner network, maintaining scheme compliance.
Refund rights and risk management
Under the SEPA Core Direct Debit scheme, consumers hold a legal right to request a refund from their bank for up to eight weeks following a successful collection, without providing a reason.
In cases of unauthorised transactions where no valid mandate exists, this refund period extends to thirteen months, introducing significant chargeback risk for merchants.
Finance teams must configure their risk management workflows to account for these extended exposure windows. By routing transactions through Cardflo, operators can monitor return codes dynamically and implement automated suspension logic.
If an eight-week refund request occurs, the platform updates the transaction status, allowing the merchant to restrict service access immediately.
SEPA payments use cases
SaaS mandate collections
Merchants changing collection providers must preserve valid SEPA Direct Debit mandates, creditor identifiers and original mandate references without triggering unnecessary reauthorisation. Cardflo coordinates onboarding with its acquirer partners, maps mandate data to the required submission format and supports controlled migration of scheduled SDD collections.
Media subscription direct debits
Finance teams collecting euro invoices must distinguish SEPA Direct Debit Core from B2B because debtor eligibility, mandate verification and refund rights differ. Cardflo routes each collection to the appropriate SDD scheme through its acquirer partner network and maintains clear reporting for returns, rejects, reversals and refunds.
Euro supplier payment batches
Organisations paying large supplier runs across the SEPA area need SCT batch files validated against IBAN, execution date and remittance requirements before submission. Cardflo supports standard SEPA Credit Transfer workflows through its acquirer partners, consolidating payment statuses and reconciliation references for treasury and accounts payable teams.
Variable invoice collections
Property managers and commercial service providers collect variable euro invoices where amounts and due dates change between SDD submissions, requiring accurate pre-notification and mandate references. Cardflo supports scheduled collection files, mandate status tracking and exception reporting through its acquirer partners, helping finance teams reconcile unpaid, rejected and returned items.
SEPA payments by the numbers
This is the standard industry timeframe for 'no-questions-asked' refunds under the SEPA Core Direct Debit scheme for consumer protections.
Typical processing time for SEPA Instant Credit Transfers between participating financial institutions, assuming no technical delays or compliance flags.
Estimated range of savings when comparing SEPA Direct Debit fees to typical merchant account fees for mid-market credit card transactions.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with SEPA payments
- Routes batch SEPA Direct Debit submissions to the most appropriate acquirer partner based on merchant entity.
- Maintains active direct debit mandates securely to automate recurring subscription pulls across the Eurozone banking area.
- Standardises ISO 20022 XML formats for uniform processing of pan-European credit transfers and bulk disbursement files.
- Interprets and maps standard R-messages to automate failure handling for rejected, refused or returned euro transactions.
- Consolidates multi-country collection flows into a single settlement report to simplify reconciliation for enterprise finance teams.
- Enforces scheme-specific timing rules for initial and recurring direct debit collections to prevent late submission failures.
A short scoping call, then a written plan for your MIDs.
Questions about SEPA payments
What is the difference between SEPA Core and B2B Direct Debit?
The SEPA Core Direct Debit scheme allows merchants to collect funds from both consumers and businesses, but it includes a mandate refund right extending up to eight weeks.
The B2B scheme is strictly for business transactions and requires the payer's bank to verify the mandate before the first collection. This B2B structure entirely removes the refund right, providing absolute payment certainty for the merchant.
Cardflo routes both mandate types through regulated acquirer partners based on the specific merchant account configuration.
How long do standard SEPA payments take to settle?
Standard SEPA Credit Transfers typically clear within one processing day, assuming the instruction is routed to the acquirer partner before the daily scheme cut-off time.
Direct Debit collections operate on strict presentation timelines, requiring initial mandates to be submitted up to five days prior to the collection date, though recurring transactions often clear faster.
Finance teams can orchestrate exact submission schedules through the Cardflo gateway to ensure funds arrive in their settlement accounts on predictable timelines.
What is a SEPA creditor identifier and how is it used?
A Creditor Identifier is a unique reference that allows businesses to collect direct debits across the Eurozone independently of their specific banking institution. It standardises the identification of the merchant initiating the pull request.
When routing transactions via Cardflo, merchants configure their unique identifier within the orchestration platform. This reference is then automatically attached to every batch XML file submitted to the acquirer partner network, ensuring the consumer's bank recognises the collecting entity and validates the mandate accurately.
How does the platform handle SEPA R-transactions?
R-transactions encompass rejections, refusals, returns, refunds, reversals, and revocations generated during the clearing process. The clearing networks return specific ISO codes explaining the failure reason, such as insufficient funds or a revoked mandate.
The Cardflo orchestration engine intercepts these raw codes from the acquirer partner, standardises the reporting format, and displays the actionable status in the merchant dashboard.
Operators can then use this structured data to suspend user accounts automatically or trigger automated email sequences for alternative collection methods.
Related features.
Related guides.
See how Cardflo compares.
From the blog
A merchant acquirer is a licensed bank that holds your account, takes liability for transactions, and settles funds. The payment processor is the technology layer routing data between the checkout, card networks, and issuing banks. Every card payment requires both components to manage technical encryption and financial liability. They are often separate entities with distinct fee structures.
Read articleA merchant acquirer is a financial institution that processes card transactions and verifies funds. The payment gateway acts as the technological bridge, encrypting sensitive data between the website and the acquirer. Merchants need both components to ensure that electronic payments are accepted, authorised, and settled. Together, they create a seamless and secure payment experience for customers.
Read articleA merchant account is a specialised business account used to accept electronic payments like Apple Pay and Google Pay. It acts as a bridge between the business and the customer bank. Funds are held here for verification and compliance before being transferred to a main bank account. This process ensures that all transactions are secure and reduces the risk of fraud for the merchant and the customer.
Read articleReady to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.