SEPA Inst / Learning brief
SEPA Instant R-Message flows
Your notes
In simple terms / 01
What this means in plain language
Maps the main SEPA Instant exception flows, including pacs.002 rejections, camt.056 recall requests, and pacs.004 returns.
SEPA Instant processing includes more than the successful transfer path. Exception messages explain what happened when an instruction could not proceed or when a completed payment needs corrective action. A pacs.002 can report a rejected or otherwise unsuccessful status, a camt.056 can request that funds be recalled, and a pacs.004 can carry a return. These messages serve different purposes and occur at different stages. Operations teams should link each response to the original payment, preserve reason codes, and avoid treating a recall request as a guaranteed refund.
Complete lesson / 02
Understand the full idea, step by step
In a classic transfer, most trouble is dealt with afterwards: the payment settles, and any problem becomes a return or a recall the next day. Instant payments do not have an afterwards to lean on. When everything must finish in seconds and stay all-or-nothing, the exception paths look different — and the biggest one is a payment that fails simply because no answer came back in time.
The instant exception paths
- Timeout
- No answer inside the window — payment fails, reservation released
- Beneficiary reject
- Nordbank answers negatively — pacs.002 RJCT
- Refused recall
- Payer asks back after finality — camt.056, may be declined
- Common thread
- All-or-nothing: value never moves halfway
- Who investigates patterns
- Maya's operations team at Bank Alfa
All-or-nothing changes what an exception means
Because funds are reserved and not finally debited until the beneficiary side confirms, an instant payment that fails before finality needs no return — there was never a settled amount to send back. The reservation is simply released and Riya is whole. That is why a timeout — silence past the scheme's time limit — is a clean failure, not a stuck payment. Only once a payment is final does recovering it require the same consent-based route as any completed transfer: a recall the other side may refuse.
| Timeout | Beneficiary reject | Refused recall | |
|---|---|---|---|
| What triggers it | No answer in the window | Nordbank answers no | Payer regrets a final payment |
| When | Before finality | Before finality | After finality |
| Message | Timeout handling | pacs.002 RJCT | camt.056 recall request |
| Did value move? | No | No | Yes — payment was final |
| Effect on payer | Reservation released | Reservation released | Money back only if consent given |
WHAT IF — No answer arrives from Nordbank inside the scheme's time limit
What happens: The payment fails as a timeout. No value moved; once Bank Alfa has confirmed nothing settled late, the reservation on Riya's account is released.
How it is handled: Riya is told promptly and can try again. The deliberate double-check before releasing the reservation guards against a duplicate if a late answer were still in flight. Maya's team watches for repeated timeouts toward one bank — that is an operational signal about a route, not a customer to apologise to.
WHAT IF — Riya asks for a completed instant payment back
What happens: Because the payment reached finality, it cannot simply be reversed. Bank Alfa sends a camt.056 recall request, and the money returns only if Arjun's side consents.
How it is handled: The recall is a request against the beneficiary, exactly as in classic SEPA. If Arjun does not consent or the funds are gone, the recall is refused and the original payment stands. Riya is told honestly that recovery was requested, not guaranteed — finality is the price of instant availability.
Read the steps as text
- 01MessageThe debtor initiates an instant paymentDebtor (payer) → Bank Alfa (debtor agent)
The customer pays from an app or channel. From this moment the scheme's clock is running — the whole journey must finish within the scheme's time limit.
- 02ProcessingBank Alfa validates in real timeBank Alfa (debtor agent)
Format checks, balance check, and sanctions screening all happen in seconds. Anything slow here burns the scheme's time budget.
Screening checkpoint: Real-time transaction screening — Instant rails force screening to be fast and highly automated — there is no batch window to hide latency in.
- 03PostingThe debtor's funds are reservedBank Alfa (debtor agent)
Bank Alfa earmarks the amount. The final debit is confirmed only when the beneficiary bank accepts — instant payments are all-or-nothing.
- RESERVE Debtor's current account at Bank Alfa — EUR 480.00
- 04MessageThe transfer goes to the instant CSMBank Alfa (debtor agent) → Instant CSM (e.g. TIPS-style) · pacs.008
A pacs.008 flagged for the instant scheme is sent to the CSM, which immediately pushes it onward.
- 05 · EXCEPTION PATHProcessingThe CSM treats the payment as failedInstant CSM (e.g. TIPS-style)
Instant schemes are all-or-nothing: with no positive answer in time, the transfer must not settle. An unanswered payment is resolved as a failure, never left hanging.
- 06 · EXCEPTION PATHMessageBank Alfa receives a negative statusInstant CSM (e.g. TIPS-style) → Bank Alfa (debtor agent) · pacs.002
The rejection carries a timeout reason so operations can distinguish a slow participant from a business refusal.
- 07 · EXCEPTION PATHPostingThe reservation is releasedBank Alfa (debtor agent)
The debtor's money never left — the earmark is simply removed and the customer is told the payment failed.
- RELEASE Debtor's current account at Bank Alfa — EUR 480.00
- OUTCOME
- Funds
- Never left the debtor's account — the reservation was released.
- Settlement
- No settlement occurred; instant schemes settle only on a positive answer.
- Who acts next
- Instant CSM (e.g. TIPS-style) — The debtor may simply retry; operations monitors whether one participant times out repeatedly.
COMMON CONFUSION
“If an instant payment times out, the money is stuck somewhere between the banks until someone chases it.”
A timeout is a clean, all-or-nothing failure. Nothing settled, so nothing is stranded — the reservation is released after a confirming check and Riya can simply try again. The design's whole aim is that silence can never leave money half-moved.
STRICTLY SPEAKING
Strictly speaking, the exact time limit, the reason codes a rejection may carry, and the recall procedure and its timeframes are all set by the SCT Inst rulebook version in force. The message types mirror classic SEPA — pacs.002 for status, camt.056 for recall, pacs.004 for a return where one applies — but the timing that makes them all-or-nothing is instant-specific. Check the current rulebook before quoting any window.
FOR NOW, REMEMBER
- Instant exceptions come in three shapes: timeout (no answer), beneficiary reject (a firm no), and a refused recall after finality.
- Timeouts and rejects happen before finality, so no value moved — the reservation is released and the payment fails cleanly.
- A recall applies only after finality and is a request the beneficiary side can refuse, just as in classic SEPA.
- All-or-nothing is the through-line: an instant payment is never left half-moved.
TRY IT YOURSELF
Riya's EUR 240.00 instant transfer gets no answer from Nordbank within the scheme's window. Bank Alfa has confirmed nothing settled late. What is the correct treatment?
You have now walked the SEPA exception family across both classic and instant rails. The topic behind it pulls the R-transactions together — reject, return, recall, and their status messages — as one coherent system to master.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Rejection, recall, and return are distinct events.
- 02
Every exception must correlate to the original transfer.
- 03
A recall request does not ensure funds will come back.
Practical use cases / 04
Where you would use this
An operations analyst identifies whether a failed transfer needs repair or customer notification.
A developer maps pacs.002, camt.056, and pacs.004 into separate workflow states.
A service agent explains the difference between requesting and receiving a recall.
Worked example / 05
Put the idea into a real situation
Illustrative example: a sender reports that an instant transfer went to the wrong account. The originator PSP sends a camt.056 linked to the original transaction. The beneficiary side reviews the request and local conditions. If funds are returned, a pacs.004 carries the reversal value back through the route. The case remains open until a definitive response is received; sending the recall alone is not treated as resolution.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01MessageThe debtor initiates an instant paymentDebtor (payer) → Bank Alfa (debtor agent)
The customer pays from an app or channel. From this moment the scheme's clock is running — the whole journey must finish within the scheme's time limit.
- 02ProcessingBank Alfa validates in real timeBank Alfa (debtor agent)
Format checks, balance check, and sanctions screening all happen in seconds. Anything slow here burns the scheme's time budget.
Screening checkpoint: Real-time transaction screening — Instant rails force screening to be fast and highly automated — there is no batch window to hide latency in.
- 03PostingThe debtor's funds are reservedBank Alfa (debtor agent)
Bank Alfa earmarks the amount. The final debit is confirmed only when the beneficiary bank accepts — instant payments are all-or-nothing.
- RESERVE Debtor's current account at Bank Alfa — EUR 480.00
- 04MessageThe transfer goes to the instant CSMBank Alfa (debtor agent) → Instant CSM (e.g. TIPS-style) · pacs.008
A pacs.008 flagged for the instant scheme is sent to the CSM, which immediately pushes it onward.
- 05 · EXCEPTION PATHProcessingThe CSM treats the payment as failedInstant CSM (e.g. TIPS-style)
Instant schemes are all-or-nothing: with no positive answer in time, the transfer must not settle. An unanswered payment is resolved as a failure, never left hanging.
- 06 · EXCEPTION PATHMessageBank Alfa receives a negative statusInstant CSM (e.g. TIPS-style) → Bank Alfa (debtor agent) · pacs.002
The rejection carries a timeout reason so operations can distinguish a slow participant from a business refusal.
- 07 · EXCEPTION PATHPostingThe reservation is releasedBank Alfa (debtor agent)
The debtor's money never left — the earmark is simply removed and the customer is told the payment failed.
- RELEASE Debtor's current account at Bank Alfa — EUR 480.00
- OUTCOME
- Funds
- Never left the debtor's account — the reservation was released.
- Settlement
- No settlement occurred; instant schemes settle only on a positive answer.
- Who acts next
- Instant CSM (e.g. TIPS-style) — The debtor may simply retry; operations monitors whether one participant times out repeatedly.
Read the steps as text
- 01MessageThe debtor initiates an instant paymentDebtor (payer) → Bank Alfa (debtor agent)
The customer pays from an app or channel. From this moment the scheme's clock is running — the whole journey must finish within the scheme's time limit.
- 02ProcessingBank Alfa validates in real timeBank Alfa (debtor agent)
Format checks, balance check, and sanctions screening all happen in seconds. Anything slow here burns the scheme's time budget.
Screening checkpoint: Real-time transaction screening — Instant rails force screening to be fast and highly automated — there is no batch window to hide latency in.
- 03PostingThe debtor's funds are reservedBank Alfa (debtor agent)
Bank Alfa earmarks the amount. The final debit is confirmed only when the beneficiary bank accepts — instant payments are all-or-nothing.
- RESERVE Debtor's current account at Bank Alfa — EUR 480.00
- 04MessageThe transfer goes to the instant CSMBank Alfa (debtor agent) → Instant CSM (e.g. TIPS-style) · pacs.008
A pacs.008 flagged for the instant scheme is sent to the CSM, which immediately pushes it onward.
- 05MessageNordbank receives the transfer immediatelyInstant CSM (e.g. TIPS-style) → Nordbank (creditor agent) · pacs.008
The CSM forwards the payment in real time and waits for the beneficiary bank's answer.
- 06ProcessingNordbank decides — nowNordbank (creditor agent)
The creditor agent validates the account and screens the payment, then must answer positively or negatively within the scheme's window.
- 07 · EXCEPTION PATHMessageNordbank answers negativelyNordbank (creditor agent) → Instant CSM (e.g. TIPS-style) · pacs.002
The negative pacs.002 carries a reason code. Because it arrives before settlement, nothing has to be unwound.
- 08 · EXCEPTION PATHMessageThe rejection reaches Bank AlfaInstant CSM (e.g. TIPS-style) → Bank Alfa (debtor agent) · pacs.002
The CSM relays the answer within the same real-time window.
- 09 · EXCEPTION PATHPostingThe reservation is released and the debtor informedBank Alfa (debtor agent)
The customer sees the failure with its reason within seconds of paying.
- RELEASE Debtor's current account at Bank Alfa — EUR 480.00
- OUTCOME
- Funds
- Never left the debtor's account.
- Settlement
- No settlement — the rejection preceded it.
- Who acts next
- Nordbank (creditor agent) — The debtor checks the beneficiary details; the reason code says what was wrong.
Read the steps as text
- 01MessageThe debtor initiates an instant paymentDebtor (payer) → Bank Alfa (debtor agent)
The customer pays from an app or channel. From this moment the scheme's clock is running — the whole journey must finish within the scheme's time limit.
- 02ProcessingBank Alfa validates in real timeBank Alfa (debtor agent)
Format checks, balance check, and sanctions screening all happen in seconds. Anything slow here burns the scheme's time budget.
Screening checkpoint: Real-time transaction screening — Instant rails force screening to be fast and highly automated — there is no batch window to hide latency in.
- 03PostingThe debtor's funds are reservedBank Alfa (debtor agent)
Bank Alfa earmarks the amount. The final debit is confirmed only when the beneficiary bank accepts — instant payments are all-or-nothing.
- RESERVE Debtor's current account at Bank Alfa — EUR 480.00
- 04MessageThe transfer goes to the instant CSMBank Alfa (debtor agent) → Instant CSM (e.g. TIPS-style) · pacs.008
A pacs.008 flagged for the instant scheme is sent to the CSM, which immediately pushes it onward.
- 05MessageNordbank receives the transfer immediatelyInstant CSM (e.g. TIPS-style) → Nordbank (creditor agent) · pacs.008
The CSM forwards the payment in real time and waits for the beneficiary bank's answer.
- 06ProcessingNordbank decides — nowNordbank (creditor agent)
The creditor agent validates the account and screens the payment, then must answer positively or negatively within the scheme's window.
- 07MessageA positive status confirms acceptanceNordbank (creditor agent) → Instant CSM (e.g. TIPS-style) · pacs.002
The pacs.002 positive status is the trigger for settlement and for both customers' account movements.
- 08SettlementSettlement happens immediately from prefunded positionsBank Alfa (debtor agent) → Nordbank (creditor agent)
The CSM moves the amount between the banks' prefunded positions in central bank money the moment the positive answer arrives. There is no waiting for a cycle.
- DR Bank Alfa prefunded position — EUR 480.00
- CR Nordbank prefunded position — EUR 480.00
- 09PostingThe creditor is credited within secondsNordbank (creditor agent)
The beneficiary can use the money immediately. Bank Alfa converts the reservation into a final debit at the same moment.
- CR Creditor's current account at Nordbank — EUR 480.00
- 10 · EXCEPTION PATHMessageBank Alfa requests a recallBank Alfa (debtor agent) → Instant CSM (e.g. TIPS-style) · camt.056
The recall request references the settled instant payment. It is a request for cooperation, not a reversal instruction.
- 11 · EXCEPTION PATHMessageThe recall reaches NordbankInstant CSM (e.g. TIPS-style) → Nordbank (creditor agent) · camt.056
Nordbank must investigate and answer within the scheme's response window.
- 12 · EXCEPTION PATHProcessingThe beneficiary does not consentNordbank (creditor agent)
The beneficiary disputes the claim (or the funds are gone). Where consent or funds are missing, the recall fails.
- 13 · EXCEPTION PATHMessageA negative answer closes the recallNordbank (creditor agent) → Instant CSM (e.g. TIPS-style) · camt.029
The camt.029 resolution tells Bank Alfa the recall was refused and why. The money does not come back through the scheme.
- 14 · EXCEPTION PATHMessageBank Alfa receives the refusalInstant CSM (e.g. TIPS-style) → Bank Alfa (debtor agent) · camt.029
Operations closes the case in the scheme; anything further is a matter between the customers outside the payment system.
- OUTCOME
- Funds
- Remains with the beneficiary — the scheme cannot force it back.
- Settlement
- The original instant settlement stands; nothing was reversed.
- Who acts next
- Nordbank (creditor agent) — The debtor pursues the claim outside the scheme (directly or legally); the banks document the refusal.
Evidence & review / 07
Evidence & review
SEPA Instant Credit Transfer (SCT Inst) scheme in the euro area; exception handling.
What this brief simplifies: Presents three representative exception paths. Exact time limits, eligible reason codes, and recall timeframes are version-dependent and follow the current EPC rulebook; identifiers and the scenario are illustrative.
Sources for this brief4
- Scheme-specific rule2025 version 1.1 (EPC004-16)
2025 SEPA Instant Credit Transfer rulebook ↗ — European Payments Council · Timeout, rejection, and recall handling under the instant scheme
Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. The EPC states it is compliant with Regulation (EU) 2024/886, the Instant Payments Regulation.
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pacs.002, camt.056, pacs.004 message definitions
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Official requirement
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority · Status and reason codes
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.