Today, a euro bank transfer can still take hours or wait until the next working day. The EU’s Instant Payments Regulation will require affected providers in EU countries outside the euro area to offer an instant option. The recipient must usually receive the money within ten seconds, at any time of day. The regulation itself and the ECB’s summary set out these requirements.

For customers, this appears to be a faster bank transfer. For the provider, every system involved must work within seconds, including the banking app, account balance, currency conversion, fraud checks and payment records. A delay or lost response could leave the customer unsure whether the payment succeeded or cause the same payment to be sent twice.

Which providers are affected?

The rules do not apply to every financial company. They apply to providers located in an EU country outside the euro area that already allow customers to send and receive ordinary euro transfers from payment accounts.

This includes:

• Banks, legally called credit institutions, including commercial, savings and cooperative banks. They must receive instant euro payments from 9 January 2027 and send them from 9 July 2027.
  
• Payment institutions, meaning licensed non-bank companies that provide payment accounts and euro transfers. They must receive instant payments from 9 April 2027 and send them from 9 July 2027.
  
• Electronic money institutions, including certain digital wallet and fintech account providers. The same April and July deadlines apply when they offer ordinary euro transfers from customer payment accounts.

A money-transfer company that does not provide customer payment accounts is not covered by this particular requirement. The European Commission confirms these distinctions, including the treatment of savings banks, cooperative banks, payment institutions, electronic money institutions and remittance-only firms, in its implementation Q&A.

A UK-only provider is not directly covered. However, an EU subsidiary can be covered, and an EU branch follows the deadlines of the country where that branch is located. UK systems supporting such an entity may therefore still require development work.

What else changes in 2027?

Payment speed is only one part of the regulation.

Instant transfers cannot cost more than equivalent standard euro transfers. Providers must also make them available through the same channels customers already use for standard transfers, such as mobile banking, online banking, business platforms and branches.

From 9 July 2027, providers outside the euro area must also check whether the recipient’s name matches the account number before a customer confirms a euro transfer. This Verification of Payee service applies to both standard and instant euro transfers and must be free to the payer.

Providers offering instant euro transfers must also check their customers against relevant EU financial sanctions lists at least once a day and whenever the list changes. This is a separate process from checking each individual payment.

Why the payment connection is not enough

A provider may already have selected a payment processor or settlement service. That connection carries payment messages between institutions, but it does not update the customer’s account, perform currency conversion or create the provider’s financial records.

Older account systems often process some work in scheduled batches. That becomes a problem when an incoming payment arrives overnight and the recipient must have access to the money within seconds.

Accounts held in another currency add further work. For example, a customer may receive a euro payment into an account held in Czech koruna or Polish złoty. The provider cannot reject the payment simply because its usual currency-conversion service is closed. It needs a way to convert and credit the payment outside normal market hours.

The receiving process must therefore connect the payment message with the customer account, currency service, available balance, accounting records and confirmation sent back to the payer.

Sending creates more points of failure

An outgoing instant payment passes through several checks before it reaches the recipient. The provider may need to confirm that the account exists, that enough money is available and that the payment is within the customer’s limits. It may also run fraud checks and convert the amount into euros.

These steps must complete quickly enough for the recipient to receive the money within ten seconds. A system that waits several seconds before retrying a failed request can use most of the available time before the payment even reaches the external network.

Providers must also let customers set a daily or per-payment limit specifically for instant transfers. The limit must apply across all available payment channels and changes must take effect immediately.

Payment results must remain clear

A failed message does not always mean that the payment failed.

The money may have reached the recipient even if the confirmation never returned to the customer’s app. If the customer sees an error and tries again, the same payment could be sent twice.

Every payment therefore needs a consistent identifier and status across the customer channel, payment service, processor connection and accounting system. The provider must distinguish between a rejected payment, a timed-out request and a payment whose final result is still being checked.

The same information is needed for reconciliation. Overall daily totals may appear correct while an individual payment is duplicated, missing from the ledger or recorded under the wrong status. Operations teams need to follow one payment through every system without searching several unrelated logs.

Instant payments require continuous support

Instant payments operate throughout the day, including weekends and public holidays. Systems cannot rely on a routine overnight shutdown for processing, maintenance or releases.

Technical monitoring must show more than whether servers are running. Teams need to see how long payments take, where delays occur, which payments have uncertain statuses and whether the customer balance agrees with the financial records.

Support teams also need enough information to answer a customer who reports a missing or duplicated payment. Clear payment identifiers, timestamps and status histories make that possible.

What UK providers need to check

The EU regulation does not directly require a UK-only provider to offer instant euro payments. Being part of the wider SEPA area does not by itself bring a UK institution within the EU regulation.

However, UK groups may operate an EU-authorised subsidiary or branch that is covered. The European Commission explains that a branch follows the deadline for the country where it is located.

An affected EU entity may depend on systems or teams based in the UK, including payment platforms, fraud services, customer databases, account integrations and operational support. Those shared services must be able to meet the EU entity’s requirements.

UK technology suppliers may face similar requests from EU clients. A client may require faster processing, payment-level monitoring, clear recovery procedures and continuous support even though the supplier itself is not directly regulated.

What should be tested before launch?

Connecting successfully to the payment network is not enough.

Providers should test what happens when:

1. A euro payment arrives overnight for an account held in another currency.
   
2. The recipient receives the money but the confirmation does not reach the sender.
   
3. A customer or system submits the same payment twice.
   
4. The name and account check returns a partial match, no match or no answer.
   
5. A fraud or account system responds too slowly.
   
6. The payment succeeds but the customer balance or accounting record is not updated.

Each test should confirm what the customer sees, whether the financial records are correct and how the operations team can resolve the problem.

Where Blocshop fits

Payment providers may already have selected their payment processor and overall architecture but lack enough experienced developers to complete every system change alongside existing projects.

Blocshop can add one to three senior developers to take responsibility for a defined part of the implementation. This could include a payment or Verification of Payee API, an integration with an account platform, real-time balance updates, reconciliation data, production tests or payment monitoring.

The client retains control of architecture, risk and release decisions. Blocshop’s developers work within the existing team and carry the agreed work through development, integration testing and handover.

This approach reflects Blocshop’s work supporting Erste Bank’s internal digital-banking team and building open-banking connections and financial-data logic for Asora.

If your payment connection is already planned but work remains across customer channels, account systems, currency conversion or reconciliation, book a consultation with Blocshop to identify a production workstream our senior developers can take on.