Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.2Field

RefSeqNum <45>

Tag
45
Type
int
Pedigree
Added FIX 2.7
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows RefSeqNum <45> as defined in FIX 4.2. For the current standard, see tag 45 RefSeqNum in FIX Latest.

RefSeqNum <45> in plain English

Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).

RefSeqNum gives the sequence number of the message being referred to, on a session-level Reject or a BusinessMessageReject.

Where it is used

Reject (35=3), BusinessMessageReject (35=j) . In all, 2 messages in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=101|35=3|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|45=7|371=44|372=D|373=5|58=Invalid price|10=176

Illustrative example, not real orders or market data. A Reject (35=3) in FIX 4.2, shown with BeginString FIX.4.2. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.2 dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

Reference message sequence number

Used in

Messages (2)

MessageMsgTypePresence
Reject3Required
BusinessMessageRejectjOptional