HostCrossID (FIX tag 961)

StringFIX 5.0 SP2

HostCrossID (tag 961) is a String field defined in FIX 5.0 SP2. It appears in 3 message types, always optionally.

At a glance

Tag: 961
Name: HostCrossID
Datatype: String
Dialects: FIX 5.0 SP2
Messages: 3

What the specification says

Host assigned entity ID that can be used to reference all components of a cross; sides + strategy + legs. Used as the primary key with which to refer to the Cross Order for cancellation and replace. The HostCrossID will also be used to link together components of the Cross Order. For example, each individual Execution Report associated with the order will carry HostCrossID in order to tie back to the original cross order.

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

A real message using tag 961

ExecutionReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	135
35	MsgType	8	ExecutionReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
961	HostCrossID	EXAMPLE
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
10	CheckSum	127

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 961 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	Requiredness	Where in the message
CrossOrderCancelReplaceRequest	t	Optional	directly on the message body
CrossOrderCancelRequest	u	Optional	directly on the message body
ExecutionReport	8	Optional	directly on the message body

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 961 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[961];field?.name;   // "HostCrossID"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-fix50sp2

Try the decoder Source on GitHub