Skip to main content

Consent Registration DuitNow Pay: Save Payment Flow

In the DuitNow Pay - Save Payment API flow, the customer is redirected to their selected bank to authorize the consent request. This flow is typically used when customers add their Current Account Savings Account (CASA) as a payment method on a merchant's platform.

StepSenderReceiverProcess
9CustomerMerchant / BillerCustomer confirms payment option and initiate to save payment method.
10Merchant / BillerMerchant Acquirer/System Integrator

Merchant/Biller will perform the following:

  • Validate request
  • Send save payment method request to Merchant Acquirer/System Integrator

11Merchant Acquirer/System IntegratorDuitNow Pay

Merchant Acquirer/System Integrator the following:

  • Validate request
  • Send save payment method request to Merchant Acquirer/System Integrator

12DuitNow PayRPP

DuitNow Pay will perform the following:

  • Authorize and validate Consent Registration request
  • Send Consent Registration request to RPP
  • Start timer

Note:

  • Transaction Type: 811

13RPPDuitNow 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
  • Stop timer

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

  • Generate Signature with End-to-End ID Send an ACCEPTED response back to DuitNow Pay with End-to-End ID and Signature

Note:

  • Timeout is set at 20 seconds
  • Transaction Type: 811

14DuitNow PayMerchant 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

  • Send an ACCEPTED response back to Merchant Acquirer/ System Integrator with End-to-End ID and Signature

15Merchant Acquirer/ System IntegratorMerchant/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

16DuitNow PayMerchant Acquirer/ System IntegratorDuitNow Pay will be sending the checkout details back to Merchant Acquirer/ System Integrator via webhook.
17Merchant Acquirer/ System IntegratorMerchant/BillerMerchant Acquirer/ System Integrator will be sending the checkout details back to Merchant / Biller.
18Merchant Acquirer/ System IntegratorDuitNow PayAcquirer shall provide an acknowledgement back to DuitNow Pay.
19Merchant / BillerIssuerMerchant / Biller will redirect Customer to selected bank along with Signature and End-to-End ID to Issuer.

StepSenderReceiverProcess
20IssuerRPP

Issuer performs the following

  • Validate Signature sent by Merchant / Biller
  • Send Retrieve Consent Info Request based on End-to-End ID
  • Start Timer

Note:

  • Transaction Type: 812

21RPPIssuer

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
  • Stop timer

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

  • Return Retrieved Consent Info Response

Note:

  • Transaction Type: 812

22CustomerIssuerCustomer Logs into Mobile/Internet Banking portal of Issuer
23IssuerCustomer

Issuer performs the following:

  • Perform Login Validation

If validation fails Issuer will

  • Reject Customer Login and return error code

If validation is successful

  • Display Consent Detail to customer


StepSenderReceiverProcess
24CustomerIssuer

Customer performs the following

  • Confirm Consent Detail
  • Authorise Consent Registration OR Update Status to Pending Authorisation

Note:

Update to Pending Authorisation is an optional step for scenarios where the Consent Registration needs to be updated to Pending Authorisation for two level Authentication.

25IssuerRPP

Issuer performs the following

  • Validate Customer Response
  • Any other validation
  • Send Update Consent Status request to RPP
  • Start timer

Note:

  • If customer selects multiple consent type, Issuer will send multiple Update Consent Status request
  • Transaction Type: 813

26RPPIssuer

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
  • Timeout Validation
  • Transaction Type Validation
  • Allowed Max Amount Check
  • Expiry Date Check
  • Check Consent 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

  • IF Issuer sent Update Consent Status to PDAU (Pending Authorisaton);
  • Update Consent Staging Table Status to ‘PDAU’ (Pending Authorisation)
  • IF Issuer sent Update Consent Status to ACTV (Active);
  • Update Consent Staging Table Status to ‘SUCC’ (Success)
  • Create entry in Consent Table
  • Generate Consent ID
  • Set Consent Status as ACTV
  • Send the ACCEPTED response to Issuer

Note:

  • Timeout is set at 20 seconds
  • Transaction Type: 813

27RPPDuitNow Pay

RPP performs the following:

Notify DuitNow Pay of the Consent Status

28DuitNow PayMerchant Acquirer/ System IntegratorConsent status will be parsed to Merchant Acquirer/ System Integrator as part of the webhook.
29Merchant Acquirer/ System IntegratorMerchant / BillerConsent status will be parsed to Merchant / Biller as part of the webhook.
30Merchant / BillerMerchant Acquirer/ System IntegratorMerchant / Biller shall provide an acknowledgement back to Merchant Acquirer/ System Integrator.
31Merchant Acquirer/ System IntegratorDuitNow PayMerchant Acquirer/ System Integrator shall provide an acknowledgement back to DuitNow Pay.