Connectivity to the SWIFTNet Closed User Group (CUG)

Table of Contents

Addressing SWIFTNet InterAct !pilot messages

The following rules should be followed by SWIFTNet users: 

  • Messages sent by the ASX will use a Requestor of ASX’s Distinguished Name (DN), and a Responder as provided by the SWIFT User. For CDE testing using the !pilot CUG with the environment parameter of ou=cde, the ASX DN is “ou=cde,ou=asx-csp,o=xasxau2s,o=swift”. 
  • Messages sent to ASX must have the Responder as ASX’s Distinguished Name (DN) for that test environment or they will not be processed.
  • It is recommended the Requestor’s DN follows the same convention being “ou=cde,ou=asx-csp,o=<YourBIC>,o=swift” but should be the DN nominated when joining the CUG.

The following table provides a summary of the rules:


Requestor

Responder

Service (CUG)

CDE messages to ASX

ou=cde,ou=asx-csp,o=<YourBIC>,o=swift

ou=cde,ou=asx-csp,o=xasxau2s,o=swift

xasx.csp.sf!p

CDE messages from ASX

ou=cde,ou=asx-csp,o=xasxau2s,o=swift

ou=cde,ou=asx-csp,o=<YourBIC>,o=swift

xasx.csp.sf!p

ITE1 messages to ASX

ou=ite,ou=asx-csp,o=<YourBIC>,o=swift

ou=ite,ou=asx-csp,o=xasxau2s,o=swift

xasx.csp.sf!p

ITE1 messages from ASX

ou=ite,ou=asx-csp,o=xasxau2s,o=swift

ou=ite,ou=asx-csp,o=<YourBIC>,o=swift

xasx.csp.sf!p

ITE2 messages to ASXou=ite2,ou=asx-csp,o=<YourBIC>,o=swiftou=ite2,ou=asx-csp,o=xasxau2s,o=swiftxasx.csp.sf!p
ITE2 messages from ASXou=ite2,ou=asx-csp,o=xasxau2s,o=swiftou=ite2,ou=asx-csp,o=<YourBIC>,o=swiftxasx.csp.sf!p



Connecting to the SWIFTNet Closed User Group (CUG)

Network validation will be turned off in the Customer Developer Environment (CDE). Platform validation will cover schema and business rules.

The following table details the parameters of the pilot service for ASX on SWIFTNet.

Service Level Parameters
Business Service NameASX Clearing Settlement Platform (Test)
Operational EnvironmentTest
Technical Service Namexasx.csp.sf!p
BillingStandard
Use RBAC?No
Request Level parameters
Request NameAll (*)
Messaging ServiceInterAct
ModeStore-and-Forward
Use Non-Repudiation?Yes
Use SWIFTNet Copy?No
Direction 
  • Administrator to Participant
  • Participant to Administrator

This is a Store and Forward service where the correspondent will receive the message from their own SnF queue designated for this service.

While a BIC is used for MT addressing on the SWIFTNet FIN network, a Distinguished Name including "o=<YourBIC>" is used for MX addressing on the SWIFTNet InterAct network.

Subscribing to the service(s)

Before messages can be received within the ASX SWIFTNet service, a subscription to the service provided by swift.com is required. This application must be undertaken by an individual with access to SWIFT ordering online services and the appropriate permissions granted by their swift.com administrator. The following steps are required:

  1. Go to www.swift.com and select 'Ordering and Support'.

     Click here for screenshot...

  2. Select 'Order Products and Services'.

     Click here for screenshot...

  3. Select 'Market Infrastructure'.

     Click here for screenshot...

  4. Scroll down to 'ASX Clearing Settlement Platform (Test)' and select 'Subscribe'.

     Click here for screenshot...

  5. Log into swift using the applicable credentials. For additional help, refer to SWIFTNet Connectivity to the ASX.

     Click here for screenshot...

  6. The ASX service form will be displayed. Complete as follows:
    1. Expand the 'Registered customer information' box and verify the default details. 
    2. Under 'Order Information', enter an Order Reference. Any relevant name may be used as this is an open text field.
    3. Under 'Institution that your order for', select the BIC that is to be subscribed into the ASX service.
    4. Under 'Preferred implementation date', select a date for activation on SWIFTNet. This is the date from which messages can be sent / received within this service / CUG. Note: The earliest date is always the weekend after the next (i.e. less than 2 weeks).
    5. Under 'SWIFTNet Closed User Group Information', update the default value in the SWIFTNet Address with "ou=cde,ou=asx-csp,o=<YourBIC>,o=swift" and 'CUG Category' with "Participant". 
    6. Click on 'Advanced' to expand the category
    7. Under 'SWIFTNet Closed User Group Information', Distinguished Name (DN) will need to be defined as the address used on SWIFTNet. When the ASX sends a message, this is the address that will be used. By default, the DN has two levels: "o=<YourBIC>,o=swift", however this needs to be changed.
      1. The Participant's DN will have a minimum of 4 segments with each segment separated by a comma. The DN is written entirely in lowercase and without any spaces. For Level 1 Organisation, insert "o=swift". For Level 2 Organisation, insert "o=<YourBIC>". The 1st Level 3 Organisation Unit segment is the ASX service name of "ou=asx-csp". The 2nd Level 3 Organisation Unit segment is the optional test environment of "ou=cde". The Participant may add further Level 3 Organisation Unit or Level 4 Common Name segments as required for their internal routing.
      2. The Administrator's DN for CDE testing is "ou=cde,ou=asx-csp,o=xasxau2s,o=swift".

    8. 'CUG Category' should remain as "Participant".

       Click here for screenshot...

  7. The 'Traffic Routing for Store and Forward Service' is important. It defines the central routing rules for the delivery of messages. Although default routing rules and queue names exist, SWIFT recommends specific rules for this service. 

    Routing will be based on Requester DN, Responder DN, Request Type and Rule Order. Based on this information, messages will be routed to a specific 'Full Queue Name'. 

    The SWIFT recommendation for queue name and routing is as follows:

    1. Click on the advanced button.
    2. Change the 'Full Queue Name' to "<YourBIC>_asxcsp!p".
    3. Leave the 'Requester DN' as an asterisk for messages coming from ASX .
    4. Change the 'Responder DN' to "*,o=<YourBIC>,o=swift".
    5. Leave the 'Request Type' as an asterisk to allow for future message types within this service.

       Click here for screenshot...

  8. As delivery notifications are not required, ignore the 'Queue Name' section.

     Click here for screenshot...

  9. The subscription to the service is completed. Verify the data entered and click 'Continue'.

     Click here for screenshot...

  10. Step through the remaining screens and submit the order. An email confirmation of the order will be sent advising of the activation date.



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