Skip to content
SEPA FRAD

Fraudulent origin (Recall)

Category: Recall / RFRO R-type: Recall

SCT

Applies

SCT Inst

Applies

SDD Core

N/A

SDD B2B

N/A

Retryable

N/A — recovery procedure, not a retry

Generated by

Originator bank (bank-initiated).

ISO 20022 definition

Cancellation requested following a transaction that was originated fraudulently.

Typical cause

Suspected fraud on the sending side of an SCT/SCT Inst payment.

What to do about it

Cooperate immediately — refusal to return funds on a FRAD recall carries regulatory and legal risk, unlike a discretionary RFRO decline. Beneficiary bank assesses and decides whether to return within the 15-banking-business-day response window.

Rulebook note

The only Recall reason code with an extended window — up to 13 months, versus 10 banking business days for DUPL/TECH. Unlike a beneficiary declining an RFRO for CUST/AM09/AC03, declining a FRAD recall carries meaningfully higher legal exposure.

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)

CUST

Customer request (RFRO)