Your complete guide to SEPA Instant

Traditionally, bank transfers have relied on batch processing, in which banks group payments and only send them at set times during business hours, on business days.

SEPA Instant operates on a real-time logic. Each transaction is sent immediately as an individual process.

This transition from batching to individual transaction-level processing is what enables the speed, but it also introduces a specific technical lifecycle that your business must manage to ensure a seamless checkout experience.

The technical lifecycle of an instant transfer

1. Initiation (the push): The customer authorises the payment via their banking app. We call this a ‘push’ payment because the customer is the one sending the money to you. Because they authorise it directly using their own bank’s security – like FaceID or a PIN – it’s highly secure by default.

2. The 10-second countdown: The moment the payment starts, a strict 10-second timer begins. Both the sending and receiving banks must confirm the transfer within this window.

   To keep this fast, banks no longer pause transfers to run manual security checks (like sanctions screening). As of 2026, they must run these checks on their databases daily in the background, ensuring nothing slows down the transaction.

3. Real-time notification: Once the banks agree, your system gets an immediate update. This is called a webhook, and it’s a real-time signal that turns your order status to ‘paid’. However, the availability of these instant alerts can vary by provider and specific bank account.
   While some banks are still rolling out real-time notifications across all IBANs, modern pay by bank infrastructure is built to deliver this confirmation instantly. That means you can release the goods or ship the order immediately, without waiting days for the funds to clear.

Possible outcomes of a SEPA Instant payment

In the SEPA Instant world, your backend and PSP webhook handling must be programmed to handle three distinct outcomes with specific logic for each:

• SUCCESS (paid): The funds have been safely deposited into your account. Unlike credit cards, there’s no pending state. You can trigger fulfilment, ship physical goods, or release digital licenses immediately.

• TIMEOUT: If the receiving bank does not respond within the 10-second window, the SEPA rail rejects the transaction. If a timeout occurs, the customer should be prompted to try again or use an alternative payment method.

• FAILURE: Failure reasons include insufficient funds, an expired reference, or a VoP mismatch if the name on the account doesn’t match the IBAN. Your system can use this data to provide a tailored message to the customer (e.g. ‘Please check your account balance’ instead of a generic ‘Payment failed’).

While banks vary in how much detail they share, your system can often receive enough data via API to trigger a helpful, automated response. Instead of a generic error message, you can send a more personalised follow-up, such as asking the customer to check their account balance or double-check the recipient's name.

Guaranteed payments and 24/7 availability

Because the network never sleeps, SEPA Instant transfers work just as fast on a Sunday evening or a public holiday as they do on a Tuesday morning.

Crucially, these payments are final. Once you receive payment confirmation, the funds are settled immediately. There’s no built-in chargeback mechanism, providing you with more payment certainty than cards or direct debits.