CDE Self-Service Real Time Pre-Payment Authorisation and Post Payment Notifications

CDE was decommissioned at the end of February 2022 and is no longer an active test environment. All information related to CDE was at a point in time only, but continues to be made available for historical reference purposes.

Table of Contents


Overview

The Self-Service Real Time Pre-Payment Authorisation and Post Payment Notifications Tool is provided to Payment Providers to act as a Participant to initiate a Bilateral Demand Settlement Instruction via upload of a configurable CSV file which is consumed and validated by the CSP.

By updating the field details of a Bilateral Demand Settlement Instruction Request (sett_105) message in the CSV file, developers are able to perform test scenarios for payment authorisation of a matched Bilateral Demand Settlement Instruction.

This service allows developers to submit a fixed CSV file containing the Bilateral Demand Settlement Instruction information using a cURL command to a REST endpoint.

The REST endpoint translates the CSV file to a ISO XML message (Bilateral Demand Settlement Instruction Request (sett_105)) which is then submitted to the CSP.

The Self-Service Tool will be provided to Payment Providers to act as a Participant to initiate the Bilateral Demand Settlement Instruction workflow and where ‘matching’ is successful, the Payment Provider subsequently receives a Funds Obligation Request (sett_133).

When a Bilateral Demand Settlement Instruction is initiated during Batch Settlement, processing of the request will be delayed until Batch Settlement completion.

The Self-Service Tool will allow for a Payment Provider to facilitate development and testing of Funds Obligation Request (sett_133) as a result of their action to initiate the Bilateral Demand Settlement Instruction workflow on behalf of a Participant, This can be achieved by the upload of a ‘CSV’ file for a Bilateral Demand Settlement Instruction.

Bilateral Demand Settlement Instructions submitted via the Self-Service Tool are restricted to the scenario where Sender Actor is the Receiving Actor and the Credit/Debit Indicator is Debit (DBIT) and therefore the Payment Provider initiating the tests (and linked to the participant) will be payer. The Receiving Actor on the Bilateral Demand Settlement Instruction will be paying funds for the receipt of units being transferred into their holding, therefore the Funds Obligation Request (sett_133) received by the Payment Provider will require their acceptance/rejection.

The Receiving Actor on the Bilateral Demand Settlement Instruction will be paying funds for the receipt of units being transferred into their holding, therefore the Funds Obligation Request (sett_133) received by the Payment Provider will require their acceptance/rejection.

If the CSV submitted by the Payment Provider is invalid due to errors in the business validity, an Invalid Transaction (comm_808) is received.

If the CSV submitted by the Payment Provider is invalid due to errors in the file format or schema validity, a rejection from the Self-Service Tool is received. Both the rejection and success responses for the Self-Service tool are delivered to the REST endpoint, where it is converted to a JSON response. 

On success, the CSP sends a Settlement Instruction Status Advice (sett_109) message to the Self-Service tool and a Settlement Instruction Allegement Notification (sett_110) to the Bilateral Demand Settlement Instruction Auto-Responder using the details from the original Bilateral Demand Settlement Instruction Request (sett_105). For further details, refer to the Bilateral Demand Settlement Instruction Process.

Based on the Settlement Instruction Allegement Notification (sett_110) received, the Bilateral Demand Settlement Instruction Auto-Responder sends a matching Settlement Instruction Request (sett_105) to the CSP.

This enables the CSP to match the Bilateral Demand Settlement Instructions (sett_105), resulting in a Settlement Instruction Response (sett_106) being sent to the Self-Service Tool and Bilateral Demand Settlement Instruction Auto-Responder. The CSP sends a Funds Obligation Request (sett_133) to the ‘paying’ Payment Provider and ‘receiving’ Payment Provider. For further details, refer to the Payment Provider Authorisation for RTGS Payments Process.

Where authorisation is required the Funds Obligation Request (sett_133) will have a Authorisation Reason value of Real Time Payment Authorisation (RPAU) otherwise the value Real Time Payment Notification (RPNO) will be provided.

The paying Payment Provider is then able to submit a Funds Obligation Status Advice (sett_135) to the CSP, advising that a payment request has been accepted or rejected.

On successful completion of RITS processing, the CSP sends both the paying and receiving Payment Provider a Funds Movement Notification (sett_137), advising them that the real time payment has been successfully processed.

On unsuccessful completion of RITS processing, the CSP sends a Transaction Acknowledgement Advice (comm_809) to both the paying and receiving Payment Provider, advising them that the real time payment instruction or RITS payment request has not been processed.

The sample below is provided as a reference; additional information on the column names and elements present in the CSV can be found on the Payment Provider Authorisation for RTGS Payments Functional Specification.

Sample Template

The file below contains a Excel file template which is used to build the CSV submitting to the cURL. 

When populating the CSV, the developer is required to ensure:

  • The message includes the appropriate fields as populated in the attached template; and
  • Supplied dates are valid business dates.
 Download Sample Data

CSV files submitted to the CSP must be encoded in UTF-8 not UTF-8-BOM. For further details refer here.

Self-Service Bilateral Demand Settlement Instruction Template.zip

Connection details

Prior to establishing connection to the CDE, Payment Providers will need to generate and submit a Certificate Signing Request and acquire the ASX root / issuing CA public key (instructions are available on the FTP)Payment Providers are also required to populate the CSV sample file above.

CSV files submitted to the CSP must be encoded in UTF-8 not UTF-8-BOM. For further details refer here.

The below code snippet demonstrates how to establish connection to the Self-Service Real Time Pre-Payment Authorisation and Post Payment Notifications:

Self Service Real Time Pre-Payment Authorisation and Post Payment Notifications
curl
    // Verbose output
    -v
                 
    // ASX’s CA’s public keys in pem format
    --cacert /c/path/to/file.pem
                
    // File containing the certificate of the client machine
    --cert /c/path/to/file.cer
     
    // Private key of the client certificate provided in cert option
    --key /c/path/to/file.key
             
    // The URL of Payment Provider's self-service real time pre-payment authorisation and post payment notifications
    "https://cde-trade-ingest.asx.com.au:5XXX/xmlIngest/sett105" 
                 
    // Header option to accept json format (not the same as the CSV file)
    -H "accept: application/json"
                 
    // Header option to tell curl command that it will be form-data in other words file as input
    -H "Content-Type: multipart/form-data"
                 
    // The input CSV file to be sent as part of the request
    -F "file=@/c/path/to/file.csv"

In the above code fragment:  

  • URL: The URL for Self-Service Real Time Pre-Payment Authorisation and Post Payment Notifications is the same as the Trade Ingest API, cde-trade-ingest.asx.com.au. The local host DNS needs to be reconfigured to 203.4.179.118 to ensure correct routing.  
  • Port: The port number exposed for the Self-Service toolThe port will take the format of 5XXX and will be provided to the Payment Providers via email.




Related Pages:

There are no related labels.

Browse Popular Pages:

No labels match these criteria.



This document provides general information only. ASX Limited (ABN 98 008 624 691) and its related bodies corporate (“ASX”) makes no representation or warranty with respect to the accuracy, reliability or completeness of the information. To the extent permitted by law, ASX and its employees, officers and contractors shall not be liable for any loss or damage arising in any way (including by way of negligence) from or in connection with any information provided or omitted or from anyone acting or refraining to act in reliance on this information.

© 2022 ASX Limited ABN 98 008 624 691