ITE2 Test Tools for Payment Providers
Further details on ITE2 Test Tool availability have been provided in the April Code Drop Notes.
Table of Contents |
|---|
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 party.
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 file must not exceed 50 rows and a maximum file size of 50KB.
The CSV file 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 with notepad or similar, not Excel, as Excel will auto-format data which may result in errors.
Sample templates are provided for reference only. Users must ensure templates are correctly populated with all of the fields applicable to the message use case 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. This is not required for Self-Service Collateral Management where Transaction IDs are automatically generated for both Intra Position Movement Instruction (pldg_301) and Collateral Release Request (pldg_304).
Self-Service Tools will parse the entire CSV file and ensure a summary of errors is available to the CHESS user. The error response will specify the Transaction ID and the number of the row on which the error occurred.
Each Self-Service Tool follows a workflow that is documented in the supporting functional and messaging specification. It is advised that these specifications are viewed prior to initiating a self-service transaction.
If the CSV file submitted is invalid due to business logic validation errors an Invalid Transaction (comm_808) is received from the self-service tool.
If the CSV file submitted is invalid due to errors in the file format or schema validation errors a rejection from the Self-Service Tool is received. These responses are delivered to the REST endpoint, where a rejection from the Self-Service Tool is received.
Additional information on the column names and elements present in the CSV file can be found in the corresponding functional specification.
Connection details
Prior to establishing connection to 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 file sample in the table below.
CSV files submitted to the CSP must be encoded in UTF-8 not UTF-8-BOM. For further details refer here.
The code snippet below demonstrates how to establish a 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.
Function | Description | Egress | URL | Impersonating | Sample CSV | Tool Considerations |
The Unilateral Settlement Instruction Request (USSI) Tool is provided to Payment Providers to act as a Participant to initiate a Settlement Instruction Request. | sett_105_sese_023 | https://ite2-test-tool.asx.com.au:5000/xmlIngest/sett105ussi | Participants | The Self-Service CSV file must be populated with a Trust Amount where the Settlement Participant is a Broker (i.e. Clearing and Settlement Participant). The Trust Amount provided may be null, where applicable. If the Trust Amount is populated, the Trust Credit Debit Indicator for the trust amount must also be provided and be one of the following values:
Where the Trust Amount is zero, the Trust Credit Debit Indicator provided must be CRDT. For further details, refer to Trust Amount. | ||
The Bilateral Settlement Instruction Request (BSSI) Tool is provided to Payment Providers to act as a Participant to initiate a Settlement Instruction Request. | sett_105_sese_023 | https://ite2-test-tool.asx.com.au:5000/xmlIngest/sett105bssi | Participants | The Self-Service CSV files must be populated with a Settlement Amount that is greater than zero, where the Payment is ‘AMPT’, indicating the transaction is ‘Against Payment Settlement’. Where the Payment is populated with ‘FREE’, the transaction is Free of Payment (FOP) and a separate cash settlement may be completed outside the CSP. In this case the Settlement Amount should not be populated. | ||
Real Time Pre-payment Authorisation and Post Payment Notifications (see also Bilateral Demand Settlement Instruction) | The 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 (BDSI). | sett_105_sese_023 | https://ite2-test-tool.asx.com.au:5000/xmlIngest/sett105 | Participant |
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 Payment Providers in ITE2:
Auto-responder / Function | Description | Ingress | Egress | Used by | Impersonating |
|---|---|---|---|---|---|
Payment Provider Authorisation | 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 workflows below apply to a Paying Payment Provider where the CSP sends a Funds Obligation (sett_133) message as a part of Batch Settlement or Bilateral Demand Settlement. For a detailed breakdown of available functionality, refer to the Batch Settlement Aggregate Funds Obligation, Batch Settlement Funds Movement and Bilateral Demand Settlement Functional Specifications. Payment Providers are encouraged to submit any Payment Provider Funds Obligation Status Advice (sett_135) messages prior to 6:15pm AEST in order to ensure completion of a scenario within the same business day. Refer to ITE2 Reserve Bank Information & Transfer System (RITS) 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) message with an Authorisation 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) message Authorisation Reason values. Where a Payment Provider submits a Funds Obligation Status Advice (sett_135) message 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) message 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 |
| Paying Payment Provider |
- style