RefCompID (FIX tag 930)

StringFIX 4.4

RefCompID (tag 930) is a String field defined in FIX 4.4. It appears in 2 message types, always optionally.

At a glance

Tag: 930
Name: RefCompID
Datatype: String
Dialects: FIX 4.4
Messages: 2

What the specification says

Assigned value used to identify a firm.

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

A real message using tag 930

NetworkCounterpartySystemStatusRequest · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	112
35	MsgType	BC	Network (Counterparty System) Status Request
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
935	NetworkRequestType	1	Snapshot
933	NetworkRequestID	EXAMPLE
936	NoCompIDs2 entries	2	repeating group
930	RefCompID	EXAMPLE
930	RefCompID	EXAMPLE
10	CheckSum	005

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 930 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
NetworkCounterpartySystemStatusRequest	BC	Conditional	inside the CompIDReqGrp component
NetworkCounterpartySystemStatusResponse	BD	Conditional	inside the CompIDStatGrp 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 930 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[930];field?.name;   // "RefCompID"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