flow-4
This is a mandatory step for the following scenarios where the Request-to-Pay status needs to be updated 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:
|
25 | Issuer | RPP | Issuer performs the following:
Note:
|
26 | RPP | Issuer | RPP performs the following:
If any Message Validation fails, RPP will:
If any Business Validation fails, RPP will:
If all validations are successful, RPP will:
Note:
|
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. |