MEFF Exchange API Mapping

Exchange API Mapping for MiFiD II

To support MiFiD II, MEFF Gateway 7.18.25 and higher supports the LSE and IDEM exchange API fields described in the following table. The valid values are entered in the client trading application for each of the following fields and sent to the exchange by the TT Gateway.

X_TRADER®/TT User Setup Field

Sent to Exchange as...

Description

Mandatory for Order Routing?

Direct Electronic Access Tag 1724-OrderOrigination

Indication of whether or not the order is sent from direct/sponsored access, or from another source. Valid values: 

  • 5: True*
  • null: False

No

Trading Capacity

Tag 29-LastCapacity

Indication of dealing on own account (DEAL), matched principal (MATCH), or any other trading capacity (AOTC). Valid values: 

  • 4: Market Maker (DEAL)
  • 3: Matched Principal (MATCH)
  • 1: Client (AOTC)

Yes

Liquidity Provision Tag 2594-OrderAttributeType

Indication of market making. Valid values: 

  • 2: True
  • null: False

No

Commodity Derivative Indicator

 N/A

Indication of whether the order is for hedging purposes to reduce risk.

Not supported

Investment Decision

Tag 448 with 452-PartyRole = 122

Indication of who made the trading decision. A short code of up to 15 characters is sent to the exchange.

Yes

InvestmentDecisionIsAlgo Investment Decision ID Qualifier Indication of whether an algo made the trading decision. Valid values:
  • Y: True
  • N: False
Yes

Execution Decision

Tag 448 with 452-PartyRole = 12

Indication of who or what algo submitted the order. A short code of up to 15 characters is sent to the exchange.**

Yes

ExecutionDecisionIsAlgo Execution Decision ID Qualifier

Indication of whether an algo submitted the order. Valid values: 

  • Y: True
  • N: False
 Yes

Client

Tag 448 with 452 PartyRole = 3-ClientID

Identification of the customer. Valid values:***

  • 0 – Own account orders.
  • 1 – Aggregated orders. Associated to flag “AGGR”
  • 2 – Pending allocation. Associated to flag “PNAL
  • a Shortcode value

No

FFT4

N/A Used for free-form text or non-standard exchange fields.

No

FFT5

N/A Used for free-form text or non-standard exchange fields.

No

FFT6

N/A Used for free-form text or non-standard exchange fields.

No

Notes:

          • *If the order has been marked as "true" in Direct Electronic Access, then: set Client ID to different from "0", Investment Decision ID equal to"0", and Trading Capacity to "AOTC".
          • **When execution has been realized directly by the client, then: set Direct Electronic Access to "true", Client ID different from "0", Investment Decision ID equal to "0", and Trading Capacity to "AOTC".
          • ***If the Client Identification Code is "0", then:  set Investment Decision ID to non-zero, Trading Capacity to DEAL or MTCH. If the Client ID is different from zero, then set Trading Capacity to "AOTC" or "MTCH."