Rules of Engagement Home
PURPOSE AND DOCUMENT SCOPE
A3 released this document to provide an entry mechanism for market data subscription and order routing to its Electronic Trading Exchange using the FIX Protocol. The A3 Trading System provides the hardware and software needed to connect to its Electronic Derivatives Exchange. The goal of this document is to describe the message types and tags supported to successfully connect to the A3 FIX 5.0 interface.
REFERENCES TO OTHER DOCUMENTS
For detailed information on each of these fields, please refer to the FIX Protocol specifications at https://www.fixtrading.org/.
Typographical and Syntax Conventions
This document uses certain typographical conventions:
Text in this style | is used for identify Blocks of Data of any kind. |
-> | is used for indicates one level of depth in blocks of data, for example, Block Instrument. |
->-> | is used for indicates two levels of depth in blocks of data. |
->->-> | is used for indicates three levels of depth in blocks of data. |
->->->-> | is used for indicates four levels of depth in blocks of data. |
<125> | a tag number enclosed between major and minor signs indicate that the field is a “A3’ Custom field. |
Conventions for tables
Tag | FixName | Req | Format | Description | |
|---|---|---|---|---|---|
Tag Number | Field Name according to the Fix Protocol | Indicates if the field is required, possible values: | File format used | Description of Use | |
Tag Number | Num In Group | Idem | Field format used | Idem | |
-> | Tag Number | Field Name | Idem | Field format used | Idem |
<Custom Tag Number> | Name of | Idem | Idem | Description of use for custom field | |
Message Flow Conventions
In the message flow diagrams used throughout this document, messages are classified as synchronous or asynchronous according to the expected interaction pattern.
Synchronous messages represent requests for which an immediate response is expected as part of the same interaction flow.
Asynchronous messages represent notifications or events that are sent independently of a specific request and may occur at a later point in time.
Asynchronous messages are typically used by the market to broadcast events or state changes to participants and are not directly correlated to a single client request.
Certification
In order to connect to A3, a certification process must be undertaken to validate that the FIX protocol is correctly implemented and functional and non-functional requirements are met.
When a participant wants to use a DMA platform to route orders to the Exchange they should send an email to mpi@primary.com.ar to start this process.
The latest version of our ROEs and certification process are available at: https://matbarofex.com.ar/tecnologia/negociacion-electronica
Once granted it will be valid for 1 year.
Leased lines and Internet connections to the Exchange are allowed.
The list of DMA platforms currently connected to the Exchange is available at:
https://a3mercados.com.ar/productos-servicios/miembros-dma/
Connection information
MARKET TRADING HOURS
FIX Session Hours: 9.30 am - 7 pm
Trading Hours: 10:00 am -17:30 pm
FIX VERSION USED
The version protocol used is Fix 5.0.
IDENTIFICATION OF THE FIX SESSION
The exchange will provide every member with an Exchange Code, Member Code, Login Username and a Password. All messages sent by the member to the exchange should contain the provided Member Code in the SenderCompID and OnBehalfOfCompID fields. For test connections, the Member will be provided with a separate Exchange Code, Member Code, Login Username and Password. All messages sent by the Member to the exchange should also have the TargetCompID field set to the exchange’s code provided, and will have to be set to “MatbaRofex”. No more than one
FIX session can exist at the time with the same values for these fields. If a message is received with values that do not correspond with those of the session, it will be rejected and the connection closed. It should be noted that the values of these fields are inverted when the message is sent by the exchange, with respect to those sent by the client.
Interconnection agreements between markets
It is defined, according with practices used in other marketplaces, that to send orders to other markets or take orders from them, a different FIX session will be used for each direction. To send orders from Primary to another market, Primary act as initiator of a session to that market, using the FIX version and dictionary provided by the other Exchange. Those wishing to submit market orders to Primary, must start a session, in which Primary act as "aceptor" using the FIX version, dictionary and specification provided by Primary.
This allows both markets to connect, regardless of the differences between dictionaries and specifications.
IP ADRESSES
All Members connecting to the system will be provided with a production DNS name and one or more test DNS names.
TCP PORT NUMBER
Primary’s Router listens for Member connections on a TCP specific port number. This port number will be also provided by the exchange.
FIX SESSION ASSIGNMENT
FIX comp IDs and IP addresses/DNS names for connection are assigned by Primary to connecting counterparties. The process is differentiated according to the counterparty category (banks, trading firms, vendors, other exchanges, etc.). For more details, please contact Primary.
IDENTIFICATION OF INSTRUMENTS
The instruments are identified by the "symbol", which is unique in each market.