IT Documentation by type

Euronext informs customers that a new version of the Saturn Regulatory Reporting Solution is available in P-EUA with the production released in July 2019.
This release of Saturn covers the new “Transaction Recovery” functionality.

This document describes the Euronext Dublin On Exchange Off Book trade reporting facility. The objective is to give an overview of the functionality as well as the main system rules associated to these facilities. For more detailed information Euronext Members have to refer to the related documentation described below.

Euronext has developed a suite of reporting services to support the implementation of MiFID II. These services will be operated via a new tool named Saturn, which is composed of a Web API and a Webbased User Interface (UI) offering a number of features to clients. This document describes how to use the Saturn User Interface (UI) as a support of the global reporting services provided by Euronext.

Please note that this version of the User Guide covers the Transaction Reporting, ARM functional services as well as Admin features and Off Book On Exchange (OBOE) services..

Sample file for Saturn OBOE upload file

Sample file for Saturn APA ARM upload file

This document describes the Euronext Global Reporting Solution concerning the Euronext APA/ARM Services as well as the transaction modalities for Euronext Members not subject to MIFIR and the Cleared OTC Trade Facility. The objective is to give an overview of the services and functionalities. For more detailed information Market participants have to refer to the related documentation described below.

This purpose of this document is to provide guidance to Euronext Clients on the application of the requirements for Transaction Reporting (RTS 22) and Order Record Keeping (RTS 6), for the activity conducted on Euronext Regulated Markets.

TradeManagerAPI – 1.8.wdsl (Web Service File) – MiFID II

TradeManager – 1.8.xsd (Schema File) – MiFID II

Short and long code mapping submission process to Euronext Saturn for purposes of Order Storage
under MiFID II

This specification document is related to the Euronext Saturn Web Services, part of Euronext’s Reporting Services. Saturn offers a REST API which is used to access the services of the gateway. The purpose of this document is to describe the technology and the supported messages.

EURONEXT DERIVATIVES CCG IP CONFIGURATION FOR UTP-D V-EUA

Euronext’s UTP has a built-in protection mechanism that restricts the total number of messages (of all types) that a trading session can submit per second. In UTP-Derivatives, each session on the Common Customer Gateway (CCG) has a session limit of 100 msgs/s. Next to that, an inbound order throttle can be set at an individual contract level or for some contracts (product group). If the throttle for a contract is set to n messages per second, then the Trading Host will allow a maximum of n messages per second in a certain second for an ITM for that contract.

This document provides a functional overview of the Request for Cross (RFC) trading facility which is available for Euronext commodity, equity and index options.

Production & DR OEG Drop copy IP addresses for Cash OEG, OEG DC per Optiq Segment Name and Partition ID and for derivatives per CCG name.

Request For Cross (RFC) Frequently Asked Questions

This document provides guidelines on how to write effective and efficient applications using the UTP protocols for Order Entry (Binary or FIX 5.0) and Market Data (XDP). It is important to be aware that this document is not a replacement for, but rather a complementary document to the UTP Reference Manuals (see related documentation below). Most of the points raised in this document are concerned with the most efficient, or Exchange friendly way of performing various tasks, and the Exchange requires application developers to adopt the recommendations given where relevant.

The purpose of this document is to set out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the binary format. More specifically, it describes the structures of the technical, administrative and market data messages and a precise definition for any field part of these message structures. Any message is composed by one header, one body, one trailer. The description of the CCG Derivatives protocol herein addresses all Euronext derivative-related trading engines.

This document sets out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the FIX 5.0 format. More specifically, it describes the structures of the technical, administrative and market data messages and a precise definition for any field part of these message structures. Any message is composed by one header, one body, one trailer. The description of the CCG Derivatives protocol herein addresses all derivative-related trading engines.

The purpose of this document is to provide customers with a description of the UTP-Derivatives MiFID II order entry conformance script, with scenarios for functional data conformance tests using the new MiFID II fields. Conformance testing will begin on 11 September 2017 on the P-EUA environment until 27 October 2017.

This document provides the list of errors that can be issued from the UTP Matching Engine upon receipt of request messages. Indeed, when the Matching Engine receives a request, it performs several checks on this incoming request message, and may reject it. When it does, the error is identified in the response message sent back by the Matching Engine by an error code together with an associated text in the Text [58] field.

The purpose of this document is to provide customers with a detailed description of the guidelines to follow for testing UTP-Derivatives order entry with the new MiFID II fields.

Derivatives CCG Binary Header file - MiFID II

This document details the test cases to be performed by the client in order to certify its trading software following the RISKGUARD implementation on the EURONEXT Cash and Derivatives markets.

This document details the test cases to be performed by the client in order to certify its trading software for the Request for Cross functionality implemented on the Euronext Derivatives markets .

Euronext offers to market participants a range of liquidity provider incentive programs tailored to each market (Paris, Amsterdam, Brussels and Lisbon) and aimed at improving on-screen liquidity. Specific functionalities have been implemented within the UTP Matching Engine to support these programs:

■ Market Making Orders (Mass Quotes)

■ Market Maker Protections

These features are only available via the CCG Binary interface to designated Market Makers. This document provides a functional overview of the Market Making functionalities to Members intending to develop an application using the Binary Interface to the Common Customer Gateway (CCG).

This document describes the full conformance test script for order entry on UTP-D

This document describes the drop copy conformance test script for UTP-D

The primary audience for this document are Member Developers and/or ISV’s who want to conform their application/software for drop copy on UTP-D . The drop copy conformance test is mandatory before access to drop copy is granted on the production environment.

This document details the test cases to be performed by the client in order to certify its trading software for CCG Order Entry for EURONEXT Derivatives markets.

This document provides details of the high availability and business continuity for the UTP® trading chain components, including features and elements associated to the Common Customer Gateways (CCG) for the Exchange’s Cash Markets.

This document details the steps required to be provisioned with production access to the NYSE Liffe Common Customer Gateway (CCG).

optiq_technical_note_cash_market_equities_instrument_migration_among_partitions.V1.2

This document provides you the exhaustive list of changes introduced by the implementation of the SBE Template 110 (versus SBE template version 107) on OEG and MDG messages, fields and values as well as the standing data files.

Scope and audience: This technical note intends to provide general technical information about SBE and specify the SBE implementation on Optiq®.
This document is meant to familiarize developers who will work with SBE for the first time and remind others the current rules of implementation.

Euronext would like to provide customers with further details on the current rules that apply for the design of SBE templates, and consequently the format of messages. In order to secure a smooth implementation of the coming changes on the SBE template,
Euronext is pleased to provide on the changes the rules of implementation and delivery for the upcoming releases on Optiq CASH®. Clients are strongly invited to test it in Next EUA (p-EUA) prior to the implementation of these changes in production.

This dpocument provide you exhaustive list of changes introduced by the implementation of the SBE Template 107 (versus SBE template version 105) on OEG and MDG messages, fields and values as well as the standing data files. For an explanation of the changes.

Euronext’s electronic trading platform hosts a Hybrid (Request For Execution) market model for Structured Products (incl. Warrants & Certificates and Structured Notes) formerly known as the New Warrants & Certificate market model or Quote Driven market model. This model has been developed jointly with market participants. The model presented below which manages trading of Structured Products using Liquidity Provider quotes has been approved by Euronext market authorities. On Euronext’s electronic trading platform, Optiq®, this market model is hosted on the dedicated Structured Products segment. Note that this segment also supports the trading of instruments using the Order Driven market model.

The Optiq Order Entry Gateway (OEG) provides high-speed and real-time connection to the Exchange markets. This document provides information about the High Availability (HA) and Business Continuity mechanisms for the trading chain implemented in Optiq and details of:

■ high availability and business continuity facilities supported by the Optiq trading chain

■ features of the trading chain that support client’s ability to:

– manage their sessions in cases of trading chain recovery,

– resynchronize with the Exchange if required

■ recommended practices in different cases of failure

The scope of this version of the document covers high availability and Exchange business continuity for the Cash markets hosted on Optiq.

This document provides an overview of the exchange of messages between the Optiq Order Entry Gateway (OEG), the clients’ systems and the Market Data Gateway (MDG). It includes:

■ Typical trading scenarios and the corresponding public and private messages for these scenarios, and the different cases they may cover;

■ The names and IDs of the messages sent;

■ The events that trigger the transmission of messages.

This overview is meant to provide a description of the main structures and concepts used within this document, to facilitate the review of the individual topics and cases covered within.

The messages that are sent between trading members and Optiq are referred to as private messages whereas the messages that are sent by the external broadcasting systems are referred to as public messages.

Private messages are exchanged exclusively between the clients’ system and the Optiq matching engine via order entry gateways, for example to request information from the system or to issue a command (e.g., enter an order). Private messages are also sent back by Optiq via order entry gateways (OEGs) to the client’s system to provide the information requested, or confirm that a command has been successfully executed (or not), as well as to notify of trades, etc.

Public messages are sent by Optiq via MDG to provide to all subscribing clients with anonymized Market data, such as orders entered, best limits, trades executed, market events, updated limits, etc.

The diagrams in this document express representative examples of message sequences and other scenarios can be figured out from the ones described inside that document. The details of the message contents may vary depending on the example.

The diagrams also endeavour to represent as close to reality as possible the sequence in which events and steps occur, and messages are sent. This introduction provides indication when such cases are not feasible to represent faithfully due to complexity of graphical representation.

For a complete description of the messages and their fields, please refer to the associated document:

■ Optiq Order Entry Gateway Messages Specifications SBE;

■ Optiq Order Entry Gateway Messages Specifications FIX;

■ Optiq Market Data Gateway Messages Specifications.

Euronext RiskGuard is a pre-trade risk management service providing Risk Managers at Clearing or Trading Member firms of Euronext the ability to monitor their clients' or firm's risk exposure. This document describes how to set and amend the different pre trade risk controls available through the Euronext RiskGuard web-based User Interface (UI).

This version of the User Guide is dedicated to clearing participants acting as ‘RiskGuard Clearers’. It provides a description of all the risk controls and additional features available through the RiskGuard User Interface to monitor their NCMs’ customers.

Euronext RiskGuard is a pre-trade risk management service providing Risk Managers at Clearing or Trading Member firms of Euronext the ability to monitor their clients' or firm's risk exposure. This document describes how to set and amend the different pre trade risk controls available through the Euronext RiskGuard web-based User Interface (UI).

This version of the User Guide is dedicated to Trading Member firms acting as ‘RiskGuard Members’. It provides a description of all the risk controls and additional features available through the RiskGuard User Interface to monitor their firm’s and client’s risk.

This document sets out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the FIX 5.0 SP2 format. More specifically, it describes the structures of the technical, administrative and application messages for the CCG Euronext RiskGuard (ERG) Functionality. The description of the CCG Derivatives protocol herein addresses all Euronext derivative-related trading engines.

Euronext informs about the go-live dates of the SBE template version 109 implementation in Production: Monday 6 May 2019.

The go live date in Production for the SBE Template version 109 will cover the following segments: Equities, Warrants & Certificates, Fixed Income, Bourse du Luxembourg and Index

Euronext informs that the SBE template version 109 go-live in Production has been rescheduled.

The go live date in Production for the SBE Template version 109 is postponed for the time being for the following segments: Equities, Warrants & Certificates, Fixed Income, Bourse du Luxembourg and Index.

The TRF Conversion Parameters files provide the following data to the members on a daily basis:
■ Contract referential data: Contract code, Maturity, Number of days to expiry, Daily Settlement Price,etc.
■ Pricing of Funding leg and Dividend leg: Daily accrued funding, Daily accrued dividend, Accumulated funding, Accumulated dividend, etc.

Euronext File Services is a Server providing files necessary for Euronext’s customers that have either an EMDDA (market data), SPA (Service Provider) or TPA (Trading Platform) agreement to get access to the core trading chain of Euronext. This document provides general technical information about Euronext’s File Services.

This document intends to provide general technical information about Euronext File Services.

This technical note intends to provide general technical information about Euronext’s File Services (EFS), a file service mechanism that will be used during the implementation of OPTIQ.

This document sets out the client messages specifications for Optiq® OEG using the SBE format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.  Please note that Euronext Block, and Algomi are not in scope of this document.

This document sets out the client messages specifications for Optiq OEG using the FIX 5.0 format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.

Note: Algomi is not in scope of this document.

This document sets out the client messages specifications for Optiq® OEG using the SBE format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.

This document provides details of the throttling mechanism for the Optiq® Order Entry Gateways (OEG). This document is a supporting document for other technical specifications made available for Optiq, some of which are listed in the section Associated documents.

Drop Copy is a service, providing near real-time copies of trade reports & order messages, usually used by for risk management, back-offices and compliance teams. Clients require a dedicated connection to receive Drop Copy messages, which can be setup with configuration that fits their needs. The scope of data in Drop Copy could provide client messages for various (or all of their) Logical Accesses, for one, or across different Optiq Segments. This version of the document covers activity on the Cash market only, that are in scope of Phase 2 of the migration to Optiq.

This document provides the list of errors that can be issued by the Optiq® Matching Engine upon reception of incoming private messages, occurrence of client or exchange business continuity conditions and also the errors that are issued by the Trade Reporting & Publication services.

This document provides the list of errors that can be issued by the Optiq® Matching Engine upon reception of incoming private messages, occurrence of client or exchange business continuity conditions and also the errors that are issued by the Trade Reporting & Publication services.

Euronext’s electronic trading platform hosts a Hybrid (Request For Execution) market model for Structured Products (incl. Warrants & Certificates and Structured Notes) formerly known as the New Warrants & Certificate market model or Quote Driven market model. This model has been developed jointly with market participants. The model presented below which manages trading of Structured Products using Liquidity Provider quotes has been approved by Euronext market authorities. On Euronext’s electronic trading platform, Optiq®, this market model is hosted on the dedicated Structured Products segment. Note that this segment also supports the trading of instruments using the Order Driven market model.

This document sets out the client messages specifications for TCS Optiq OEG using the SBE and FIX formats. 

The purpose of this document is to provide customers with a description of the Optiq order entry conformance script, with scenarios for connectivity, functional data conformance and high availability tests for the Phase 2 of the migration to Optiq covering the Euronext Cash markets. Please note that the DR(disaster recovery) testing will be detailed in a future version.

This document sets out the client messages specifications for Optiq OEG using the FIX 5.0 format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.    Note: Euronext Block and Algomi are not in scope of this document.

Self-Trade Prevention (STP) has been introduced on Euronext’s Cash Markets to allow Member Firms acting as Liquidity Providers to avoid trading with themselves. The STP mechanism allows customers to avoid unintentional self-trading that results from the matching of two opposite orders on the same instrument, of the same Member Firm (i.e. with the same Member Code). The mechanism applies to orders that are submitted via private messages (SBE or FIX) with the Account Type of Liquidity Provider (LP). In the event that two opposite LP orders belonging to the same Member Firm would match against each other, the mechanism cancels either the resting or the incoming order (depending on the STP Type chosen). If STP Type chosen is “Cancel Resting”, then the system enters the incoming order of the possible match, into the central order book. If STP Type chosen is “Cancel Incoming”, then no changes occur in the central order book and the incoming order is rejected.

This document provides guidelines on how to test customers’ applications against Euronext’s Optiq® Order Entry Gateway (OEG) and Matching Engine (ME) on Cash markets.

This document outlines all conformance steps required, how tests are organised and testing timelines.

This document sets out the client connectivity configuration specifications for Optiq® Order Entry Gateways (OEG). It describes the sources of data for connectivity, manner in which clients should attempt to connect to the OEGs. This document is a supporting document to the interface technical specifications.

This document provides additional information related to time stamps for Optiq OEG.

This document describes the (Auto-Mass) Cancel on Disconnect feature in Optiq. This functionality is made available on all Optiq Segments of Cash Market, and is available for management by clients for individual submitted order messages. This document provides a general description of the functionality, how it works and how it behaves in different situations of day-to-day operations and business continuity cases.  Note: This document is for informational purposes only, and should be consulted alongside its associated documents, as outlined below.    Optiq Support Desk Tel: +33 1 70 48 25 55

Email: optiq@euronext.com 

The purpose of this technical note is to provide general information about the MiFID II technical changes on UTP Derivatives. More specifically, this document aims to describe the MiFID II technical changes with regards to new fields in order entry messages and familiarise developers with how to implement these changes for the respective order entry interfaces.

An Exchange for Physical (EFP) is a transaction involving the simultaneous exchange of a futures position for a basket of shares.

EFPs based on index futures are transactions made on the basis of the difference between the index futures price and the spot price of the index. Currently, the futures leg of these transactions can be reported on Euronext’s Basis Trade Facility, with reference to a cash leg. Euronext’s new Exchange for Physical Facility enables members to trade EFPs on the CAC 40® and AEXIndex® by simultaneously exchanging index futures for the corresponding basket of underlying component securities of the index. The new EFP solution will be available for trading in a regulated environment by means of a transparent central order book supported by a liquidity-providing scheme. Trading of EFPs takes place by means of a fully automated straight-through-process, eliminating operational burdens and facilitating post-trade reporting obligations. In addition, it reduces execution risk thanks to the guarantee of the central counterparty.

Global overview of the application message flow exchanged between SLEs and Euronext’s Trade Confirmation System (TCS), and the associated broadcast messages; main rules and particularities associated with this model.

This document details the Referential Data HTTPS Server for Euronext, to be used in conjunction with the Optiq MDG Client Specifications.

The Servers provide full referential data for the Euronext markets, as well as feed configurations and intraday trades with their MiFID II flags. Users of the Euronext market data feed should use the Servers to:

- Configure feed connections every day.

- Support the referential data that is disseminated on the feed.

- Complete their list of trades.

This document details the Referential Data HTTPS Server for Euronext, to be used in conjunction with the Optiq MDG Client Specifications.

The Servers provide full referential data for the Euronext markets, as well as feed configurations and intraday trades with their MiFID II flags. Users of the Euronext market data feed should use the Servers to:

- Configure feed connections every day.

- Support the referential data that is disseminated on the feed.

- Complete their list of trades.

This document describes the files generated on a daily basis by the Optiq for the End Of Day (EOD) application and provided to the members of the Euronext Cash regulated markets.

The Euronext Optiq Market Data Gateway (MDG) provides high-speed, real-time market data for Euronext markets.

The data feed has the following high-level features:

■ Multicast technology

■ Ultra-low latency

■ MiFID II compliance

■ Cash & Derivatives message harmonization

■ Optimized feed for each type of connectivity

■ High availability

■ Reliable network solution

■ High level of scalability

■ Access to a wide range of European market data sets

This document provides detailed information about the features of the feed to support the development of client applications.

This document provides all multicast addresses required to access the Euronext Optiq® Market Data Gateway Production and Disaster Recovery (DR).

The Euronext Optiq® Market Data Gateway Production environment (PROD) is located in Basildon and the Disaster Recovery (DR) environment is located at St. Denis. The Production Primary (P) and Secondary (S) Source IP Address ranges are provided in this document for the live and standby systems as part of the High Availability mechanism.

Customers are requested to allow the Production Primary, Production Secondary and Disaster Recovery (DR) Source IP Address ranges through their Firewalls.

With the XML Standing Data files for the different Optiq Segments, customers will be able to map which instruments are available in which channel. The Optiq MDG feed configuration can be found at the end of each Standing Data file available and these will be provided on a daily basis in XML format. It is required to use the feed configuration details as part of the standing data files to connect to the feed on a daily basis.

In case a new partition is added to an Optiq Segment, customers are required to adapt to this type of change using the Optiq MDG Standing Data files that include the feed configuration details.

The Euronext Optiq Market Data Gateway (MDG) provides high-speed, real-time market data for Euronext markets.

The data feed has the following high-level features:

■ Multicast technology

■ Ultra-low latency

■ MiFID II compliance

■ Cash & Derivatives message harmonization

■ Optimized feed for each type of connectivity

■ High availability

■ Reliable network solution

■ High level of scalability

■ Access to a wide range of European market data sets

This document provides detailed information about the features of the feed to support the development of client applications.

This document provides all multicast addresses required to access the Euronext Optiq® Market Data Gateway External User Acceptance (EUA). Only shaped data is provided in the test environment. In order to ensure a Production-like test environment, separate IP addresses and ports are used to replicate the Production ‘shaped’ and ‘unshaped’ configuration.

The Euronext Optiq® Market Data Gateway Physical-EUA (P-EUA) environment is located in Basildon and the Virtual-EUA (V-EUA) environment is located at St. Denis. The P-EUA and V-EUA Source IP Address ranges are provided in this document and for P-EUA the Source IP Address ranges are provided for the live and standby systems as part of the High Availability mechanism. EUA High Availability (HA) and failover testing will only be conducted on the physical test environment (P-EUA).

Customers are requested to allow the V-EUA and P-EUA Source IP Address ranges through their Firewalls.

With the XML Standing Data files for the different Optiq Segments, customers will be able to map which instruments are available in which channel. The Optiq MDG feed configuration can be found at the end of each Standing Data file available and these will be provided on a daily basis in XML format. It is required to use the feed configuration details as part of the standing data files to connect to the feed on a daily basis.

In case a new partition is added to an Optiq Segment, customers are required to adapt to this type of change using the Optiq MDG Standing Data files that include the feed configuration details.

The purpose of this document is to describe all the specifications of Optiq™ Market Data Gateway

The purpose of this document is to describe all the technical and application messages (APA and Euronext Synapse) of Market Data Gateway (MDG) i.e. Technical messages (Start of day, End of day and Health Status), Referential messages (for quotes and for trades), application messages (APA quotes and APA full trade information) and Snapshot messages and all the related features for those messages i.e. Snapshots (message recovery), Compression (market data packet for low bandwidth connections), Shaping (bandwidth optimization), Gap detection (packet loss recovery), System failures trade, Quote retransmission (outbounded messages rebroadcasting) and Health status Production timetable (list of events during the trading day).

This document provides guidelines on how to test applications against Euronext’s Optiq Market Data Gateway (MDG) publisher. The document outlines all required conformance steps, the organization of tests, the testing timelines.

This document provides additional information related to session management, order management, MDG high availability and Exchange business continuity.

This technical note intends to provide general information about the Snapshot Service for Optiq MDG. Describing the Snapshot kinematics, this document aims to familiarize developers how to implement this recovery functionality in their feed handler to recover from packet loss, or in case of an intraday/late start.

This technical note intends to provide general technical information about LZ4 compression on Optiq®.

This document describes how to use the TCS (Trading Confirmation System), which is a Euronext web-based application for the publication and reporting functions that are available to TCS trading members.

The purpose of this document is to describe how to use the TCS functions for funds that are available to TCS trading members and fund managers through the TCS-Web Interface.