FIX applications connecting to TT FIX services are required to complete TT's FIX Certification. Successfully completing the FIX Certification process will ensure that your FIX application works as expected in our live production environment.
FIX applications can complete TT's FIX Certification through five easy steps:
UAT FIX client connectivity is available via the Internet or Stunnel (secure Internet).
TT supports SSL-wrapped TCP connections for FIX connections. TT encrypted FIX utilizes server-side certificates only, similar to how most Secure HTTP (https) websites are implemented. Client certificates are not utilized or checked; client authentication occurs at the FIX protocol level utilizing SenderCompID in FIX tag 49 and password in FIX tag 96.
If your FIX engine natively supports SSL encryption, please consult the documentation for your FIX engine for configuration details. TT provides the stunnel.zip file which contains the TTFIX.crt. This file contains the public certificates utilized by the TT Platform's FIX endpoints for customers' use to minimize the risk of a Man-in-the-Middle attack.
If your FIX engine does not natively support SSL encryption, TT recommends using the open source stunnel proxy to implement the SSL encryption wrapper. Stunnel is available from https://www.stunnel.org/ and supports multiple operating systems, including Linux and Windows. Stunnel encrypts only the individual FIX connection, rather than implementing a full VPN tunnel as was traditionally used to encrypt FIX.
Your company on-premises DNS services must be able to access public DNS entries below pending the connection method:
|FIX Drop Copy||fixdropcopy-ext-uat-cert.trade.tt: 11501||fixdropcopy-ext-uat-cert.trade.tt: 11701|
|FIX Order Routing||fixorderrouting-ext-uat-cert.trade.tt: 11502||fixorderrouting-ext-uat-cert.trade.tt: 11702|
|FIX Market Data||fixmarketdata-ext-uat-cert.trade.tt: 11503||fixmarketdata-ext-uat-cert.trade.tt: 11703|
|FIX Recovery||fixrecovery-ext-uat-cert.trade.tt: 11505||fixrecovery-ext-uat-cert.trade.tt: 11705|
Sample Stunnel configurations are available here.
A company administrator must add and create the FIX session in User Setup.
Adding and Configuring a FIX Session:
The administrator must add Users to Order Routing FIX sessions.
Adding a User to an Order Routing FIX Session:
The administrator must add Accounts to Back Office FIX sessions.
Adding an Account to a Drop Copy FIX Session:
Developers should begin to develop against TT's FIX spec:
Don't support a FIX tag? Need to add an unsupported FIX tag or remap a tag's value to another tag? Want to change symbology?
To assist in simplifying the integration effort, TT offers a FIX Rules Engine that allows your company's administrator to define rules as well as symbol mappings.
Administering FIX Rulesets:
Configuring FIX Rules:
Defining Symbol Mappings:
The FIX Certification process aims to meet each client's specific testing needs. We encourage the client to run through testing scenarios that would closely resemble behavior specific to their application in Production. As such, the client should submit orders with the same characteristics as would be expected in Production (order types, TIFs and exchanges).
To provide some structure and guidance during the conformance process, we have provided a basic test outline for both Drop Copy and Order Routing FIX client apps. Please note that these are only suggestions. The outline does not cover all supported order types & TIFs. For more information on what is supported by each exchange, please see
Download the Order Routing Test Outline here.
Execution of Tests:
Download the Drop Copy Test Outline here.
Execution of Tests:
Once you have submitted your test data, our FIX Integration team will review your orders and provide relevant feedback and recommendations. We will point out certain exchange specific behaviors that you may not have been aware of. Our objective is to advise on best practices to minimize disruptions and ensure a smooth trading experience when you move into Production.
Do ensure the FIX Integration e-mail (email@example.com) is added on all corresponding emails so that someone from our global team can assist if another is not available.
When the above tests are completed, we will then request that you complete Session-Level tests. The purpose of this is to ensure your application can handle sequence number mis-matches during certain logon scenarios. This can be done in real-time by following the instructions in our TT FIX Session-level Tests document.
Once the Session Level tests are completed, we would proceed to certify you as having passed conformance for T FIX. By which you may then proceed into getting set up for Production.
Please contact our global FIX Integration team for assistance with your development needs, or by email at firstname.lastname@example.org.