Self-Service Tools

Self-Service Tools are provided by ASX to allow the CHESS user to simulate an event or workflow that is initiated by another counterparty.

Using the Self-Service Feature

• Only one CSV file submission is accepted at a time.

• Unless stated otherwise in the tool consideration column, the CSV must not exceed 50 rows and a maximum file size of 50KB.

• The CSV must be encoded in UTF-8 not UTF-8-BOM. For further details refer here.

• Date fields must be populated in a yyyy-mm-dd format.

• CSV files should be opened into notepad or similar, not excel, as excel with autoformat data resulting in errors.

• Sample templates are provided for reference only. Users must ensure templates are correctly populated with all of the fields available in the message before submitting them to the tool.

• Self-Service Tools include the ability to specify the User Defined ID component of the Transaction ID. Users are required to populate this value, ensuring the Transaction ID is unique for each record within a CSV file as well as for the CSP. For further information, refer to Transaction IDs and Reference fields.

• Self-Service Tools will parse the entire CSV file and ensure a summary of error/s is available to the CHESS user. The error response will specify the Transaction Id and the number of the row in which the error occurred.

• Each Self-Service Tool follows a workflow detailed and supported by and documented in supporting /wiki/spaces/CSP/pages/23233045 and /wiki/spaces/CSP/pages/23233033 specifications, it is advised that these specifications are viewed prior to initiating a self-service transaction.

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

• If the CSV submitted 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 it is converted to a JSON response.

• Additional information on the column names and elements present in the CSV can be found on the corresponding /wiki/spaces/CSP/pages/23233045 specification.

Connection details

Prior to establishing connection to the ITE2, the CHESS User 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). The CHESS User is also required to populate the CSV sample file in the table below.

The below code snippet demonstrates how to establish connection to the 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
    "<insert url provided in the table below>" 
                 
    // 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"

The URL for the Self-Service Tool is ite2-test-tool.asx.com.au and is listed for each tool below. The local host DNS needs to be reconfigured to 203.4.179.152 to ensure correct routing. Refer to Section 04 - Networking Details for ITEs for further information.

Auto-responders

An Auto-responder is a feature provided by ASX to help CHESS users simulate events where a Counter-party response is required. The table below details the Auto-responders available to Issuer (Registries) in ITE2:

Auto-responder / Function	Description	Ingress	Egress	Used by	Impersonating
Payment Provider Authorisation	Click here to expand In ITE2, only UIC is permitted. Paying Payment Providers must not submit a rejection Funds Obligation Status Advice (sett_135) message in response to a Funds Obligation (sett_133) message with an Authorisation Reason of Funds Authorisation (PFAU) that is received during Batch Settlement. Providing a rejection response in this scenario will cause Batch Settlement to not complete and the only remediation will be an environment reset. The below workflows apply to a Paying Payment Provider where the CSP sends a Funds Obligation (sett_133) as a part of Batch Settlement or Bilateral Demand Settlement. For a detailed breakdown of available functionality, refer to the /wiki/spaces/CSP/pages/86675272, /wiki/spaces/CSP/pages/313393513 and /wiki/spaces/CSP/pages/23233747 Functional Specifications. Payment Providers are encouraged to submit any Payment Provider Funds Obligation Status Advice (sett_135) messages prior to 6:15pm in order to ensure completion of a scenario within the same business day. Refer to /wiki/spaces/CSP/pages/1688508435 for further details. For Payment Providers, the Auto-responder will act in the role of a Paying Payment Provider, however Payment Providers may still perform testing of the relevant workflow. The Auto-responder will not immediately generate an Acceptance response for Funds Obligation (sett_133) messages that have an Authorisation Reason of Funds Authorisation (PFAU). Instead, it will generate a delayed acceptance response after 30 minutes from the receipt of a Funds Obligation (sett_133) with an Authorisation Reason of Funds Authorisation (PFAU). This will allow Batch Settlement to complete in the scenario where the Payment Provider has not accepted the Funds Obligation as part of their required business workflow. Where the Paying Payment Provider wants to accept a Funds Obligation (sett_133) with an Authorsiation Reason of Funds Authorisation (PFAU), then they must accept within 30 minutes from the receipt of the Funds Obligation (sett_133) message. No responses will be automatically generated for other Funds Obligation (sett_133) Authorisation Reason values. Where a Payment Provider submits a Funds Obligation Status Advice (sett_135) to the CSP prior to the Auto-responder Acceptance response, the Auto-responder Acceptance response will be rejected by the CSP and the Payment Provider will receive a Rejected Transaction (comm_808) message. The Payment Provider should ignore this message if it doesn’t relate to a Funds Obligation Status Advice (sett_135) they submitted. The rules governing the Auto-responder behaviour are detailed in the diagrams below: Payment Providers: Batch Settlement and Bilateral Demand Settlement Payment Providers: Batch Settlement Bank Funds Transfer	sett_133_camt_089	sett_135_camt_090	Payment Provider	Paying Payment Provider