Price (FIX tag 44)

PriceFIX 4.4FIX 4.2

Price (tag 44) is a Price field defined in FIX 4.4 and FIX 4.2. It appears in 21 message types and is required in 1 of them.

At a glance

Tag
44
Name
Price
Datatype
Price (float)
Dialects
FIX 4.4 and FIX 4.2
Messages
21

What the specification says

FIX 4.4

Price per unit of quantity (e.g. per share)

FIX 4.2

Price per share

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

A real message using tag 44

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength122
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
44Price1.09210
10CheckSum243
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 44 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
BidResponselOptionalOptionalinside the BidCompRspGrp component
CollateralAssignmentAYOptionaldirectly on the message body
CollateralInquiryBBOptionaldirectly on the message body
CollateralReportBAOptionaldirectly on the message body
CollateralRequestAXOptionaldirectly on the message body
CollateralResponseAZOptionaldirectly on the message body
CrossOrderCancelReplaceRequesttConditionaldirectly on the message body
ExecutionReport8ConditionalOptionaldirectly on the message body
IOI6OptionalOptionaldirectly on the message body
ListStrikePricemRequiredRequiredinside the UndInstrmtStrkPxGrp component
MultilegOrderCancelReplaceACConditionaldirectly on the message body
NewOrderCrosssConditionaldirectly on the message body
NewOrderListEConditionalOptionalinside the ListOrdGrp component
NewOrderMultilegABConditionaldirectly on the message body
NewOrderSingleDConditionalOptionaldirectly on the message body
OrderCancelReplaceRequestGConditionalOptionaldirectly on the message body
QuoteRequestROptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptionalinside the QuotReqRjctGrp component
QuoteResponseAJOptionaldirectly on the message body
QuoteStatusReportAIOptionaldirectly on the message body

Wire format

A decimal price. Precision is a venue convention, not a protocol rule, so compare the raw string when exactness matters. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 44 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[44];field?.name;   // "Price"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other Price 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