Tenors

...

• 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.

Block Pricing

When Whisperer receives a Block QuoteRequest from 360T, it needs to identify and net all allocations per value date leg, in order to determine and provide the overall LegSide in the Client QuoteRequest. All 360T Block requests are one-way.

...

Whisperer will use the resultant quote and the the allocation side of the original QuoteRequest to determine the field to populate (either LegBidPx or LegOfferPx) in the 360T quote 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.

PartyIDs

Please refer to either 360T TEX - PartyIDs, or Whisperer Enterprise - PartyIDs for the full Enterprise table across all venues.

Regulatory Fields

Please refer to either 360T TEX - Regulatory Details, or Whisperer Enterprise - Regulatory Fields for the full Enterprise table across all venues.

Passthru Fields

Please refer to either 360T TEX - Passthru Details, or Whisperer Enterprise - Passthru Fields for the full Enterprise table across all venues.