...DuitNow ConsentIntegrationConsent Registration Decoupled: Request to Pay

Consent Registration Decoupled: Request to Pay

The Request to Pay API enables Billers/Merchants to send a consent request to the Customer. Typically, the consent request will be delivered to the Customer’s e-banking inbox (e.g., Internet Banking or Mobile Banking). The Customer can then review and take action on the request. In the Request to Pay flow, the consent request is not time-sensitive and can have a longer expiration period.

Successful Proxy Enquiry Flow (Steps 1-4)

Pay by Proxy

Pay by Proxy allows customers to make payments using a registered Proxy ID, such as a mobile number, NRIC, passport number, army number, or business registration number.

Successful Account Enquiry Flow (Steps 1-4)

Pay by Account

The Account Resolution Enquiry API verifies the validity of a beneficiary account before processing a payment request, ensuring the account is ready to receive funds.

Successful Consent Registration: Consent Registration via Acquirer (Steps 5-8)

Step	Sender	Receiver	Process
5	Biller / Merchant	Acquirer	Biller/Merchant initiates Consent Registration request via Acquirer’s Mobile App/Internet Banking portal.
6	Acquirer	RPP	Acquirer will perform the following: Authorize and validate Consent Registration request Send Consent Registration request to RPP Start timer Note: Transaction Type: 801 or 802
6A	RPP	Acquirer	RPP performs the following Message Logging Message Validation Message Format Validation Digital Signature Validation Business Validation Timeout Validation Transaction Type Validation Date Expiry Check Allowed Max Amount Check If Acquirer Sent Registration ID, Lookup and populate Customer Account Info and Issuer based on Registration ID If any Message Validation fails, RPP will Send a REJECT response to Acquirer If any Business Validation fails, RPP will Send a NEGATIVE response to Acquirer If all validations are successful, RPP will Create entry in Consent Table Generate Consent ID Set Consent Status to PNDG Send an ACCEPTED response back to Acquirer Note: Timeout is set at 20 seconds Transaction Type: 801 or 802
7	RPP	Issuer	RPP performs the following Store Consent Registration request in SAF and begins submitting request to Issuer Check for retry necessity base on the following parameters: - SAF Maximum Distribution Rate (msg/sec) aka TPS SAF Message Response Timer (sec) SAF Message Retry Limit SAF Open Session Limit SAF Timeout Count SAF Pause Period (sec) after consecutive timeouts If retry is required, Send repeat Consent Registration Request to Issuer Start timer Note: SAF will automatically send requests to Issuer up to the number of maximums retry Once maximum retry has been exceeded with no response, Participant must check the Exceptional SAF Report Transaction Type: 801 or 802
7A	Issuer	RPP	Issuer performs the following Message Validation Message Format Validation Digital Signature Validation Business Validation Mandatory and conditional fields validation Customer Account Validation Timeout Validation Any other validation If any Message Validation fails, Issuer will Send a REJECT response to RPP If any Business Validation fails, Issuer will Send a NEGATIVE response to RPP If all validations are successful, Issuer will Send a SUCCESSFUL response to RPP Note: Transaction Type: 801 or 802
8	Issuer	Customer	Issuer sends notification and authorization request to Customer about Consent Registration request

Successful Consent Registration – Accepted Registration Flow (Steps 9-12)

Step	Sender	Receiver	Process
9	Customer	Issuer	Customer receives notification of Consent Registration and authorization request. Customer Performs the following Customer Selects Consent type Customer confirms authorization
10	Issuer	RPP	Issuer performs the following: Authorizes and validates the Register Consent request Send Register Consent request to RPP Start timer Note: Transaction Type: 803
10A	RPP	Issuer	RPP performs the following: Message Logging Message Validation Message Format Validation Digital Signature Verification Business Validation Mandatory and conditional fields validation Timeout Validation Business Message Identifier validation Issuer Check Acquirer Check Allowed Max Amount Check Expiry Date Check If any Message Validation fails, RPP will Send a REJECT response to Issuer If any Business Validation fails, RPP will Send a NEGATIVE response to Issuer If all validations are successful, RPP will Set Consent Status to ACTV Send the ACCEPTED response to Issuer Note: Transaction Type: 803
11	RPP	Acquirer	RPP performs the following Store Register Consent request in SAF Begin submitting Register Consent request to Acquirer Check for retry necessity base on the following parameters:- SAF Maximum Distribution Rate (msg/sec) aka TPS SAF Message Response Timer (sec) SAF Message Retry Limit SAF Open Session Limit SAF Timeout Count SAF Pause Period (sec) after consecutive timeouts SAF Out Payment Tolerance Period If retry is required, Send repeat Register Consent Request to Acquirer Start timer Note: SAF will automatically send requests to Issuer up to the number of maximum retry Once maximum retry has been exceeded with no response, Participant must check the Exceptional SAF Report Transaction Type: 803
11A	Acquirer	RPP	Acquirer performs the following: Message Validation Message Format Validation Digital Signature Verification If any Message Validation fails, Acquirer will Send a REJECT response to RPP If all validations are successful, Acquirer will Send a SUCCESSFUL response to RPP Note: Transaction Type: 803
12	Acquirer	Biller / Merchant	Acquirer informs Biller/Merchant of successful Consent Registration

Successful Rejection Flow (Steps 9-12)

Step	Sender	Receiver	Process
9	Customer	Issuer	Customer receives notification of Consent request and authorization request. Customer rejects the request. Note: Customer can also opt to block receiving any further Consent requests from the Merchant/ Biller. Issuer will manage list of blocked Merchant/ Billers
10	Issuer	RPP	Issuer performs the following: Rejects the request Checks if customer would also like to block Any other validations If all validations are successful, Issuer will Send Reject request to RPP Start timer Note: If the customer has indicated to block the Merchant/ Biller, Issuer shall monitor. Transaction Type: 804
10A	RPP	Issuer	RPP performs the following: Message Logging Message Validation Message Format Validation Digital Signature Verification Business Validation Mandatory and conditional fields validation Business Message Identifier validation Issuer Check Acquirer Check Repeat Check Date Tolerance Check Timeout Validation If any Message Validation fails, RPP will Send a REJECT response to Issuer If any Business Validation fails, RPP will Send a NEGATIVE response to Issuer If all validation are successful, RPP will Send the ACCEPTED response to Issuer Note: Timeout is set at 20 seconds Transaction Type: 804
11	RPP	Acquirer	RPP performs the following Store Reject request in SAF Begin submitting Reject request to Acquirer Check for retry necessity base on the following parameters: - SAF Maximum Distribution Rate (msg/sec) aka TPS SAF Message Response Timer (sec) SAF Message Retry Limit SAF Open Session Limit SAF Timeout Count SAF Pause Period (sec) after consecutive timeouts SAF Out Payment Tolerance Period If retry is required, Send repeat Reject request to Acquirer Start timer Note: SAF will automatically send requests to Acquirer up to the number of maximums retry Once maximum retry has been exceeded with no response, Participant must check the Exceptional SAF Report Transaction Type: 804
11A	Acquirer	RPP	Acquirer performs the following: Message Validation Message Format Validation Digital Signature Verification If any Message Validation fails, Acquirer will Send a REJECT response to RPP If all validation is successful, Acquirer will Send a SUCCESSFUL response to RPP Note: Acquirer shall not reject transactions coming from the SAF queue If the customer has indicated to block the Merchant/ Biller, Acquirer shall monitor. Transaction Type: 804
12	Acquirer	Biller / Merchant	Acquirer informs Merchant/ Biller of the rejected Consent request.