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

CheckSum <10>

Tag
10
Type
String
Pedigree
Added FIX 2.7
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

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

CheckSum <10> in plain English

Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.2 description is quoted in full below and may differ.

CheckSum is a three-character checksum and is always the last field. With its trailing delimiter it marks the end of the message, and it is never encrypted.

Where it is used

StandardTrailer (component) . In all, 46 messages in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=60|35=0|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|10=143

Illustrative example, not real orders or market data. A Heartbeat (35=0) 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)

Three byte, simple checksum (see Appendix B: CheckSum Calculation for description). ALWAYS LAST FIELD IN MESSAGE; i.e. serves, with the trailing <SOH>, as the end-of-message delimiter. Always defined as three characters. (Always unencrypted)

Used in

Components and repeating groups (1)

NameKindPresence
StandardTrailerComponentRequired
All 46 messages that can carry CheckSum, including through components and groups