...DuitNow Online Banking/WalletIntegrationOverview

Integration

The DuitNow Online Banking/Wallets API enables seamless integration, allowing merchants to accept payments from customers using their preferred bank or wallet through DuitNow Pay. This API is essential for Issuers and Acquirers, ensuring smooth payment processing and linking merchants with a wide range of financial institutions and digital wallets.

The diagram below provides a detailed overview of the DuitNow Online Banking/Wallets process.

Successful Redirect - Request List of Banks Flow (Steps 1-8)

Step	Sender	Receiver	Process
1	Customer	Merchant/Biller	Customer initiates payment via Merchant/Biller Portal.
2	Merchant/Biller	Merchant Acquirer/System Integrator	Merchant/Biller performs the following: Submit request for list of banks
3	Merchant Acquirer/System Integrator	DuitNow Pay	Merchant Acquirer/System Integrator performs the following: Submit request for list of banks
4	DuitNow Pay	RPP	DuitNow Pay performs the following: Submit request for list of banks Note: Transaction Type: 650
5	RPP	DuitNow Pay	RPP performs the following: Message Logging Message Validation Message Format Validation Digital Signature Verification If any Message Validation fails, RPP will: Send a REJECT response to DuitNow Pay If all validations are successful, RPP Back Office will: Send List of Banks response to DuitNow Pay Note: Transaction Type: 650
6	DuitNow Pay	Merchant Acquirer/System Integrator	If any Message Validation fails, DuitNow Pay will: Send a REJECT response to Merchant Acquirer/System Integrator If all validations are successful, DuitNow Pay will: Send List of Banks response to Merchant Acquirer/System Integrator
7	Merchant Acquirer/System Integrator	Merchant/Biller	Merchant Acquirer/System Integrator will: Send List of Banks response to Merchant/Biller
8	Merchant/Biller	Customer	Merchant/Biller performs the following: For SUCCESSFUL List of Banks response received, display List of Banks For UNSUCCESSFUL List of Banks response received, display an error message on the customer screen

Successful Redirect – Request-to-Pay Flow (Steps 9-19)

Step	Sender	Receiver	Process
9	Customer	Merchant/Biller	Customer confirms payment option and initiates One Time Payment via DuitNow Pay.
10	Merchant/Biller	Merchant Acquirer/System Integrator	Merchant/Biller will perform the following: Validate One Time Payment request Send One Time Payment request to Merchant Acquirer/System Integrator
11	Merchant Acquirer/System Integrator	DuitNow Pay	Merchant Acquirer/System Integrator performs the following: Validate One Time Payment request Send One Time Payment request to DuitNow Pay
12	DuitNow Pay	RPP	DuitNow Pay will perform the following: Authorize and validate One Time Payment request Send One Time Payment request to RPP Start timer Note: Transaction Type: 861
13	RPP	DuitNow Pay	RPP performs the following: Message Logging Message Validation Message Format Validation Digital Signature Validation Business Validation Timeout Validation Payment Validation Check Date Expiry Check Merchant ID Validation Merchant Product ID Validation If any Message Validation fails, RPP will: Send a REJECT response to DuitNow Pay If any Business Validation fails, RPP will: Send a NEGATIVE response to DuitNow Pay If all validations are successful, RPP will: Lookup and populate Acquirer Account ID and Acquirer based on Merchant ID and Merchant Product ID Generate Signature with End-to-End ID Store Transaction Information in Request-to-Pay Staging Table Send an ACCEPTED response back to DuitNow Pay with End-to-End ID and Signature Note: Timeout is set at 20 seconds Transaction Type: 861
14	DuitNow Pay	Merchant Acquirer/System Integrator	If any validation fails, DuitNow Pay will: Send a REJECT response to Merchant Acquirer/System Integrator If all validations are successful, DuitNow Pay will: Generate Signature with End-to-End ID Send an ACCEPTED response back to Merchant Acquirer/System Integrator with End-to-End ID and Signature
15	Merchant Acquirer/System Integrator	Merchant/Biller	If any validation fails, Merchant Acquirer/System Integrator will: Send a REJECT response to Merchant/Biller If all validations are successful, Merchant Acquirer/System Integrator will: Send an ACCEPTED response back to Merchant/Biller with End-to-End ID and Signature
16	DuitNow Pay	Merchant Acquirer/System Integrator	DuitNow Pay will be sending the checkout details back to Merchant Acquirer/System Integrator via webhook.
17	Merchant Acquirer/System Integrator	Merchant/Biller	Merchant Acquirer/System Integrator will be sending the checkout details back to Merchant/Biller.
18	Merchant Acquirer/System Integrator	DuitNow Pay	Acquirer shall provide an acknowledgment back to DuitNow Pay.
19	Merchant/Biller	Issuer	Merchant/Biller will redirect Customer to selected bank along with Signature and End-to-End ID to Issuer.

Successful Redirect – Retrieve Transaction Info Flow (Steps 20-23)

Step	Sender	Receiver	Process
20	Issuer	RPP	Issuer performs the following: Validate Signature sent by Merchant/Biller Send Retrieve Transaction Info Request based on End-to-End ID Start Timer Note: Transaction Type: 862
21	RPP	Issuer	RPP performs the following: Message Logging Message Validation Message Format Validation Digital Signature Validation Business Validation Timeout Validation Payment Validation Check Check Request-to-Pay Staging Status 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: Lookup Transaction Info based on End-to-End ID from Staging Table Return Retrieve Transaction Info Response Note: Transaction Type: 862
22	Customer	Issuer	Customer logs into Mobile/Internet Banking portal of Issuer
23	Issuer	Customer	Issuer performs the following: Perform Login Validation If validation fails, Issuer will: Display error code to Customer Send cancel Request-to-Pay to RPP If validation is successful, Issuer will: Display Transaction Information to Customer

Successful Redirect – Update Payment Status Flow (Steps 24-31)

This is an optional step for scenarios where the Request-to-Pay status needs to be updated either to (a) Rejected, where Issuer has to reject the redirect due to failed login or cancelled payments, or to (b) Pending Authorisation for two-level Authentication.  

Step	Sender	Receiver	Process
24	Customer	Issuer	Customer performs the following: Confirm Transaction Information Request update transaction status to Pending Authorisation for two-level authentication.
25	Issuer	RPP	Issuer performs the following: Validate Customer Response Any other validation Send update payment status request to RPP Start timer Note: Transaction Type: 863
26	RPP	Issuer	RPP performs the following: Message Logging Message Validation Message Format Validation Digital Signature Validation Business Validation Timeout Validation Payment Validation Check Check Request-to-Pay Staging Status 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: Update Request-to-Pay Staging table status to: ‘PDAU’ (Pending Authorisation) OR ‘RJCT’ (Rejected) Return Transaction Status Response Note: Transaction Type: 863
27	RPP	DuitNow Pay	RPP performs the following: Notify Merchant of Update Payment Status via DuitNow Pay
28	DuitNow Pay	Merchant Acquirer/System Integrator	Payment status will be parsed to Merchant Acquirer/System Integrator as part of the webhook.
29	Merchant Acquirer/System Integrator	Merchant/Biller	Payment status will be parsed to Merchant/Biller as part of the webhook.
30	Merchant/Biller	Merchant Acquirer/System Integrator	Merchant/Biller shall provide an acknowledgment back to Merchant Acquirer/System Integrator.
31	Merchant Acquirer/System Integrator	DuitNow Pay	Merchant Acquirer/System Integrator shall provide an acknowledgment back to DuitNow Pay.

Successful Redirect – Credit Transfer Flow (Steps 24-34)

Step	Sender	Receiver	Process
24	Customer	Issuer	Customer performs the following: Confirm Transaction Information
25	Issuer	RPP	Debiting Agent performs the following : Validate Customer Response Expiry of RTP Request (861) receive during Retrieve Transaction Information (862) Any other validation Debit customer Send update payment status request to RPP Start timer Note: Transaction Type: 070
26	RPP	Issuer	RPP performs the following: Message Logging Message Validation Message Format Validation Digital Signature Validation Business Validation Timeout Validation Payment Validation Check Check Request-to-Pay Staging Status Minimum Amount Check Maximum Amount Check If any Message Validation fails, RPP will: Send a REJECT response to Debiting Agent If any Business Validation fails, RPP will: Send a NEGATIVEresponse to Debiting Agent If all validations are successful, RPP will: Update liquidity positions of both Crediting Agent and Debiting Agent Update settlement totals Update Request-to-Pay Staging table status to ‘SUCC’ (Successful) Return Payment Status Response with Merchant Redirect URL/App ID Encrypts Debtor Account with Business Message ID Submits Credit Transfer Request to SAF Note: Timeout is set at 20 seconds Transaction Type: 070
27	RPP	DuitNow Pay	RPP performs the following: Notify Merchant of Update Payment Status via DuitNow Pay
28	DuitNow Pay	Merchant Acquirer/System Integrator	Payment status will be parsed to Merchant Acquirer/System Integrator as part of the webhook.
29	Merchant Acquirer/System Integrator	Merchant/Biller	Payment status will be parsed to Merchant/Biller as part of the webhook.
30	Merchant/Biller	Merchant Acquirer/System Integrator	Merchant/Biller shall provide an acknowledgment back to Merchant Acquirer/System Integrator.
31	Merchant Acquirer/System Integrator	DuitNow Pay	Merchant Acquirer/System Integrator shall provide an acknowledgment back to DuitNow Pay.
32	RPP	Acquirer	RPP performs the following: Check for SAF retry necessity based 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 Credit Transfer Request to Acquirer Start timer Note: SAF will automatically send requests to Acquirer up to the maximum number of retries Once maximum retry has been exceeded with no response, Participant must check the Exceptional SAF Report Note: Transaction Type: 070
33	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 SUCCESSFULresponse to RPP Note: Transaction Type: 070
34	Issuer	Merchant	Issuer to display the result to customer and redirect customer back to merchant portal.