PartyID (FIX tag 448)

StringFIX 4.4FIX 5.0 SP2

PartyID (tag 448) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 44 message types, always optionally.

At a glance

Tag
448
Name
PartyID
Datatype
String
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
44

What the specification says

FIX 4.4

Party identifier/code. See PartyIDSource (447) and PartyRole (452). See "Appendix 6-G – Use of <Parties> Component Block"

FIX 5.0 SP2

Party identifier/code. See PartyIDSource (447) and PartyRole (452).

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

A real message using tag 448

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength141
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
453NoPartyIDs2 entries2repeating group
448PartyIDEXAMPLE
448PartyIDEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum211
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 448 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 5.0 SP2Where in the message
AdjustedPositionReportBLOptionalinside the Parties component
AllocationInstructionJConditionalOptionalinside the Parties component
AllocationInstructionAckPConditionalOptionalinside the Parties component
AllocationInstructionAlertBMOptionalinside the Parties component
AllocationReportASConditionalOptionalinside the Parties component
AllocationReportAckATConditionalOptionalinside the Parties component
ApplicationMessageRequestBWOptionalinside the Parties component
ApplicationMessageRequestAckBXOptionalinside the Parties component
AssignmentReportAWConditionalOptionalinside the Parties component
CollateralAssignmentAYConditionalOptionalinside the Parties component
CollateralInquiryBBConditionalOptionalinside the Parties component
CollateralInquiryAckBGConditionalOptionalinside the Parties component
CollateralReportBAConditionalOptionalinside the Parties component
CollateralRequestAXConditionalOptionalinside the Parties component
CollateralResponseAZConditionalOptionalinside the Parties component
ConfirmationAKConditionalOptionalinside the Parties component
ContraryIntentionReportBOOptionalinside the Parties component
CrossOrderCancelReplaceRequesttConditionalOptionalinside SideCrossOrdModGrp › Parties
CrossOrderCancelRequestuConditionalOptionalinside SideCrossOrdCxlGrp › Parties
ExecutionReport8ConditionalOptionalinside the Parties component
IOI6Optionalinside the Parties component
ListCancelRequestKOptionalinside the Parties component
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › Parties
MarketDataRequestVOptionalinside the Parties component
MarketDataRequestRejectYOptionalinside the Parties component
MarketDataSnapshotFullRefreshWOptionalinside MDFullGrp › Parties
MassQuoteiConditionalOptionalinside the Parties component
MassQuoteAcknowledgementbConditionalOptionalinside the Parties component
MultilegOrderCancelReplaceACConditionalOptionalinside the Parties component
NewOrderCrosssConditionalOptionalinside SideCrossOrdModGrp › Parties
NewOrderListEConditionalOptionalinside ListOrdGrp › Parties
NewOrderMultilegABConditionalOptionalinside the Parties component
NewOrderSingleDConditionalOptionalinside the Parties component
OrderCancelReplaceRequestGConditionalOptionalinside the Parties component
OrderCancelRequestFConditionalOptionalinside the Parties component
OrderMassActionReportBZOptionalinside the Parties component
OrderMassActionRequestCAOptionalinside the Parties component
OrderMassCancelReportrOptionalinside the Parties component
OrderMassCancelRequestqOptionalinside the Parties component
OrderMassStatusRequestAFConditionalOptionalinside the Parties component
OrderStatusRequestHConditionalOptionalinside the Parties component
PositionMaintenanceReportAMConditionalOptionalinside the Parties component
PositionMaintenanceRequestALConditionalOptionalinside the Parties component
PositionReportAPConditionalOptionalinside the Parties component
QuoteSConditionalOptionalinside the Parties component
QuoteCancelZConditionalOptionalinside the Parties component
QuoteRequestRConditionalOptionalinside QuotReqGrp › Parties
QuoteRequestRejectAGConditionalOptionalinside QuotReqRjctGrp › Parties
QuoteResponseAJConditionalOptionalinside the Parties component
QuoteStatusReportAIConditionalOptionalinside the Parties component
QuoteStatusRequestaConditionalOptionalinside the Parties component
RFQRequestAHOptionalinside the Parties component
RegistrationInstructionsoConditionalOptionalinside the Parties component
RegistrationInstructionsResponsepConditionalOptionalinside the Parties component
RequestForPositionsANConditionalOptionalinside the Parties component
RequestForPositionsAckAOConditionalOptionalinside the Parties component
SettlementInstructionRequestAVConditionalOptionalinside the Parties component
SettlementInstructionsTConditionalOptionalinside SettlInstGrp › Parties
SettlementObligationReportBQOptionalinside SettlObligationInstructions › Parties
StreamAssignmentReportCDOptionalinside StrmAsgnRptGrp › Parties
StreamAssignmentRequestCCOptionalinside StrmAsgnReqGrp › Parties
TradeCaptureReportAEConditionalOptionalinside TrdCapRptSideGrp › Parties
TradeCaptureReportAckAROptionalinside TrdCapRptAckSideGrp › Parties
TradeCaptureReportRequestADConditionalOptionalinside the Parties component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

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

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