These FIX recommended practices provide guidance on the rejection scenarios of the FX market and communicating of the reason for rejection. Using FIX with a defined […]

These recommended practices define the usage expectations for the FIX fields that describe the final destination point of an execution (tag 30), the capacity of the […]

This document contains guidance on using FIX standards (specifically the FIX Protocol and MMT) for transmitting and using post-trade transparency data in European securities. This document […]

This document provides guidance on using the RoutingGrp component on FIX Advertisement(35=7) messages for selectively targeting or blocking firms from receiving trade advertisements.

Guidance on usage of the FIX Protocol for using self-match prevention features on exchanges, including the provision and usage of self match prevention identifiers and instructions. […]

This document covers securities settlement status message flow for communicating the settlement status of a security transaction.  As an extension of the existing FIX Allocations and […]

The purpose of this document is to define industry practices for the establishment and certification of FIX and non-FIX connectivity between trading counterparties and to highlight […]

This document sets out a series of topics that should be addressed in any project that intends to use FIX for a continuous workflow over an […]

The FIX Asia Pacific Technical Subcommittee recommends how to communicate a BCAN (Broker-to-Client Assigned Number) using FIX fields for Hong Kong ID regime.

2020/11/19 – Errata version of CAT-FIX Mapping Phase 2A (Equities) messages based on CAT Reporting Technical Specifications for Industry Members Version 2.2, dated 24th June 2019.  […]

(Master) SPSA (Special Segregated Account) IDs were introduced by HKEx for the sole purpose of pre-trade checking for sell orders. This document provides a proposed solution […]