← Back to X_TRADER® Help Library

MEFF Gateway Documentation

Trader and Firm Identification

Obtaining Exchange Credentials/Membership

MEFF offers the following types of memberships:

  • Custodian Clearing Member
  • Clearing Member
  • Proprietary Trading Member

Before trading at MEFF, prospective traders must either open an account with a MEFF member or obtain a unique MEFF membership. For further details, consult with an entity member of MEFF. You will find a list on the members page at:


Additionally, you must work with the exchange to properly configure the following:

The exchange configures the following types of member IDs:

  • Non-Trader ID: The Price Server uses a Non-Trader ID to make a Price API connection to the exchange.
    • Trader ID: only receives the execution reports from the exchange for that Trader. MEFF has instituted a daily transaction limit of 60,000 orders for each Trader ID.
    • Multi-Trader ID: receives all execution reports from the exchange for the entire membership. Since the MEFF Gateway drops all unsolicited fills and orders, using the Multi-Trader ID unnecessarily will increase the amount of processing performed by the Gateway.
  • Trader and Multi-Trader IDs: The Order Server can use either of the following ID types to make an Order API connection to the exchange.

    TT recommends that customers configure the Order Server to use the Trader ID unless they exceed the daily transaction limit.

TT Direct Trader IDs

You can determine and set up any Group ID and Trader ID you like, however, you must use the Member ID as distributed by MEFF. The exchange does not require members to identify each user individually.

You must complete the following fields in Guardian to map a TTORD proxy trader to a direct trader:

  • Exchange: the TT Gateway exchange-flavor (e.g., MEFF-A)
  • Member: MEFF provides the SenderCompID (1st 4 Characters of the Trader ID). This value should be entered into the GatewayCompany parameter of the [OrderServerSession] of the hostinfo.cfg file. If the Member parameter is configured in the [OrderServerSession], its value will be used as the Member portion of the direct trader.
  • Group: a three-digit variable defined by the firm.
  • Trader: a multi-digit variable defined by the firm.

If an incorrectly mapped TTORD trader submits a trade, the MEFF Gateway rejects the transaction and forwards a No mapping for Trader TTORDXX 001 001 acct |XX001001| in database error message to the X_TRADER® Audit Trail.

If a TTORD trader submits a trade with an unrecognized account, the MEFF Gateway rejects the transaction and forwards a Trader TTORDXX 001 001 is not allowed to use account |ABC| error message to the X_TRADER® Audit Trail.

TTORD Trader IDs

The following lists how MEFF Gateways use TTORD trader IDs.

  • MEFF Gateways support TTORDs.
  • You can map multiple TTORDs to one direct exchange trader.

Each TTORD ID used to connect to and trade on the MEFF exchange must use a unique clearing account.

Order Session Identification

TT Gateways 7.16 and higher contain an enhancement that displays the exchange credential used to route all orders and fills through the exchange. This includes all order modifications and exchange rejects but does not include order actions on Hold orders and position reserve orders.

Currently, this value is available in the following locations:

  • Audit logs: appears in the ExchangeCredentials column
  • Order Server logfile
  • FIX Adapter 7.8: via Tag 18216 (ExchCred)

The exchange credential will be available in future versions of other TT client applications.

For MEFF, the exchange credential equals a combination of FIX Tag 49 (SenderCompID) as listed in the GatewayCompany parameter and the FIX Tag 50 (SenderSubID) listed in the GatewaySessionId parameter listed in the [OrderServerSession_X] section used to route the order.

This information is available for all actions on orders and fills including incomplete orders/fills.