R transactions for SEPA indirect participants
Becoming a SEPA indirect participant through a sponsor bank brings a payment service provider closer to the SEPA clearing and settlement mechanisms (CSMs). While being SEPA indirect participant is a significant undertaking (usually part of a broader core banking build initiative), it does bring additional payment agility and control.
In addition to regular SEPA payment flows, SEPA indirect and direct participants have access to and must be able to support additional payment flows. These flows are known as related transactions or R transactions.
A SEPA indirect or direct participant must be able to return a SEPA credit transfer that was previously received or a SEPA direct debit that was previously sent. Similarly, they must be able to receive a return related to a SEPA credit transfer previously sent or a SEPA direct debit previously debited. A return can be proactive or be sent in response to a return request, also called a recall.
A return includes a reason code that explains the cause of the return. Common reason codes include AC01 for an incorrect account number, AC06 for a blocked bank account, and AM04 for insufficient funds. A return sent in response to a return request always has FOCR (for “following cancellation request”) as a reason code.
A SEPA direct or indirect participant must also be able to recall a SEPA credit transfer that was previously sent or a SEPA direct debit core that was previously debited. Similarly, they must be able to answer a recall received from another SEPA direct or indirect participant.
The recall includes a reference to the corresponding payment as well as a reason code. The three reason codes authorised for recalls are DUPL for a duplicate payment, TECH for a technical error, and FRAD for a fraudulent payment.
When receiving a recall, a SEPA direct or indirect participant can either answer positively, returning FOCR as a reason code, or negatively, with reason codes including LEGL for legal reasons, NOOR if no original payment was sent or received, or ARDT if the payment had already been returned.
Not answering a recall can result in an inquiry message. This message is a reminder of a recall which has remained unanswered. SEPA direct and indirect participants are expected to accept or deny the inquiry by responding to the related recall.
When sending R transactions, SEPA indirect or direct participants are expected to use standard reason codes. Just like SEPA messages, SEPA reason codes rely on ISO standards and use ISO external codes. Below is a list of the most common reason codes.
Learn more about becoming a SEPA indirect participant
In this article, we've just covered how the R transactions are managed by SEPA indirect participants. We will soon share more content about the opportunities and challenges of becoming a SEPA indirect participant.
Subscribe to our newsletter to stay in the loop or download our guide to SEPA to learn more.
Other articles you might like
SEPA rulebook digest for 2023: what to look for
The main differences between SEPA Direct Debit Core and B2B
SEPA messages: what they are and how they work
Local payment schemes in the UK: CHAPS, BACS, FPS and ATP explained
SEPA payments by the numbers
The different stakeholders involved in SEPA
The different SEPA payment schemes
Common characteristics of a SEPA payment
Not sure where to start?
Let’s talk about how we can work together to accelerate your payment flows. Get a demo of our platform, explore our pricing, or get started right away.