Currency (FIX tag 15)

CurrencyFIX 4.4FIX 4.2

Currency (tag 15) is a Currency field defined in FIX 4.4 and FIX 4.2. It appears in 45 message types, always optionally.

At a glance

Tag
15
Name
Currency
Datatype
Currency (String)
Dialects
FIX 4.4 and FIX 4.2
Messages
45

What the specification says

FIX 4.4

Identifies currency used for price. Absence of this field is interpreted as the default for the security. It is recommended that systems provide the currency value whenever possible. See "Appendix 6-A: Valid Currency Codes" for information on obtaining valid values.

FIX 4.2

Identifies currency used for price. Absence of this field is interpreted as the default for the security. It is recommended that systems provide the currency value whenever possible. See Appendix A: Valid Currency Codes for information on obtaining valid values.

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

A real message using tag 15

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength118
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
15CurrencyEUR
10CheckSum135
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 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 15 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
Advertisement7OptionalOptionaldirectly on the message body
AllocationInstructionJOptionalOptionaldirectly on the message body
AllocationReportASOptionaldirectly on the message body
AssignmentReportAWOptionaldirectly on the message body
BidRequestkOptionalOptionaldirectly on the message body
CollateralAssignmentAYOptionaldirectly on the message body
CollateralInquiryBBOptionaldirectly on the message body
CollateralInquiryAckBGOptionaldirectly on the message body
CollateralReportBAOptionaldirectly on the message body
CollateralRequestAXOptionaldirectly on the message body
CollateralResponseAZOptionaldirectly on the message body
ConfirmationAKOptionaldirectly on the message body
CrossOrderCancelReplaceRequesttOptionaldirectly on the message body
DerivativeSecurityListAAOptionalinside the RelSymDerivSecGrp component
DerivativeSecurityListRequestzOptionaldirectly on the message body
ExecutionReport8OptionalOptionaldirectly on the message body
IOI6OptionalOptionaldirectly on the message body
ListStrikePricemOptionalOptionalinside the UndInstrmtStrkPxGrp component
MarketDataIncrementalRefreshXOptionalOptionalinside the MDIncGrp component
MarketDataSnapshotFullRefreshWOptionalOptionalinside the MDFullGrp component
MassQuoteiOptionalOptionalinside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgementbOptionalinside QuotSetAckGrp › QuotEntryAckGrp
MultilegOrderCancelReplaceACOptionaldirectly on the message body
NewOrderCrosssOptionaldirectly on the message body
NewOrderListEOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABOptionaldirectly on the message body
NewOrderSingleDOptionalOptionaldirectly on the message body
OrderCancelReplaceRequestGOptionalOptionaldirectly on the message body
PositionMaintenanceReportAMOptionaldirectly on the message body
PositionMaintenanceRequestALOptionaldirectly on the message body
PositionReportAPOptionaldirectly on the message body
QuoteSOptionalOptionaldirectly on the message body
QuoteRequestROptionalOptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptionalinside the QuotReqRjctGrp component
QuoteResponseAJOptionaldirectly on the message body
QuoteStatusReportAIOptionaldirectly on the message body
RequestForPositionsANOptionaldirectly on the message body
RequestForPositionsAckAOOptionaldirectly on the message body
SecurityDefinitiondOptionalOptionaldirectly on the message body
SecurityDefinitionRequestcOptionalOptionaldirectly on the message body
SecurityListyOptionalinside the SecListGrp component
SecurityListRequestxOptionaldirectly on the message body
SecurityStatusfOptionalOptionaldirectly on the message body
SecurityStatusRequesteOptionalOptionaldirectly on the message body
TradeCaptureReportAEOptionalinside the TrdCapRptSideGrp component

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 15 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[15];field?.name;   // "Currency"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-fix44