SEPA Instant Payments Regulation: phased obligations from 2025

The SEPA Instant Payments Regulation, Regulation (EU) 2024/886, made instant euro payments mandatory across the euro area in phases, not on a single date. Payment service providers in the euro area had to be able to receive instant payments from 9 January 2025 and to be able to send them from 9 October 2025. Verification of payee became required from October 2025, and payment service providers in EU member states outside the euro area follow later dates in 2027, with receiving required from 9 January 2027 and sending from 9 July 2027. Before the regulation, SCT Inst was an optional scheme, and only about half of European payment service providers had joined. The regulation changed that. Instant payments are now a standard service, not a premium option. The phased dates matter because they define the compliance deadlines, and an analyst must be able to state them. For a bank in the euro area, the receive obligation came first, on 9 January 2025, so a bank had to be able to accept an instant payment from any other euro area bank from that date. The send obligation followed on 9 October 2025, so the same bank had to be able to send an instant payment from that date. Verification of payee became mandatory from October 2025, at the same time as the send obligation. For a bank in an EU member state outside the euro area, such as Sweden or Poland, the dates are later: receive from 9 January 2027 and send from 9 July 2027. The analyst must confirm which dates apply to their bank, because a euro area bank and a non euro area bank in the same group have different deadlines. The regulation also introduced verification of payee. Since October 2025, before sending an instant payment, the sending bank must check that the name the customer entered matches the name on the beneficiary account, and warn the customer if there is a mismatch. This is the European equivalent of the UK confirmation of payee service, and it is designed to reduce fraud, particularly authorised push payment fraud where a customer is tricked into sending money to a fraudster. The check must happen before the payment is sent, because an instant payment cannot be recalled once it has been executed. The response is one of three: a match, a close match where the correct name is shown, or no match. The analyst must design the user experience for each, and must record the result with the payment. The regulation caps the price of an instant payment at the price of a regular credit transfer. A bank cannot charge more for an instant payment than it charges for a standard SEPA credit transfer. This removes the price barrier that had slowed adoption, and it means customers can choose instant payments without paying extra. The regulation also requires that instant payments be available 24 hours a day, 7 days a week, 365 days a year, with a maximum execution time of 10 seconds. The analyst must confirm the pricing with the product team: if the standard credit transfer is free for a retail customer, the instant payment must also be free, and the product must not present instant as a paid upgrade. Sanctions screening changed under the regulation, and the analyst must understand the change. Before the regulation, many banks screened every instant payment against the sanctions lists before sending it, which was difficult inside a ten second budget. The regulation moved sanctions screening to a daily check against the sanctions lists, because a per payment check cannot fit inside ten seconds. The bank checks its customer base against the lists at least once a day, and relies on that check rather than a per payment screen. The analyst must confirm the sanctions approach with compliance: the daily list check replaces the per payment check only where the regulation allows it, and the payment must still be screened against the lists that apply, including any real time screening the bank chooses to keep for high risk payments. The operational impact is the part that catches banks by surprise. Instant payments run 24 hours a day, 7 days a week, 365 days a year, which means exception handling, reconciliation and customer support must all work outside business hours. A payment that fails at 2am on a Sunday needs the same handling as one that fails at 2pm on a Tuesday: the customer must be told, the reason code must be recorded, and the reconciliation must match the pacs.008 against its pacs.002 within seconds. A bank that staffs its operations only on business days will discover on the first Sunday that its instant payments have no one watching them. The analyst must design the 24 hour operations model with the operations team, including the alerting, the on call rota and the automated handling for the common failures. The 10 second execution time is a hard requirement, not a target. The regulation requires that an instant payment be executed within 10 seconds, and the 2025 scheme rulebook sets the same 10 second maximum. A bank that regularly takes 20 seconds is outside both the scheme limit and the regulation, and the analyst should treat 10 seconds as the design budget. The budget breaks down across fraud screening, sanctions screening, the funds check, verification of payee, the pacs.008 transit, the payee bank credit and the pacs.002 return. Each part needs a latency budget and monitoring, and the analyst should specify the alert threshold for each part, so a slow fraud screen is caught before it becomes a slow payment. For a business analyst, the IPR creates specific requirements. Your payment initiation flow must include a verification of payee step, with a clear user experience for match, close match, and no match results. Your pricing must comply with the cap. Your operations must handle instant payments around the clock, including at weekends and on holidays, which means your exception handling, your reconciliation, and your customer support must all work outside business hours. And your testing must cover the full instant payment lifecycle, from verification of payee through to settlement in 10 seconds. The testing must include the failure cases: a no match on verification of payee, a timeout with no pacs.002, a reject with AC04, and a recall with camt.056 and camt.029, all at 2am on a Sunday, because that is when the system will be tested in production.