With this Newsflash, we would like to draw your attention to two significant upcoming technical changes, namely (1) the mandatory implementation and usage of new ETI requests and (2) the decommissioning of the payload TLS encryption version 1.2.
(1) Decommissioning of Deprecated ETI Order Entry Requests
Milestones:
Old ETI Order Request Decommissioning:
Simulation: 23 March 2026 (T7 Release 14.1)
Production: 18 May 2026 (T7 Release 14.1)
Overview:
Five new ETI order management requests were introduced to align order layouts across T7 exchanges, combine simple and complex layouts into one request and rearrange fields for efficiency and improved latency.
These updated requests were introduced in addition to the original ETI requests with the aim of ultimately deprecating and finally decommissioning the original requests.
Deprecation and Decommissioning:
Within the Release Notes for T7 Release 13.1, clients were informed that the old Single and Multi-Leg requests were marked as deprecated in all technical documentation and would be finally decommissioned with T7 Release 14.1, taking place in mid-2026.
The following deprecated requests will be technically removed with T7 Release 14.1:
Request Name | Request ID |
New Order Single | 10100 |
New Order Single (short layout) | 10125 |
Replace Order Single | 10106 |
Replace Order Single (short layout) | 10126 |
Required Action:
Clients using the deprecated Single and Multi-Leg requests are strongly urged to adapt their order entry software to only utilize the five new requests, as soon as possible. As the new order requests are already in production, clients may begin this transition immediately and do not need to wait until the introduction of T7 Release 14.1.
The following requests should be implemented with T7 Release 14.1:
Request Name | Request ID |
New Order Single Or MultiLeg | 10138 |
New Order Single Or MultiLeg (short layout) | 10139 |
Replace Order Single Or MultiLeg | 10140 |
Replace Order Single Or MultiLeg (short layout) | 10141 |
Please note that the following request will remain unchanged for Cash Markets:
Request Name | Request ID |
Cancel Order Single | 10109 |
(2) TLS 1.3 for ETI LF and FIX LF
Milestones:
TLS 1.2 Decommissioning:
Simulation: 13 March 2026
Production: 27 April 2026
Overview:
An upgrade to Transport Layer Security (TLS) version 1.3 is required due to improved security features. As such, T7 will decommission TLS 1.2 for ETI LF and FIX LF gateway connections.
Decommissioning:
TLS 1.2 will be decommissioned from the T7 Release 14.0 Simulation on 13 March 2026 and T7 Release 14.0 Production environment on 27 April 2026.
Required Action:
Trading Participants currently using TLS 1.2 for ETI LF and FIX LF gateway connections must adapt both their infrastructure and applications to support TLS 1.3 before the date of decommission. As version 1.3 is already available in production, clients are strongly encouraged to upgrade immediately.
A list of the cipher suites supported by TLS 1.3 can be found in the Network Access Guide which is available on the Deutsche Börse website www.cashmarket.deutsche-boerse.com under the following link:
T7 Release 14.0 > Network Access
If you have questions or require further information, please contact us via e-mail: cts@deutsche-boerse.com.
Kind regards,
Your Client Services Team
Further information
Recipients: | All Frankfurt Stock Exchange (Frankfurter Wertpapierbörse, FWB®) Trading Participants and Vendors | |
Target groups: | Traders, Technical Contacts, Security Administration, System Administration, Nominated Persons, General | |
Contact: | Technical Key Account Manager via your VIP number or cts@deutsche-boerse.com | |
Related circular: | Xetra Circular 006/25 | |
Web: |
Market Status XETR ⓘ
XETR
The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.
Please find further information about incident handling in the Emergency Playbook published on the webpage under Data & Tech > Information Channels > Emergency procedures. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message
We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.
An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.