Currency (FIX tag 15)

CurrencyFIX 4.4FIX 4.2FIX 5.0 SP2

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

At a glance

Tag: 15
Name: Currency
Datatype: Currency (String)
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
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.

FIX 5.0 SP2

Identifies currency used for price or quantity fields, depending on the asset class being traded. CurrencyCodeSource(2897) may be used to disambiguate the code source scheme used, and ISO 4217 is the default scheme if absent.

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

A real message using tag 15

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	118
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
15	Currency	EUR
10	CheckSum	135

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.

Message	MsgType	FIX 4.4	FIX 4.2	FIX 5.0 SP2	Where in the message
Advertisement	7	Optional	Optional	Optional	directly on the message body
AllocationInstruction	J	Optional	Optional	Optional	directly on the message body
AllocationInstructionAlert	BM	—	—	Optional	directly on the message body
AllocationReport	AS	Optional	—	Optional	directly on the message body
AssignmentReport	AW	Optional	—	Optional	directly on the message body
BidRequest	k	Optional	Optional	Optional	directly on the message body
CollateralAssignment	AY	Optional	—	Optional	directly on the message body
CollateralInquiry	BB	Optional	—	Optional	directly on the message body
CollateralInquiryAck	BG	Optional	—	Optional	directly on the message body
CollateralReport	BA	Optional	—	Optional	directly on the message body
CollateralRequest	AX	Optional	—	Optional	directly on the message body
CollateralResponse	AZ	Optional	—	Optional	directly on the message body
Confirmation	AK	Optional	—	Optional	directly on the message body
CrossOrderCancelReplaceRequest	t	Optional	—	Optional	directly on the message body
DerivativeSecurityList	AA	Optional	—	Optional	inside the RelSymDerivSecGrp component
DerivativeSecurityListRequest	z	Optional	—	Optional	directly on the message body
DerivativeSecurityListUpdateReport	BR	—	—	Optional	inside the RelSymDerivSecUpdGrp component
ExecutionReport	8	Optional	Optional	Optional	directly on the message body
IOI	6	Optional	Optional	Optional	directly on the message body
ListStrikePrice	m	Optional	Optional	Optional	inside the UndInstrmtStrkPxGrp component
MarketDataIncrementalRefresh	X	Optional	Optional	Optional	inside the MDIncGrp component
MarketDataRequest	V	—	—	Optional	inside the InstrmtMDReqGrp component
MarketDataSnapshotFullRefresh	W	Optional	Optional	Optional	inside the MDFullGrp component
MarketDefinition	BU	—	—	Optional	directly on the message body
MarketDefinitionUpdateReport	BV	—	—	Optional	directly on the message body
MassQuote	i	Optional	Optional	Optional	inside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgement	b	Optional	—	Optional	inside QuotSetAckGrp › QuotEntryAckGrp
MultilegOrderCancelReplace	AC	Optional	—	Optional	directly on the message body
NewOrderCross	s	Optional	—	Optional	directly on the message body
NewOrderList	E	Optional	Optional	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	—	Optional	directly on the message body
NewOrderSingle	D	Optional	Optional	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	Optional	Optional	directly on the message body
PositionMaintenanceReport	AM	Optional	—	Optional	directly on the message body
PositionMaintenanceRequest	AL	Optional	—	Optional	directly on the message body
PositionReport	AP	Optional	—	Optional	directly on the message body
Quote	S	Optional	Optional	Optional	directly on the message body
QuoteRequest	R	Optional	Optional	Optional	inside the QuotReqGrp component
QuoteRequestReject	AG	Optional	—	Optional	inside the QuotReqRjctGrp component
QuoteResponse	AJ	Optional	—	Optional	directly on the message body
QuoteStatusReport	AI	Optional	—	Optional	directly on the message body
RequestForPositions	AN	Optional	—	Optional	directly on the message body
RequestForPositionsAck	AO	Optional	—	Optional	directly on the message body
SecurityDefinition	d	Optional	Optional	Optional	directly on the message body
SecurityDefinitionRequest	c	Optional	Optional	Optional	directly on the message body
SecurityDefinitionUpdateReport	BP	—	—	Optional	directly on the message body
SecurityList	y	Optional	—	Optional	inside the SecListGrp component
SecurityListRequest	x	Optional	—	Optional	directly on the message body
SecurityListUpdateReport	BK	—	—	Optional	inside the SecLstUpdRelSymGrp component
SecurityStatus	f	Optional	Optional	Optional	directly on the message body
SecurityStatusRequest	e	Optional	Optional	Optional	directly on the message body
SettlementObligationReport	BQ	—	—	Optional	inside the SettlObligationInstructions component
TradeCaptureReport	AE	Optional	—	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	—	—	Optional	directly on the message body

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

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

Try the decoder Source on GitHub