Page History
synopsis
The counterparty is defined within FX as the opposite party in a currency transaction. Therefore if a participant is consuming liquidity and entering bids on quotes (the participant will often be referred to as a buyer), within the MarketFactory framework such a participant is identified as a 'Taker'. The counterparty to the example given would be a participant providing liquidity to the consumer (referred to commonly as the seller) known as a within the MarketFactory Framework 'Market Maker'.
Configuration
If configured to do so, Whisperer will populate the counterparty Counterparty field of the TradeCapture message with TradeCaptureMessage with a JSON string containing any known counterparties counterparty attribute contained in the execution report. The set of all counterparties is configured on a per-instance basis and applies to all venues in the instance. The feature is either on or off for all venues in an instance.Any Venue Execution Report. Any string-type FIX tag and any partyRole, as well as partySubIDType, can be included.The intention is to normalise presentation of counterparties to allow customers to pick and choose the information they're interested in
| Info | ||
|---|---|---|
| ||
Where Counterparty handling is employed, the feature becomes absolute and operates across all Feeds/Connections on a per-instance basis, and cannot be isolated to individual sessions (it is either on for all connections, or off for all connections). |
| Warning | ||
|---|---|---|
| ||
The data provided in the JSON string is not Normalised, thus per-venue variations in field usage must be understood by the Customer. |
Examples of the field information that can be included withinTradeCapturemessage within the TradeCaptureMessage are outlined below. The table below is not exhaustive as many venues use custom Fix Tags to convey a significant amount of counterparty information
| Note | ||
|---|---|---|
| ||
| Replace this table with relevant examples. |
| Number | Fix Tag | Name | Description | JSON Example |
|---|---|---|---|---|
| 1 | "17" | "ExecID" | Unique identifier of execution message as assigned by sell-side (broker, exchange, ECN) (will be 0 (zero) for ExecType (50) =I (Order Status)). Uniqueness must be guaranteed within a single trading day or the life of a multi-day order. | |
| 2 | "30" | "LastMkt" | Market of execution for the last fill, or an indication of the market where an order was routed. | {"LastMkt":{"ID":"Hotspot"}} |
| 3 | "375" | "ContraBroker" | Identifies the contra broker. | |
| 4 | "1" | "Account" | Account mnemonic as agreed between buy and sell sides |
| title | Caution |
|---|
Overview
Content Tools