RTX5FIX Connectivity
Review the proposed FIX 4.4/5.0 adapter scope, session agreement and certification requirements. A certified version, dictionary and tested message matrix are not yet published.
FIX connectivity does not imply every counterparty automatically supports FIX sessions.
Protocol Scope to Confirm
FIX 4.4
Agree FIX 4.4 session, order and market-data scope with the counterparty. The adapter version and certified support matrix remain unpublished; plan fees do not establish availability.
FIX 5.0
Agree the exact FIX 5.0 application/service-pack version and FIXT transport, dictionary and party fields. No universal FIX 5.0 dialect or tested adapter is established here.
Session Scope
Each FIX session has defined scope: which instruments, order types and message types are supported. Session count and scope must be agreed per adapter/order.
Adapter Certification
Each counterparty adapter must be certified for the specific FIX version, message set and order types. A generic FIX connection does not guarantee compatibility with every venue.
Recovery & Sequencing
Specify and test heartbeat, sequence reset, resend and gap-fill behavior for the agreed session. Recovery support requires an adapter-specific test record.
Messages to Certify
Candidate message families include orders, cancel/replace, execution reports and market-data requests/updates. Exact fields, rejects and message coverage must be certified per adapter; these are not a supported-message claim.
Agree the Adapter, Dialect and Recovery Rules
A FIX version identifies a protocol family. The bilateral session agreement establishes the messages, fields, instruments and recovery behavior available for a particular route.
Swipe horizontally to view all columns.
| Contract field | Developer requirement |
|---|---|
| Connection purpose | Market data, order entry, drop copy and account administration are separately scoped. Quote access alone cannot fund or administer an account. |
| Protocol | Application version, service/extension pack, session transport, TLS, dictionary extensions and required identifiers. |
| Lifecycle | Logon/logout, heartbeats, sequence reset, resend, duplicate detection, recovery and session calendar. |
| Execution semantics | Order type, time-in-force, quantity/price precision, partial fills, rejects, corrections and cancel races. |
| Commercial boundary | Included RTX5 charge, provider quote, market-data rights, network costs, environments and certification ownership. |
Swipe horizontally to view all columns.
| Agreement field | What the route must specify | Public evidence |
|---|---|---|
| Application and session | FIX 4.4, or the agreed FIX 5.0 application version and FIXT transport; service-pack details where applicable. | Adapter-specific version and tested build: not yet published. |
| Dialect and identity | Counterparty dictionary, required/custom fields, party identifiers and sender/target identities. | Sanitized dictionary and counterparty scope: not yet published. |
| Quotes and orders | Subscription types, eligible instruments, order types, time-in-force values, cancel/replace and report coverage. | Certified per-message support matrix: not yet published. |
| Session operations | Schedule, heartbeat, logon permissions, sequence resets, resend/gap-fill behavior and disconnect recovery. | Tested session configuration and recovery report: not yet published. |
Swipe horizontally to view all columns.
| Task | Message sequence to agree | Validation question |
|---|---|---|
| Market data | MarketDataRequest → agreed snapshot and/or incremental updates. | Which depth and update types are supported, and what happens when a subscription is rejected? |
| New order | NewOrderSingle → ExecutionReport acknowledgment and subsequent reports. | How are acceptance, partial fills, full fills and rejection identified for this dialect? |
| Cancel or replace | OrderCancelRequest / OrderCancelReplaceRequest → execution or rejection response. | How are request IDs linked, and how are fills received during a pending change reconciled? |
| Recover a gap | Detect sequence gap → agreed resend/gap-fill procedure → reconcile order state. | Which messages can be replayed, and when is a fresh account/order snapshot required? |
- 01
Agree commercial and technical access
Confirm the counterparty, instrument entitlement, network/security requirements and the exact number and purpose of sessions.
- 02
Validate a named adapter build
Exercise supported order types, rejects, partial fills, cancel/replace races, disconnects and sequence recovery in the agreed test environment.
- 03
Approve production scope
Record the reviewer, certification date, adapter/build version, passed cases, exceptions and production contact path.
- 04
Retest changes
Assess dictionary, session and adapter updates against the agreed cases before expanding the certified scope.
Pricing
| Protocol | Entry | Standard | Enterprise |
|---|---|---|---|
| FIX 4.4 | From US$600/month | Included | Included |
| FIX 5.0 | US$2,000/month | Included | Included |
Define the Included Connection Scope
Use the pricing matrix above alongside a route-specific order form. Plan inclusion covers the agreed connection scope.
Swipe horizontally to view all columns.
| Item | What to confirm |
|---|---|
| Entry | FIX 4.4 From US$600/month and FIX 5.0 US$2,000/month apply when separately chargeable under the route contract. Specify session count and message scope. |
| Standard and Enterprise | Bridge/FIX connection fees are included for the agreed scope. Define included adapters, sessions and environments so the same included connection is not charged again. |
| Counterparty and data access | Confirm the broker's eligibility, counterparty agreement and any separate market-data, venue or third-party charges. |
| Changes and support | Document additional-session pricing, certification work, support responsibility and change-management arrangements in the quote. |