The FIX protocol, short for Financial Information Exchange, is a non-proprietary electronic messaging standard that financial firms use to send trade-related data to each other in real time. Created in 1992, it replaced phone calls and paper tickets with a shared language for placing orders, confirming executions, and reporting trades across different software systems. A small asset manager and a global investment bank can speak to each other through FIX using the same message formats.
What a FIX Message Looks Like
Every FIX message is built from tag-value pairs: a numbered tag, an equals sign, and the data that goes with it. Tag 35 identifies the message type. Tag 44 carries the price per unit of a security. Each message follows a rigid three-part layout. A standard header identifies who sent the message and who should receive it. The body carries the business content, such as the details of an order or an execution report. The trailer closes the message with a checksum that lets the receiving system confirm nothing was corrupted in transit.
The numbering system is managed by the FIX Trading Community, an independent nonprofit that publishes and updates the protocol specification. Core tags cover the vast majority of trading scenarios, and the protocol reserves separate ranges for custom use when counterparties need proprietary fields.
Application Layer and Session Layer
FIX separates its work into two layers that handle very different jobs. The application layer deals with business content: what security is being traded, at what price, in what quantity, and on whose behalf. Think of it as the letter inside the envelope.
The session layer is the envelope and the postal service. It manages the connection between two FIX engines, keeps messages in the right order, tracks sequence numbers, and recovers anything lost during a disconnection. Starting with version 5.0, the FIX Trading Community formally separated the two so that changes to trading messages would not force changes to session plumbing, and vice versa.
Who Uses the FIX Protocol
Three broad groups depend on FIX. The buy-side includes institutional investors, pension funds, and asset managers moving large orders. They send instructions through FIX to the sell-side, which consists of broker-dealers and investment banks that provide execution services. Sell-side firms route those orders to trading venues, including regulated stock exchanges and electronic communication networks, where buy and sell orders are matched.
Because every participant speaks the same protocol, a mid-sized asset manager can route an order to a global bank’s execution desk just as easily as it can reach a regional exchange. A firm builds one FIX interface and connects to any venue or broker that supports the standard, rather than wiring up a separate integration for every counterparty.
Most individual investors never touch FIX directly, but their orders usually pass through it on the way to execution. When you tap “buy” on a brokerage app, the broker’s internal system translates that request into a FIX message and routes it to the appropriate market center. Some brokers offer direct FIX access to active or algorithmic traders, though it typically requires minimum commission thresholds and a formal certification review.
What Information Travels Over FIX
FIX messages map to every stage of a trade’s lifecycle, from first expression of interest through final settlement.
Pre-Trade
Before anyone commits capital, firms exchange Indications of Interest: messages that signal a willingness to buy or sell a particular security without creating a binding obligation. Pre-trade messaging also includes real-time quote data and market depth information that traders use to time their entries.
Execution
A New Order Single message submits an order to a broker or exchange. Execution Reports come back confirming fills, partial fills, or rejections. Status messages let the originating firm track an order’s progress in real time. A “Fill” message, for instance, confirms that a specific quantity was executed at a specific price.
Post-Trade
After execution, FIX carries allocation messages that break a large institutional trade into smaller pieces destined for individual client accounts. It also transmits confirmation and settlement instructions that keep both sides in agreement on what happened and what is owed. Standardized post-trade messaging reduces settlement failures and gives compliance teams a clean audit trail.
How a FIX Session Works
A FIX session follows a predictable lifecycle: logon, active messaging, logout. A misstep at any stage can mean lost orders or broken audit trails.
Logon and Heartbeats
The initiating party sends a Logon message that includes its CompIDs, the next expected sequence number, and a proposed heartbeat interval. If the counterparty accepts, it responds with its own Logon, and the session is live. The Logon must be the first message in any FIX session; nothing else is valid until the handshake completes.
During periods when no business messages are flowing, both sides send Heartbeat messages at the agreed interval to confirm the connection is still alive. The heartbeat timer resets after every message, not just after heartbeats. If a heartbeat fails to arrive within the expected window, the system sends a Test Request to probe whether the counterparty is still responsive. Silence after that probe typically triggers an automatic reconnection attempt.
Sequence Numbers and Gap Recovery
Every message carries a sequence number that increments by one. This running count is the protocol’s primary defense against lost or duplicated data. If the receiving engine detects a gap, it sends a Resend Request asking the sender to retransmit the missing messages. The sender replays business messages and uses a Sequence Reset in Gap Fill mode to skip over administrative messages like heartbeats that do not need resending.
Sequence numbers typically reset to one on a scheduled basis, often weekly or at a custom daily time configured by the counterparties. A firm can force an on-demand reset by sending a Logon with the ResetSeqNumFlag set, though doing so after an unexpected disconnection may trigger the counterparty’s engine to replay any undelivered executions before resuming normal sequencing.
Logout
A clean session termination starts with a Logout message from one side, acknowledged by a Logout from the other. Both engines save their current state so the next session can pick up where it left off. Disconnecting without exchanging Logout messages is treated as an abnormal condition, and the engines will attempt recovery the next time they connect.
Message Rejects
Not every message makes it through cleanly, and FIX has two distinct rejection mechanisms depending on where the problem occurs.
A Session-Level Reject fires when an incoming message violates the basic structural rules of the protocol: an invalid tag number, a required tag that is missing, a tag with no value, or a data format that does not match what the tag expects. The reject includes a reason code in tag 373. Common codes include 0 for an invalid tag number, 1 for a required tag missing, and 5 for a value outside the allowed range. A session-level reject usually signals a bug in the sender’s FIX engine configuration.
A Business Message Reject handles problems that pass the structural checks but fail at the application level. The message is well-formed FIX, but the receiving system cannot process it for business reasons: the message type is not supported, the application is temporarily unavailable, or a conditionally required field is missing. A stop order that arrives without a stop price is a classic example. Business rejects should not be used to enforce proprietary rules stricter than the FIX specification itself.
Security
FIX sessions carry sensitive financial data, and the protocol’s security model has evolved to match modern threats. The primary protection is FIXS, the FIX-over-TLS standard published by the FIX Trading Community. FIXS wraps the entire FIX session in a Transport Layer Security tunnel, encrypting data in transit and preventing eavesdropping or tampering between counterparties. The FIX Trading Community treats it as the baseline requirement for any production connection.
Firms typically layer additional controls on top: IP whitelisting to restrict which network addresses can initiate sessions, CompID validation to confirm identity at the application level, and the sequence number mechanism to detect replayed or injected messages. Some counterparties also negotiate message-level encryption or digital signatures for high-value workflows.
Setting Up and Certifying a FIX Connection
Getting onto the FIX network requires three things: a FIX engine, a secure network link, and a set of identifiers that tell other systems who you are.
The FIX engine is specialized software that translates a firm’s internal data into properly formatted FIX messages, manages sequence numbering, and handles session recovery. Some firms build engines in-house, but most purchase or license one from a vendor. Pricing varies widely. Basic licenses can start in the low thousands of dollars per year, while enterprise-grade engines with dedicated support cost significantly more.
Network connectivity is the second piece. Most production FIX connections run over dedicated leased lines or secure VPN tunnels rather than the open internet, with FIXS layered on top.
Each participant is assigned a pair of identifiers called CompIDs. The SenderCompID (tag 49) tells the receiving system who sent the message, and the TargetCompID (tag 56) tells the sending system where to deliver it. These values are configured in the FIX engine before the first session begins and stay consistent across connections.
No firm goes straight from development to live trading. Every exchange, broker, and trading venue requires a certification process before allowing a new FIX engine onto its production network. The specifics vary, but the general pattern is consistent:
- Connectivity: establish a link to the counterparty’s test environment, usually over an SSL-wrapped TCP connection or VPN tunnel.
- Configuration: set up session parameters including CompIDs, supported message types, and account mappings.
- Development: build the integration against the counterparty’s published FIX specification, which may include custom tags beyond the base standard.
- Certification testing: run through scenarios that simulate production conditions, covering every order type the firm intends to use, handling unsolicited cancellations, processing trade corrections, and recovering from simulated connection failures.
- Review: the counterparty’s integration team reviews the test results and grants or withholds production access.
Simulator tools let firms test engines against a realistic counterparty without a live connection. These platforms can stress-test order management systems with high message volumes, validate session behavior like sequencing and recovery, and automate regression testing so that engine upgrades do not break existing functionality.
Which Version to Use
The FIX Trading Community recommends that firms use FIX Latest, the current and continuously updated version of the specification. Legacy versions 4.2 and 4.4 remain officially supported for firms with established implementations, but all other older versions, including 5.0 and its service packs, have been retired to the archive. A new firm building FIX connectivity for the first time should target FIX Latest unless a specific counterparty requires an older version.
For high-frequency workflows, the community also publishes Simple Binary Encoding, which replaces the text-based tag-value format with native binary data types that can be read directly from memory. SBE encoding speeds exceed text-based alternatives by an order of magnitude for densely populated messages, with the tradeoff that debugging raw binary is far less intuitive than reading tag-value pairs.
Regulatory Touchpoints
Several federal regulations intersect with how FIX messages are generated, stored, and reported. SEC Rule 10b-10 requires broker-dealers to send customers written confirmation of every securities transaction at or before completion of the trade, and the structured data in FIX execution reports maps directly to many of those disclosure requirements.
The Consolidated Audit Trail, established under SEC Rule 613, requires national securities exchanges and associations to report order and trade activity to a central repository so regulators can reconstruct market events across all U.S. equity and options markets. Standardized FIX messaging makes that reporting more straightforward because the data already exists in a machine-readable, timestamped format.
SEC Rule 17a-4 requires broker-dealers to preserve certain trading records for at least six years, with the first two years in an easily accessible location. In 2023, the SEC levied hundreds of millions of dollars in combined fines against firms that failed to maintain proper records. Using a standardized messaging protocol does not guarantee compliance, but it makes the underlying data far easier to archive and retrieve when regulators ask for it.