View Source

Supported Instruments

Please refer to Supported Instruments to view across all venues.

PartyIDs

Please refer to PartyIDs to view across all venues.

Regulatory Fields

Please refer to Regulatory Fields to view across all venues.

Passthru Fields

Please refer to Passthru Fields to view across all venues.

Details

Tenors

MarketFactory recommend that Makers always reference the provided value dates in order to correctly price 360T requests.

For Swaps, the Far leg tenor is relative to the Near leg, rather than representing a date WRT Spot as per market convention:

20200202-13:34:17.022155046 RX 8=FIX.4.4|9=555|35=R|34=118|49=360T_RFQ_TEST|52=20200202-13:34:16.959|56=MF_RFQ_TEST|131=35490095-MarketFactory.TEST|828=65| 6215=6M|6216=1M|7070=20200205|7611=2|14001=5|14003=3|146=1|55=EUR/USD|48=EZHPPZCSQSC8|22=4|454=2|455=EZ0HL6Y6WL59|456=4|455=EZMBWZSKXQJ2|456=4|461=SFCXXP|167=FOR|537=1|54=1|38=1000000| 64=20200805|193=20200908|192=1000000|15=EUR|1=MarketFactory Comp1.TEST|40=D|126=20200202-13:36:28.943|453=3|448=MarketFactory.TEST|447=D|452=35|448=MarketFactory Comp1.TEST|447=D|452=1|448=MFCOMP1.Treasurer1|447=D|452=11|553=MFCOMP1.Treasurer1|7071=FX-STD|7074=Y|10=089|

FWD, NDF, SWP, NDS requests with allocations (360T "Trade on Behalf", TOB) never include tenor codes, Whisperer will always pass such requests through as Broken-dated.
In the "Classic" applet, User IMM dates (March, June, September and December) are passed through as specific tenors. In the Bridge UI however, the same selections are delivered as broken dates.
Note also that in UAT at least, 360T Tenors via the Bridge are currently subject to change.

FX Block Trading Overview

Whisperer Enterprise aggregates allocations into distinct legs grouped per LegSettlDate/ LegSettlType, as per standard market convention across most venues.

360T Block Trades are a simple list of individual allocations with no direct grouping by date.

Details of the Whisperer transformation of the Block trades are as follows:

Technical Workflow

When the Whisperer API receives a Block QuoteRequest from 360T, it performs a deterministic netting process to simplify the request for the client:

Allocation Identification: Whisperer identifies all constituent allocations within the incoming request.
Per-Leg Netting: Allocations are netted per value date (leg) to determine the net quantity for each specific date.
Side Determination: Whisperer calculates the aggregate LegSide across all legs to define the global direction of the request. Note that all 360T Block requests are one-way (strictly Buy or strictly Sell).

Client Pricing Logic

To provide an accurate quote for a multi-leg block, clients must follow a specific pricing sequence:

Determine Aggregate Trade Side: Net the leg quantity across all legs to identify the overall direction of the trade.
Price the Spot Component: Use the aggregate trade side to determine the correct side (bid or offer) and value for the Spot rate.
Calculate Leg-Specific Forward Points: For each individual leg, reference its specific LegSide to determine the appropriate side and value for forward points.
Compute All-in Price: The final Quote for each leg is the sum of the global Spot rate and the leg-specific Forward Points (Spot + Forward Points = All-in Price).

Upon receiving the client's response, Whisperer uses the original allocation side to populate the correct price field in the 360T Quote message: either LegBidPx (Tag 681) or LegOfferPx (Tag 684).

MarketFactory Gateway Attribute Mapping

The following table details how the MarketFactory gateway maps and handles specific Block Trade attributes between Legs and Allocations:

Attribute	MF Leg Attributes	MF Allocation Attributes
Number of legs/ Allocations	`NoLegs` (Tag 555): Determined by the total number of unique LegSettlDate values.	`NoLegAllocs` (Tag 670): Determined by the number of 360T allocations sharing the same LegSettlDate.
Quantity	`LegOrderQty` (Tag 685): The aggregate netted quantity of all legs sharing a specific LegSettlDate.	`LegAllocQty` (Tag 673): The individual quantity of the specific allocation, specified in terms of LegSide. Note: This value can be negative.
Regulatory	`NoLegRegulatoryFields` (Tag 20060): Group containing regulatory data mapped at the leg level.	`NoLegAllocRegulatoryFields` (Tag 20080): Group containing regulatory data mapped at the individual allocation level.

For detailed field support, please refer to the Regulatory Fields section for the supported LegRegulatoryKey and AllocRegulatoryKey per FIX message.

Certification

360T requires that the MTF certification is done with the specific algo-id that is to be used in production.

As a sidenote to this, if a client would like to add an algo id in the future, this will also require a further conformance test for the MTF side to verify the algo id.

Forward Time Options

Clients interested in trading Forward Time Options should be on Whisperer schema version 19457 or later.

Please take note of the following when trading Forward Time Options:

SecurityType - Should be FTO in SecurityType and LegSecurityType.
TimeOptionStartTenor - Conditionally required to specify the start of the settlement period in standard tenor.
TimeOptionStartDate - Conditionally required when TimeOptionStartTenor = BKN to specify the start date of the settlement period.
LegSettlType - Specifies a standard tenor for the end of the settlement period. This is a required field when trading Forward Time Options.
LegSettlDate - Specifies the end date of the settlement period in a Forward Time Option. Conditionally required when LegSettlType = BKN.

Please refer to 2025-02-18 - Whisperer API Upgrade to v19457 for further info.