Credit Transfer

See also API reference for Credit Transfer

Introduction

info

The terminology Phase 1 is being used interchangeably to refer to services that are originally built for DuitNow Transfer i.e. Account Enquiry, Credit Transfer and National Addressing Database (NAD) related. QR, P2P, JomPAY and etc are built as overlay services on top of Phase 1. Hence these overlay services will adopt similar architecture and user will be asked to refer to Phase 1 sections throughout our documentations

Instant Transfer is a Credit Transfer service in which the customer sends the payment request and confirms the recipient's name before the actual credit transfer is performed. This payment request is a two-step process where an account enquiry request is sent to the Receiving Participant to request for the recipient's name, and upon successful retrieval of the Account Name, displays it to the customer for confirmation. Once confirmation is received, the Originating Participant then debits customer account and sends the actual Credit Transfer request to the Receiving Participant for processing

DuitNow Transfer will be marketed for use by the Participants' Retail and Corporate customers and invoked from the Participants' Internet and Mobile Banking channels

Overlay Services

Overlay services are services that augment a payment service by building on top of Real-time Retail Payments Platform (RPP) existing infrastructure to deliver enhanced value to the participants within Malaysia payment network

What are Overlay Services?

In RPP, we have built the below overlay services to improve the workflows and customer experience in facilitating different payment use cases

QR payment for both domestic and cross border
Bill payment via JomPAY
Request-to-pay for end user to request or make a payment within the eCommerce space

Refer to the respective service sections on our product offerings

Account Enquiry

note

Account resolution enquiry is used to determine if particular beneficiary account is valid and ready to receive payment. There are many situations in which you may need to know if a beneficiary account provided by customer is valid before accepting payment request. Examples include:

Customer needs to validate the beneficiary account name before making final confirmation to the payment request
Customer needs to ensure the recipient details before making top-up to their eWallet account

Successful End-to-End Account Enquiry Flow

Step	Sender	Receiver	Process
1	Customer	OFI	Customer logs into Online Banking or Mobile Banking app and initiates a DuitNow Instant Transfer
2	OFI	RPP	OFI performs the following: Authorize and validate the Instant Transfer transaction Any internal validations If all validations are successful: Send Account Enquiry request
3	RPP	RFI	RPP performs the following: Message Validations Business Validations 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 all validations are successful: Send Account Enquiry message request
4	RFI	RPP	RFI performs the following: Message Validations Business Validations Beneficiary Account Validations 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
5	RPP	OFI	RPP performs the following: Message Validations Business Validations If any of the validations are not successful: Send a NEGATIVE/REJECT response If all validations are successful: Send Account Enquiry message response with the necessary beneficiary account information
6	OFI	Customer	OFI performs the following: Message Validations Business Validations 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

Condition	Actions	Alternatives
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	OFI shall: Timeout Display an appropriate error message to the Customer Stop processing	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 error message to Customer Stop processing

OFI Failed to Receive Response from RPP

Condition	Actions	Alternatives
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	OFI shall: Timeout Display an appropriate error message to the Customer Stop processing	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 error message to Customer Stop processing

RFI Failed to Receive Request from RPP

Condition	Actions	Alternatives
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	-

Condition

Actions

Alternatives

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

RPP Failed to Receive Response from RFI

Condition	Actions	Alternatives
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	-

Condition

Actions

Alternatives

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

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

Step	Sender	Receiver	Process
1	Customer	OFI	Customer verifies the beneficiary account details and confirms on the payment
2	OFI	RPP	OFI performs the following: Authorize and validate the Instant Transfer transaction Any internal validations Debit source account If all validations are successful: Send Credit Transfer message request
3	RPP	RFI	RPP performs the following: Message Validations Business Validations Liquidity Position Validations 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 (Participant is expected to always initiate an Account Enquiry 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 Go to Step 7
CONDITIONAL ACCOUNT ENQUIRY
4	RFI	RPP	RFI performs the following: Message Validations Business Validations Beneficiary Account Validations 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
5	RPP	OFI	RPP performs the following: Message Validations Business Validations 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 all validations are successful: Check the message response If response is SUCCESSFUL Send Credit Transfer message request Go to Step 7 If response is UNSUCCESSFUL Return a NEGATIVE response to OFI Credit Transfer will not be triggered
6	OFI	Customer	OFI performs the following: Message Validations Business Validations 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
CREDIT TRANSFER
7	RFI	RPP	RFI performs the following: Message Validations Business Validations Beneficiary Account Validations 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 Notes: When a REPEAT request is received by the RFI from RPP: If the original transaction has been posted successfully by the RFI, RFI will respond with the original transaction response instead of rejecting the REPEAT request as duplicate If the original transaction has not been processed previously, RFI will process the transaction and return the appropriate response to RPP
8	RPP	OFI	RPP performs the following: Message Validations Business Validations 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 an 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
9	OFI	Customer	OFI performs the following: Message Validations Business Validations If all validations are successful: If SUCCESSFUL response is received: Display the final payment status to the Customer If UNSUCCESSFUL response is received: Display an error message to the Customer Perform a debit reversal on the Customer account (if necessary)