ITE1 Self-Service SRN Enquiry

Table of Contents


Overview

The Self-Service SRN Enquiry Tool is provided to Issuer (Registries) to facilitate and manage SRN Enquiry test scenarios cases acting on behalf of Participant via upload of a configurable SRN Enquiry Request (hold_217) CSV file using a cURL command to a REST endpoint, which will be consumed and validated by the CSP.

The REST endpoint translates the CSV file to an ISO XML message (SRN Enquiry Request (hold_217)) which is then submitted to the CSP.

To leverage the Self-Service SRN Enquiry Tool, a Registration Identifier (RGID) is required. An RGID can be generated through /wiki/spaces/CSP/pages/25395254 via the ITE1 Self-Service Bulk Account Creation Tool.

The Self-Service Tool supports both single and multiple SRN Enquiries.

This can be achieved by uploading 'CSV' file/s to trigger an SRN Enquiry, if the SRN is not supplied and Security Code and Registration Identifier (RGID) is populated (to create an RGID, the ITE1 Self-Service Bulk Account Creation tool can be utilised);

The maximum CSV file size is 50 kB and the maximum number of records accepted by the Self-Service Tool input via a CSV file is 50 records. The CSV file will be rejected if either of these parameters are exceeded.

The Self-Service Tool will parse the entire CSV file and ensure a summary of error/s is available to the CHESS user. If a single record is invalid due to errors in the file format, business validity or schema validity, the entire CSV file will be rejected.

On success, an SRN Enquiry Status Advice (hold_218) will be sent back to the Participant, an Account Notification (acct_002) and SRN Enquiry Request (hold_217) will be received by the Issuer (Registry).

The Issuer (Registry) can choose to Accept or Reject the SRN Enquiry Request (hold_217) by providing an SRN Enquiry Status Advice (hold_218) to the CSP. Upon receiving the SRN Enquiry Response (hold_219), the Issuer (Registry) will receive an SRN Enquiry Status Advice (hold_218).

If the Issuer (Registry) accepts the SRN Enquiry Request, the Participant will receive the SRN Enquiry Response (hold_219) and Issuer (Registry) will receive the SRN Enquiry Status Advice (hold_218).

If the Issuer (Registry) rejects the SRN Enquiry Request, the Participant and Issuer (Registry) will receive the SRN Enquiry Status Advice (hold_218).

Where the SRN Enquiry Request is pending authorisation for six days or more, the CSP will cancel the SRN Enquiry Request as part of ASX Housekeeping.

If the CSV submitted by the Issuer (Registries) on behalf of the Participant is invalid due to errors in the business validity, an Invalid Transaction (comm_808) is received.

If the CSV submitted by the Issuer (Registries) on behalf of the Participant is invalid due to errors in the file format or schema validity, a rejection from the Self-Service Tool is received.

These responses are delivered to the REST endpoint, where they are converted to a JSON response.

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 /wiki/spaces/CSP/pages/80708481.

Sample Template

The file below contains a Excel file template which is used to build the CSV submission 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 SRN Enquiry.zip

Connection details

Prior to establishing connection to the ITE1, Issuer (Registries) 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)Issuer (Registries) 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 Tool:

Self Service Tool
curl
    // Verbose output
    -v
                 
    // Informs recipients that the client is about to send a message body in this request and wishes to receive a 100 (continue) interim response
    -H "Expect: 100-continue"

    // 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 the Self-Service Tool
    "https://ite1-test-tool.asx.com.au:5000/xmlIngest/hold217SRNEnquiry"
                 
    // 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 the Self-Service Tool is ite1-test-tool.asx.com.au. The local host DNS needs to be reconfigured to 203.4.179.146 to ensure correct routing.  
  • Port: The port number exposed for the Self-Service Tool.




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


The following macros are not currently supported in the footer:
  • style