Skip to main content

Credit Transfer

Note

A Credit Transfer is a push payment transaction of an amount from a bank account (the debtor account) to a beneficiary account (the creditor) that can be invoked from the Participants' various channels or touchpoints within their ecosystem. Some of these touchpoints may be Internet Banking, Mobile Banking, Branches, Kiosks and etc

The Originating Participant initiates a payment instruction that pushes a credit to the Receiving Participant. The instruction must be sent one at a time to RPP (in case of Bulk Credit Transfers)

Successful End-to-End Credit Transfer Flow

Successful End-to-End Credit Transfer Flow

StepSenderReceiverProcess
1CustomerIssuer (OFI)Customer verifies the beneficiary account details and confirms on the payment
2Issuer (OFI)RPPOFI performs the following:If all validations are successful:
  • Send Credit Transfer message request
3A,3BRPPAcquirer (RFI)RPP performs the following:If any of the Message Validations fails:
  • Return a REJECT response to OFI
If any of the Business Validations fails:
  • Return a NEGATIVE response to OFI
If any of the Liquidity Position Validations fails:
  • Return a NEGATIVE response to OFI
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 (RPP is expected to always initiate an Account Enquiry Webhook prior to Credit Transfer. This control above is only meant for RPP internal handling under certain circumstances):
    • Send Account Enquiry message request by using the same message but changing the transaction code from Credit Transfer to Account Enquiry
    • Go to Step 4
  • If Account Enquiry is found:
    • Send Credit Transfer message request
4Acquirer (RFI)RPPRFI 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
5Acquirer (RFI)RPPRFI 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 Credit Transfer with successful message response
  • Sends Acknowledgement Response
6RPPIssuer (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 all validations are successful:
  • Update liquidity and settlement positions of both OFI and RFI
  • Send Credit Transfer message response
Notes:

If the signature received from RFI could not be verified:

  • RPP will send ACCEPTED (signature error) response to the OFI if the RFI responds with a SUCCESSFUL transaction status
  • RPP will send an actual REJECT response to the OFI if RFI 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

7Issuer (OFI)CustomerOFI performs the following:If all validations are successful:
  • If SUCCESSFUL response is received:
    • Display the Beneficiary Account Name to the Customer for payment confirmation
  • If UNSUCCESSFUL response is received:
    • Display an error message to the Customer

Exception Flows

RPP Failed to Receive Request from OFI

RPP Failed to Receive Request from OFI

ConditionActionsAlternatives
OFI sent a request to RPP. However, RPP did not receive the request

As no response is received from RPP after x period of time, OFI eventually timeout
RPP shall:
  • Timeout
  • Return a NEGATIVE response with timeout reason
OFI shall:
  • Display an appropriate error message to the Customer
  • Stop processing
  • Initiate a Transaction Enquiry separately to confirm on the payment status
If retry is configured, OFI shall:
  • If retry count has not exceeded the maximum number of retries
    • Send a repeat request
    • Continue processing
  • If retry count has exceeded the maximum number of retries
    • Display an ACCEPTED status message to Customer
    • Stop processing
    • Confirm the payment manually via Back Office portal

OFI Failed to Receive Response from RPP

OFI Failed to Receive Response from RPP

ConditionActionsAlternatives
OFI sent a request to RPP, and RPP did receive the request. However, RPP response did not reach to OFI

As no response is received from RPP after x period of time, OFI eventually timeout
RPP shall:
  • Timeout
  • Return a NEGATIVE response with timeout reason
OFI shall:
  • Display an appropriate error message to the Customer
  • Stop processing
  • Initiate a Transaction Enquiry separately to confirm on the payment status
If retry is configured, OFI shall:
  • If retry count has not exceeded the maximum number of retries
    • Send a repeat request
    • Continue processing
  • If retry count has exceeded the maximum number of retries
    • Display an ACCEPTED status message to Customer
    • Stop processing
    • Confirm the payment manually via Back Office portal

RFI Failed to Receive Request from RPP

RFI Failed to Receive Request from RPP

ConditionActionsAlternatives
RPP sent a request to RFI. However, RFI did not receive the request from RPP

As no response is received from RFI after x period of time, RPP eventually timeout
RPP shall:
  • Timeout
  • Return a NEGATIVE response with timeout reason
OFI shall:
  • Display an appropriate error message to the Customer
  • Stop processing
  • Initiate a Transaction Enquiry separately to confirm on the payment status
If retry is configured, RPP shall:
  • Store the request to SAF
  • If retry count has not exceeded the maximum number of retries
    • Send a repeat request
    • Continue processing
  • If retry count has exceeded the maximum number of retries
    • Display an ACCEPTED status message to Customer
    • Stop processing
    • Confirm the payment manually via Back Office portal

RPP Failed to Receive Response from RFI

RPP Failed to Receive Response from RFI

ConditionActionsAlternatives
RPP sent a request to RFI, and RFI did receive the request. However, RFI response did not reach to RPP

As no response is received from RFI after x period of time, RPP eventually timeout
RPP shall:
  • Timeout
  • Return a NEGATIVE response with timeout reason
OFI shall:
  • Display an appropriate error message to the Customer
  • Stop processing
If retry is configured, RPP shall:
  • Store the request to SAF
  • If retry count has not exceeded the maximum number of retries
    • Send a repeat request
    • Continue processing
  • If retry count has exceeded the maximum number of retries
    • Display an ACCEPTED status message to Customer
    • Stop processing
    • Confirm the payment manually via Back Office portal