Skip to content
SEPA CUST

Customer request (RFRO)

Category: Recall / RFRO R-type: RFRO

SCT

Applies

SCT Inst

Applies

SDD Core

N/A

SDD B2B

N/A

Retryable

N/A — recovery request, not a retry

Generated by

Originator, via the originator bank (customer-initiated, not bank-initiated).

ISO 20022 definition

Cancellation requested by the Debtor.

Typical cause

The customer asks for recovery — commonly a wrong beneficiary or a duplicate the customer identified themselves — after the payment has already settled.

What to do about it

File an RFRO via your originator bank within 13 months. The beneficiary can legitimately decline a CUST-reason RFRO — beneficiary consent is required, unlike a FRAD recall.

Rulebook note

RFRO-specific — the customer-initiated counterpart to the bank-initiated Recall procedure (DUPL/TECH/FRAD). Up to 13 months for all RFRO reasons, not just fraud.

Confidence: high. Sourced from PaymentBrief's SEPA R-transaction reference article, cross-verified against ISO 20022 external code sets and EPC guidance documents. Reason-code applicability and timing windows vary by rulebook version and bank handling — verify against your bank or PSP before acting.

Full reference

SEPA Return and Reject Codes: The R-Transaction Reference

Related codes

DUPL

Duplicate payment (Recall)

TECH

Technical problem (Recall)

FRAD

Fraudulent origin (Recall)