Skip to main content

flow-5

StepSenderReceiverProcess
24CustomerIssuer
Customer performs the following:
  • Confirm Transaction Information
25IssuerRPP
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
26RPPIssuer
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
27RPPDuitNow Pay
RPP performs the following:
Notify Merchant of Update Payment Status via DuitNow Pay
28DuitNow PayMerchant Acquirer/System IntegratorPayment status will be parsed to Merchant Acquirer/System Integrator as part of the webhook.
29Merchant Acquirer/System IntegratorMerchant/BillerPayment status will be parsed to Merchant/Biller as part of the webhook.
30Merchant/BillerMerchant Acquirer/System IntegratorMerchant/Biller shall provide an acknowledgment back to Merchant Acquirer/System Integrator.
31Merchant Acquirer/System IntegratorDuitNow PayMerchant Acquirer/System Integrator shall provide an acknowledgment back to DuitNow Pay.
32RPPAcquirer
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
33AcquirerRPP
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
34IssuerMerchantIssuer to display the result to customer and redirect customer back to merchant portal.