SEPA QR codes and instant payments — the code names the payment, not the speed

Two rails, one code

A SEPA credit transfer can travel on two rails:

	SCT (classic)	SCT Inst (instant)
Settlement	Typically the next business day	Under 10 seconds
Availability	Banking days	24/7/365
Amount limit	None from the scheme	Set by the payer's bank
Finality	Same — irrevocable once settled	Same — irrevocable once settled

An EPC QR code describes the payment — beneficiary, IBAN, amount, reference. Line 4 of the payload is always SCT, and there is no field anywhere in the format that selects the rail. When the payer confirms the prefilled transfer, their bank decides (or their app lets them choose) whether it goes classic or instant. The code cannot force it, and no QR generator can honestly promise "instant" on your behalf.

What changed with the Instant Payments Regulation

For most of SEPA's history, instant transfers were an optional, often surcharged extra — many banks did not offer them at all, and the original scheme capped them at €100,000.

The EU's Instant Payments Regulation, adopted in 2024, changed the defaults for euro-area payment service providers: by January 2025 they had to be able to receive instant euro transfers, by October 2025 to send them, and instant transfers may not be priced higher than ordinary credit transfers. The regulation also removed the old scheme-level cap, leaving limits to individual banks, and required providers to verify that the payee name matches the IBAN before sending.

The practical consequence for QR payments: a scanned Girocode now usually can settle in seconds at no extra cost, across the euro area — something that was bank-lottery before.

Why this matters for your invoice or counter

Instant settlement changes what an EPC code is good for:

• Invoices — a customer can scan the code on your invoice and you see the money before the phone is back in their pocket. "Payment on receipt" becomes literal.
• Point of sale and trades — a plumber or market seller can accept an account-to-account payment and verify arrival before handing over goods, which classic SCT's next-day settlement never allowed. This is the model UPI and PIX proved at scale; SEPA now has the rails for it.
• Deposits and handovers — anywhere you currently wait for a transfer to clear.

The honest caveats: the payer's app controls the experience, some banks still route to classic SCT by default or apply conservative instant limits, and an instant payment is instantly irrevocable — there is no card-style chargeback, so the payee name shown at confirmation is the payer's one real check. None of this is visible in, or fixable by, the QR code.

Building the code

Nothing about instant payments changes the payload. Generate a standard EPC code with the EPC builder — name, validated IBAN, amount, one reference — keep it under 331 bytes, and test-scan it with a banking app before it ships. The speed comes from the rails, which is exactly as it should be: formats age badly when they encode assumptions about infrastructure.

FAQ

Does an EPC QR code trigger an instant payment?

It triggers a SEPA credit transfer; the payer's bank determines whether it travels as an instant (SCT Inst) or classic (SCT) transfer. The payload has no field for speed — line 4 is always simply SCT.

How fast is a SEPA Instant payment?

The scheme requires end-to-end settlement in under ten seconds, at any time of day, every day of the year. Classic SEPA transfers typically settle the next business day.

Do banks charge extra for instant transfers?

Under the EU Instant Payments Regulation, euro-area providers may not price instant euro transfers above ordinary credit transfers. Before the regulation took effect in 2025, surcharges were common.

Can an instant payment be reversed if I scanned a fraudulent code?

No — instant settlement means instant finality. Recovery depends on the banks' goodwill and fraud procedures. Check the beneficiary name your app displays before confirming; that confirmation screen is the real defence.