TradingCurrency (FIX tag 1245)

CurrencyFIX 5.0 SP2

TradingCurrency (tag 1245) is a Currency field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag
1245
Name
TradingCurrency
Datatype
Currency (String)
Dialects
FIX 5.0 SP2
Messages
8

What the specification says

Used when the trading currency can differ from the price currency

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 1245

MarketDefinition · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength96
35MsgTypeBUMarketDefinition
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
1394MarketReportIDEXAMPLE
1301MarketIDXNAS
1245TradingCurrencyEUR
10CheckSum183
Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1245 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

MessageMsgTypeRequirednessWhere in the message
DerivativeSecurityListAAOptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
DerivativeSecurityListUpdateReportBROptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
MarketDefinitionBUOptionalinside the BaseTradingRules component
MarketDefinitionUpdateReportBVOptionalinside the BaseTradingRules component
SecurityDefinitiondOptionalinside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
SecurityDefinitionUpdateReportBPOptionalinside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
SecurityListyOptionalinside SecListGrp › SecurityTradingRules › BaseTradingRules
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › SecurityTradingRules › BaseTradingRules

Wire format

A three-letter ISO 4217 code. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1245 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1245];field?.name;   // "TradingCurrency"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other Currency fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix50sp2