Skip to main content

Credit Transfer Reversal

When there's a timeout at RPP (which can occur if the request wasn't sent to the RFI or if RPP didn't receive a response from the RFI), the status of the transaction becomes unknown. To handle this, the transaction is saved in the Store and Forward (SAF) queue so that it can be sent to the RFI again. After resending, some transactions may succeed, while others may be rejected or still remain unknown if the timeouts keep happening and the maximum retry attempts have been reached. Reversal transactions with the status ACSP and ACTC can be updated immediately.

When transactions encounter timeout issues at the RFI and remain unknown even after reaching the maximum number of retries, the OFI and RFI will need to address them separately from RPP. On the other hand, for successful transactions, the payment amount will be reversed accurately.

Credit Transfer Reversal for SAF Rejected Transactions

For this process, only the transactions that have been processed by SAF but then ended with a rejection status will be included into a data file for banks to download from the staging server. When the RFI receives this file, an automated process in the RFI will be triggered to initiate a reverse Credit Transfer back to the Originating FI one by one

Credit Transfer Reversal for SAF Rejected Transactions

StepSenderReceiverProcess
1PayNetAcquirer (RFI)PayNet will provide a Back Office portal where RFI can view the transactions that were rejected by them

Transactions that are in rejected status can either be due to timeout, maximum retries has been exceeded or an outright rejection by the RFI
2Acquirer(RFI)RPPOFI performs the following:If all validations are successful:
  • Send Credit Transfer message request
3A,3BRPPIssuer(OFI)RPP performs the following:If any of the Message Validations fails:
  • Send a REJECT response
If any of the Business Validations fails:
  • Send a NEGATIVE response
If any of the Liquidity Position Validations fails:
  • Send a NEGATIVE response
If all validations are successful:
  • Check if an Account Enquiry request has been made in prior within a stipulated time interval
  • If Account Enquiry is NOT found:
    • Send Account Enquiry by using the same message but changing the transaction code from Credit Transfer to Account Enquiry
  • If Account Enquiry is found:
    • Send Credit Transfer message request
4Issuer (OFI)RPPOFI performs the following:If any of the Message Validations fails:
  • Send a REJECT response
If any of the Business Validations fails:
  • Send a NEGATIVE response
If any of the Beneficiary Account Validations fails:
  • Send a NEGATIVE response
If all validations are successful:
  • Send Account Enquiry message response with the necessary beneficiary account information
5Issuer (OFI)RPPOFI performs the following:If any of the Message Validations fails:
  • Send a REJECT response
If any of the Business Validations fails:
  • Send a NEGATIVE response
If any of the Beneficiary Account Validations fails:
  • Send a NEGATIVE response
If all validations are successful:
  • Send Reversal Response
  • Send Acknowledgement Response.
6RPPAcquirer (RFI)RPP Return Response to RFI

RPP performs the following:

If any of the Message Validations fails:
  • Return a REJECT response to RFI
If any of the Business Validations fails:
  • Return a NEGATIVE response to RFI
If all validations are successful:
  • Update liquidity and settlement positions of both OFI and RFI
  • Send Credit Reversal message response
Notes:

If the signature received from OFI could not be verified:

  • RPP will send an ACCEPTED (signature error) response to the RFI if the OFI responds with a SUCCESSFUL transaction status
  • RPP will send an actual REJECT response to the RFI if OFI responds with a REJECT transaction status
This should take care of any message manipulation done within the data when a signature could not be verified
7Acquirer (RFI)CustomerRFI performs the following:If all validations are successful:
  • SUCCESSFUL response is received:
    • Display the final reversal status to the Customer
  • UNSUCCESSFUL response is received:
    • Display an error message to the Customer
Note
  • The exception scenarios will be handled similarly toCredit Transfer flows
  • While performing credit transfer reversals, it is important to keep in mind the maximum time or date allowed for the reversal. It is advisable not to execute reversals too frequently without considering this limitation, as there won't be any checks in place to prevent it.

Credit Transfer Reversal for Immediate Reversal

For this process, transactions that have been processed by SAF but then ended with a rejection status will be reversed by RPP immediately. This is to support certain payment flows that requires the credit to be reversed immediately to reduce unnecessary manual reconciliation especially to the OFI/Issue

Credit Transfer Reversal for Immediate Reversal

StepSenderReceiverProcess
8bPayNetRPPRFI performs the following:
  • Reject the Credit Transfer request
  • Send Credit Transfer message response

Reversal

Reverse Credit Transfer

For Reverse Credit Transfer, refer to the diagram in the “Credit Transfer Reversal for SAF Rejected Transactions” section step 2 to step 6.



Note
  • The exception scenarios will be handled similarly toCredit Transfer flows
  • While performing credit transfer reversals, it is important to keep in mind the maximum time or date allowed for the reversal. It is advisable not to execute reversals too frequently without considering this limitation, as there won't be any checks in place to prevent it.