EU Instant Payments Regulation: The Compliance Timeline Every Operator Needs

The European Union’s Instant Payments Regulation (Regulation EU 2024/886, amending SEPA Credit Transfer regulations) is the most consequential structural change to euro payment infrastructure since the SEPA migration. Unlike previous payment regulations that primarily imposed consumer protections or licensing requirements, the IPR mandates operational change at every PSP in the eurozone — and in non-euro EU member states on a delayed schedule.

The core obligation is simple in principle: if you offer standard SEPA credit transfers, you must also offer SCT Inst (SEPA Instant Credit Transfer) at the same price or less. Instant cannot cost more than standard. And you must verify that the IBAN and account name match before sending. What looks simple in principle has substantial compliance complexity for PSPs, embedded finance providers, and operators who have built payment workflows assuming standard SEPA transfer economics.

What SCT Inst Is and Why It Matters

SCT Inst is the SEPA Instant Credit Transfer scheme operated by the European Payments Council (EPC). It has existed since 2017 as an optional scheme — PSPs could choose to participate or not. Participation was uneven: as of late 2023, approximately 65% of EU PSPs offered SCT Inst in some form, but coverage was patchy enough that an operator sending to a random EU bank account had no guarantee the recipient could receive an instant transfer.

The practical consequence was that the real-time rail existed but couldn’t be relied upon. Operators still had to use standard SEPA credit transfers (SCT, 1-business-day clearing) as the baseline, falling back to instant only when they knew both sender and recipient PSPs supported it.

The IPR eliminates this optionality. SCT Inst becomes mandatory for all euro PSPs, with a phased timeline based on geography and PSP type.

The Compliance Timeline

The IPR was published in the Official Journal of the EU on March 19, 2024, and entered into force 20 days later. The compliance obligations are staggered:

Phase 1 — Receive (Eurozone PSPs): PSPs in eurozone member states must be able to receive SCT Inst transactions by January 9, 2025. This means accepting inbound instant transfers is already required for most EU banks and payment institutions.

Phase 2 — Send (Eurozone PSPs) + Pricing Parity: PSPs in eurozone member states must be able to send SCT Inst and must apply pricing parity (instant ≤ standard) by October 9, 2025.

Phase 3 — Non-Euro EU Member States (Receive): PSPs in non-euro EU member states (Sweden, Poland, Hungary, Czech Republic, Romania, Bulgaria, Denmark) must be able to receive SCT Inst by July 9, 2027.

Phase 4 — Non-Euro EU Member States (Send + Pricing Parity): Send capability and pricing parity for non-euro EU PSPs by January 9, 2028.

Verification of Payee: The IBAN/name verification requirement (see below) applies from October 9, 2025 for eurozone PSPs.

For operators in the UK, note that the IPR does not apply to UK-regulated entities (post-Brexit). The UK’s equivalent initiative — the Pay.UK New Payments Architecture and the Financial Conduct Authority’s work on Faster Payments expansion — is on a separate, less mandated trajectory.

Pricing Parity: What It Actually Means

The pricing parity requirement prohibits PSPs from charging more for SCT Inst than for standard SCT. This is a direct attack on the fee premium that many PSPs had built into instant transfer pricing.

The practical impact depends on how your cost model is structured:

If you charge a flat per-transfer fee (e.g., €0.20 per standard SEPA, €0.40 per instant): You must either reduce instant pricing to match standard, or reduce standard pricing to provide room. You cannot maintain a premium for instant.

If you charge on a value basis (e.g., 0.1% of transfer value): You must apply the same rate to both instant and standard transfers.

If you are a PSP embedding euro transfers into a product (BaaS, embedded finance, platform): Your underlying banking partner’s pricing must comply, and you cannot pass through a differential cost to end users that results in instant costing more.

The regulation does not mandate that instant must be zero-cost — only that it cannot cost more than standard. If a PSP charges €0 for standard SCT, they must also charge €0 for SCT Inst. If they charge €0.15 for standard, they can charge up to €0.15 for instant.

What operators should model: If your business processes large numbers of euro credit transfers and you have been paying a premium for instant settlement, that premium disappears after October 2025. This directly reduces your cost of funds for time-sensitive payment flows. If you have been using standard SEPA (accepting the 1-day delay) to avoid instant premium costs, you can now default to instant at no additional cost — improving your customer-facing settlement speed.

Verification of Payee (IBAN/Name Check)

The IPR introduces a mandatory Verification of Payee requirement: before sending an SCT Inst transfer, the sending PSP must verify that the account holder name associated with the destination IBAN matches the payee name provided by the sender. This check must be completed before the sender confirms the transaction.

The verification requirement applies to:

• All SCT Inst transactions sent by eurozone PSPs (from October 9, 2025)
• Eventually, standard SCT transactions as well (timing TBD by implementing legislation)

The match result must be communicated to the payer in one of three ways:

1. Match: The name matches — proceed normally
2. Close match / Partial match: The name is similar but not identical — the payer is notified and must confirm
3. No match: The name does not match — the payer is notified; the payer can override but the mismatch is logged

The purpose is fraud reduction, specifically Authorized Push Payment (APP) fraud where victims are manipulated into sending payments to attacker-controlled accounts. By requiring name verification, the IPR aims to surface mismatches at the pre-send stage rather than post-fraud.

Verification of Payee: Implementation Implications

For operators initiating euro instant transfers on behalf of customers or counterparties:

You must collect the payee name. If your transfer initiation flow currently only collects IBAN, you need to add a name field. Many B2B payment flows, especially automated invoice payment systems, only store beneficiary IBANs — adding name collection requires workflow changes across the payment initiation chain.

You must handle mismatch responses. Your integration with your banking partner or PSP needs to handle three verification states: match, partial match, and no match. For automated payment runs (payroll, mass disbursements), you need a workflow for partial/no match cases — typically a hold-for-review queue rather than automatic processing.

Data quality matters. “Partial match” outcomes increase with poor-quality payee name data: abbreviations (“IBM” vs “International Business Machines”), trading names vs legal names, or stale name data for accounts that have changed ownership. Operators running large beneficiary databases should audit name data quality before the October 2025 deadline.

Cross-border VoP: The Verification of Payee service is implemented at the PSP level — each PSP maintains a directory or API for name lookup. For transfers between PSPs in different EU member states, the EPC is developing a pan-European VoP interoperability framework, but as of Q2 2025, VoP is primarily reliable for domestic transfers within a country and increasingly for intra-eurozone transfers at major PSPs. Operators should not assume VoP is available for all cross-border EUR transfers.

PSP Access to SCT Inst: Infrastructure Requirements

Participation in SCT Inst requires PSPs to be reachable 24/7. The SCT Inst scheme rules require:

• Continuous availability (no maintenance windows that interrupt instant transfer processing)
• Connection to at least one clearing and settlement mechanism (CSM) that processes SCT Inst — major CSMs include EBA CLEARING (RT1), STET (France), and TIPS (operated by the ECB)
• Maximum transaction processing time: the 2025 SCT Inst rulebook (effective October 5, 2025) specifies execution within 5 seconds, CSM response within 7 seconds, and final confirmation within 9 seconds end-to-end

For smaller PSPs or BaaS providers that previously relied on standard SEPA processing infrastructure with defined operating hours, these technical requirements are significant. The operational uplift — 24/7 operations, monitoring, incident response — is a recurring cost that doesn’t appear in per-transaction pricing but must be accounted for in the compliance business case.

For operators who are not PSPs themselves (merchants, platforms, marketplaces accessing euro payments via a licensed PSP partner), the requirement falls on the PSP. But the downstream effect is felt in the settlement timeline: operators who have built cash-flow models assuming T+1 SEPA settlement will find that their PSP now provides T+instant settlement, which changes the float dynamics.

Sanctions Screening: The 24/7 Challenge

One compliance challenge the IPR creates that is less discussed is the interaction with sanctions screening requirements. Under Regulation (EU) 2023/1113 (the revised Funds Transfer Regulation, which replaced the earlier 2015/847 regulation and is aligned with FATF Recommendation 16), PSPs must screen AML and sanctions checks before processing transfers.

For standard SEPA transfers, this was manageable: the 1-day processing window gave compliance teams time to run sanctions checks and resolve flags before settlement. For instant transfers completing in 10 seconds, the same checks must complete in near-real-time.

The practical requirement is automated, API-based sanctions screening against EU, OFAC, and UN sanctions lists, with no manual review in the critical path. PSPs that relied on batch overnight sanctions checks must rebuild this infrastructure before October 2025 for full send-capability compliance.

For operators, the implication is that your PSP’s sanctions screening architecture determines whether instant payments can genuinely process at speed or whether there are silent delays imposed by compliance workflows. Ask your PSP specifically how sanctions screening is handled for SCT Inst — a PSP that claims SCT Inst compliance but imposes 2-4 hour review windows for certain transfer patterns is not delivering genuine instant payments.

What This Means for Operators

The IPR changes the euro payment cost structure for every operator processing significant EUR volumes. Key actions before October 2025:

1. Audit your euro transfer fee structure. If you’re paying a premium for SCT Inst, that premium is illegal after October 2025. Renegotiate your PSP agreement or switch to a PSP that has repriced ahead of the deadline.

2. Update transfer initiation flows to collect payee name. Every euro transfer initiation flow must capture a beneficiary name. This applies to manual user-initiated transfers and to automated payment runs.

3. Build Verification of Payee response handling. Integrate VoP responses (match/partial/no match) into your payment workflow. Define what happens at each outcome — especially the partial match case.

4. Reassess settlement timing assumptions. If you’ve built liquidity models around T+1 SEPA settlement, the move to near-instant settlement changes your float position. This is generally positive but requires model updates.

5. Confirm PSP compliance status. Ask your euro PSP for written confirmation of their IPR compliance timeline — specifically for send capability and VoP integration. Some smaller PSPs were not compliant with the January 2025 receive deadline; the October 2025 send deadline is higher-stakes.

The IPR represents the EU completing the SEPA project’s original ambition: a genuinely unified euro payment area where instant transfers are the standard, not the premium option. For operators who have been routing around instant payments due to cost or availability concerns, that friction largely disappears by end of 2025.