Product
The TwoWay Platform
Structured fixed-income data from broker chat. Ingestion, parsing, ISIN enrichment, and feed delivery in one pipeline.
How It Works at the Data Layer
From Chat to Structured Feed
Every broker quote passes through four stages: ingestion from messaging platforms, NLP-based parsing, instrument normalisation, and structured feed delivery to your OMS or export pipeline.
Ingestion Layer
Connects to Bloomberg Messenger, ICE Chat, Symphony and Refinitiv Eikon Messenger. Broker messages are pulled in real time and queued for parsing. Integration depth varies by platform; contact us for current availability.
NLP Parse Engine
Natural-language parsing extracts instrument identifiers, directional intent (bid or offer), notional size, and price or spread from free-form broker text without requiring structured input from counterparties.
Output Feed Delivery
Normalised records delivered via JSON API, CSV file, or direct OMS-compatible format. Each record carries a full audit trail including source platform, timestamp, and parsing confidence indicators.
Messenger Coverage
Where Your Brokers Already Are
TwoWay connects to the messaging platforms your broker relationships run on today. No new tooling required from counterparties.
Integration depth varies by platform. Contact us for current technical availability and onboarding timeline.
Structured Output Schema
What a Parsed Record Contains
Each structured record from TwoWay includes the fields your OMS or portfolio system needs, normalised from raw broker language.
| Field | Type | Example | Source |
|---|---|---|---|
| ISIN | String | FR0013451670 | Parsed + resolved via reference data |
| Direction | Enum | BID | NLP directional intent |
| Notional | Decimal | 5,000,000 | Extracted from quantity token |
| Price Type | Enum | SPREAD | Pricing convention detection |
| Price Value | Decimal | +42 | Numeric extraction |
| Settlement Date | ISO 8601 | 2026-10-17 | T+2 convention or explicit |
| Source Platform | String | ICE Chat | Ingestion metadata |
| Counterparty Label | String | Broker desk identifier | Message metadata |
| Parse Confidence | Score 0-1 | 0.94 | Model confidence indicator |
| Audit Timestamp | ISO 8601 | 2026-10-06T09:14:22Z | Ingestion time |
Reference Data Enrichment
From Raw Token to Clean Identifier
Raw broker messages rarely contain a clean ISIN. TwoWay resolves partial identifiers, ticker aliases, and currency-tenor shorthand against reference data providers to produce a normalised, exchange-ready instrument identifier.
- ISIN and CUSIP resolution from partial ticker or bond alias
- Currency normalisation across EUR, USD, GBP and multi-currency deals
- Pricing convention detection: yield, spread-to-benchmark, or discount margin
- Settlement date normalisation to ISO 8601 with T+N convention support
GDPR and Data Lineage
Your Data, Your Audit Trail
TwoWay processes trading communication data under EU GDPR. Every record carries a verifiable lineage from source message to structured output.
EU-Hosted Infrastructure
All data processing and storage occurs within EU data centres. No data leaves EU jurisdiction. Fully compatible with GDPR cross-border transfer restrictions.
Data Processing Agreement
A GDPR-compliant DPA is included with Floor and Enterprise tiers. It covers lawful processing basis, data subject rights, and sub-processor controls required under Article 28.
MiFID II Audit Compatibility
Structured records support MiFID II Article 16 communication surveillance requirements. Source message metadata retained for the regulatory review period. No client data used for model training.
Encryption End-to-End
Data encrypted in transit with TLS 1.3 and at rest with AES-256. Encryption keys managed per-tenant. No shared key material between client environments.
Ready to see the platform in action?
We run structured pilots with fixed-income desks. Contact us to discuss your data environment.