...DuitNow ConsentIntegrationConsent Registration Via Issuer Flow

We've Launched a New Documentation Website (Beta Launch)

The documentation for DuitNow is now available on our newly launched documentation platform. This is an initial beta rollout of our new documentation site, designed to become the long-term home for all documentation moving forward.

You'll find the familiar content you're used to—now hosted on a new platform that will progressively receive updates and enhancements.

We encourage you to start accessing DuitNow materials there to explore the new experience and ensure you're viewing the latest documentation updates. If you have any feedback, please reach out to us.

Visit the New Documentation Website

Consent Registration via Issuer Flow

The Consent Registration API via Issuer enables customers to initiate consent registration through their Debiting Agent. This provides an alternative way for customers to register their consent with their billers, directly through their bank or financial institution.

Successful Registration via Issuer – Request List of Merchants Flow (Steps 1-4)

Step	Sender	Receiver	Process
1	Customer	Issuer	Customer selects to register Consent
2	Issuer	RPP	Issuer performs the following: Submit request for list of merchants Starts Timer Note: Transaction Type: 660
3	RPP	Issuer	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 Issuer If all validations are successful, RPP will Send List of Merchant response to Issuer Note: Transaction Type: 660
4	Issuer	Customer	Issuer performs the following: Stops timer Message Validation Message Format Validation Digital Signature Verification If all validations are successful, Issuer will For SUCCESSFUL List of Merchant response received, Display List of Merchant For UNSUCCESSFUL List of Merchant response received, Display an error message on the customer screen

Successful Registration via Issuer – Request List of Merchant Product Flow (Steps 1-4)

Step	Sender	Receiver	Process
1	Customer	Issuer	Customer selects Merchant
2	Issuer	RPP	Issuer performs the following: Submit request for list of merchant product Starts Timer Note: Transaction Type: 670
3	RPP	Issuer	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 Issuer If all validations are successful, RPP will Send List of Merchant response to Issuer Note: Transaction Type: 670
4	Issuer	Customer	Issuer performs the following: Stops timer Message Validation Message Format Validation Digital Signature Verification If all validations are successful, Issuer will For SUCCESSFUL List of Merchant Product response received, Display List of Merchant Product For UNSUCCESSFUL List of Merchant Product response received, Display an error message on the customer screen

Successful Registration via Issuer – Consent Registration Flow (Steps 5-8)

Step	Sender	Receiver	Process
5	Customer	Issuer	Customer selects a Merchant
6	Issuer	RPP	Issuer will perform the following: Authorize and validate Consent Registration request Send Consent Registration request to RPP Start timer Note: If customer selects multiple consent type, Issuer will send multiple Consent Registration requests Transaction Type: 821
6A	RPP	Issuer	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 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 validations are successful, RPP will Generate Consent ID Send an ACCEPTED response back to Issuer Note: Timeout is set at 20 seconds
7	RPP	Acquirer	RPP performs the following Store Consent Registration request in SAF and begins submitting 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 If retry is required, Send repeat Consent Registration Request to Issuer 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 Timeout is set at 20 seconds Transaction Type: 821
7A	Acquirer	RPP	Acquirer performs the following Message Validation Message Format Validation Digital Signature Validation Business Validation Mandatory and conditional fields validation Merchant ID Validation Any other validation If any Message Validation fails, Acquirer will Send a REJECT response to RPP If any Business Validation fails, Acquirer will Send a NEGATIVE response to RPP If all validations are successful, Acquirer will Send a SUCCESSFUL response to RPP Note: Transaction Type: 821
8	Acquirer	Merchant / Biller	Acquirer sends notification and authorization request to Merchant/Biller about Consent Registration request

Successful Registration via Issuer – Update Consent Status (Steps 9-12)

Step	Sender	Receiver	Process
9	Merchant / Biller	Acquirer	Merchant / Biller receives notification of Consent Registration and authorization request. Confirmation is sent to Acquirer
10	Acquirer	RPP	Acquirer performs the following: Authorizes and validates the Update Consent Status request Send Update Consent Status request to RPP Start Timer Note: Transaction Type: 822
10A	RPP	Acquirer	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 Transaction Type Validation Timeout Validation Allowed Max Amount Validation Expiry Date Validation 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 Register the consent and account Send the ACCEPTED response to Acquirer Note: Timeout is set at 20 seconds Transaction Type: 822
11	RPP	Issuer	RPP performs the following Store Update Consent Status request in SAF Begin submitting Update Consent Status 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 SAF Out Payment Tolerance Period If retry is required, Send repeat Update Consent Status Request to Issuer 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: 822
11A	Issuer	RPP	Issuer performs the following: Message Validation Message Format Validation Digital Signature Verification If any Message Validation fails, Issuer will Send a REJECT response to RPP If all validations are successful, Issuer will Send a SUCCESSFUL response to RPP Note: Issuer shall not reject transactions coming from the SAF queue Transaction Type: 822
12	Issuer	Customer	Issuer informs Customer of successful Consent Registration