Reference

Operator-grade reference for payment failure codes, status flows, validation, operations, and playbooks. SEPA, SWIFT, ISO 20022.

Start here

Mid-intent hub: SWIFT failures, SEPA returns, stuck payments — links into detailed reference.

Return reason codes (R01, R02, R03…) with table summary and links to detailed pages.

NACK, routing, and business rejects overview with links to detailed pages.

pacs.002 status codes (ACSP, ACSC, RJCT, PDNG) and timing.

Return codes overview (R01, R02, R03…)
Table summary of SEPA return reason codes with links to detailed pages.
R01 – Insufficient Funds
Funds-availability outcome; when it occurs, impact, and prevention.
R02 – Account Closed
Account lifecycle; beneficiary bank returns; impact on recurring flows.

Error codes overview (NACK, routing, business rejects)
Structured reference and lifecycle context; links to detailed pages.
NACK – Format Error
Network-level rejection; invalid BIC, missing field 59; pre-validation.
Intermediary routing failure
Field 56/57, nostro alignment, unexpected routing.

IBAN validation failure
Checksum vs scheme acceptance; BIC mismatch, closed account.

Cut-off time failure (cross-border)
Submission vs value cutoff; FX and liquidity timing; SLA risk.
Stuck payment detection
Absence-of-event detection; SLA thresholds; triage.
SLA breach monitoring
Settlement SLA by rail; event-driven monitoring; escalation.

Investigate a rejected SWIFT payment
Trace reconstruction; network vs correspondent vs beneficiary; evidence pack.

Preflight is a pre-execution and post-execution control layer for payments.

Preflight models these scenarios deterministically before and after execution.