Enterprise: Ediphy Managed Gateway

One connection.
Fully managed.

A drop-in on-prem deployment that integrates with your existing trade feed and takes care of every outbound obligation from there. Every tape as it goes live, MiFIR post-trade transparency, transaction reporting to regulators, deferral logic applied automatically, receipt storage and compliance assurance included. One decision, one agreement.

6+
Tapes covered
8
Components
1
Connection

Architecture

How data flows through the gateway

YOUR VENUE Trading Venue Single connection EDIPHY CT Contributor Gateway NORMALISE VALIDATE TRANSMIT CONSOLIDATED TAPES EU Bonds · EU Equities · UK 6+ tapes · multi-region APA / ARM Post-trade publication MiFID transparency · RTS 2 REGULATORS / NCA Transaction reports · RTS 22 ARM submission upstream

Product

Everything a venue needs to report, in one connection.

Nine components covering every live and upcoming obligation for trading venues, APAs, and SIs. One instruction to Ediphy, we integrate, you run the service, and you're auto-connected to each tape as it goes live.

01 / 08

CT Reporting, every tape

Problem

Multiple consolidated tapes are live or in flight across the EU and UK, each requiring you to submit your trade data in its own format, on its own timeline, with its own change cycle. Building separate outbound pipelines is a project; keeping them all current is an ongoing burden.

Solution

You submit once, to one endpoint. We fan your trade data out to every tape, normalised, formatted, and transmitted to each destination. When a spec changes or a new tape launches, the update is ours to make.

02 / 08

Post-Trade Transparency Publication (MiFIR non-equity)

Problem

As an APA or trading venue, you must publish post-trade data publicly within strict timeframes, near real-time for liquid instruments, with automated deferral rules for illiquid or large-in-scale trades. Building and operating the publication infrastructure, managing deferral calculations, and connecting to the consolidated tape is a significant ongoing technical obligation.

Solution

We host and operate the full publication infrastructure on your behalf. You provide the trade data. We apply deferral logic, publish it publicly in the required format, and submit it to the CT. You hold the authorisation; we operate the full publication infrastructure.

03 / 08

Transaction Reporting

Problem

As an ARM, you receive transaction data from investment firms and must submit complete, accurate 65-field MiFIR transaction reports to the regulator. Deriving the full field set from raw trade data, including fields that require lookup, inference, and instrument reference data, is technically demanding and error-prone at scale.

Solution

We receive your trade data, derive the complete transaction report automatically, and submit it to the NCA on your behalf. Full field coverage across all instrument types, with pre-submission validation to catch errors before they reach the regulator.

04 / 08

Deferral Engine (MiFIR transparency)

Problem

LRGS, ILQD, and SIZE deferrals each carry their own thresholds and priority ordering. Thresholds are recalibrated periodically; hand-rolled logic drifts between recalibrations.

Solution

The gateway applies the correct code automatically and tracks every recalibration centrally. Overrides and the full decision log are exposed in the dashboard.

05 / 08

Pre-Live Validation / UAT

Problem

Each tape expects a conformance period before production flow, and every subsequent spec update carries regression risk for what was already working.

Solution

Parallel-run UAT included in every subscription. Every change lands in UAT first, you see it work before it reaches production.

06 / 08

Ongoing Compliance Assurance

Problem

MiFIR transparency rules, TVTIC requirements, and deferral codes evolve continuously, and each tape evolves on its own cycle. Compliance has to track every tape's cycle continuously to stay valid.

Solution

We track each tape's changes and keep the gateway aligned. Every submission carries its receipt ID, retained permanently and exportable on demand.

07 / 08

Integration Service

Problem

Connecting your existing trade systems to six CT targets, a transparency publication path, and a transaction reporting pipeline is a significant integration project, multiple formats, protocols, and field mappings, with ongoing maintenance as specs evolve.

Solution

Ediphy integrates directly with your existing trade API. We build and own the connection; you run the service. No changes to your trading systems required.

08 / 08

Deployment, BYOC by default

Problem

Proving compliance means reconciling your internal trade record against what was actually submitted to each tape, and that reconciliation needs access to both sides within your perimeter.

Solution

BYOC by default. The gateway runs inside your environment, next to your private data, with receipts held locally. Reconciliation is a local query. An Ediphy-hosted option is available if an Ediphy-hosted operating model is preferred.

Obligations already in scope

Two obligations the gateway handles natively.

Not yet front-of-mind across the industry, but already built into every subscription.

01

Receipt State Management

Problem

At least one tape already requires permanent, per-trade receipt storage as the only accepted proof of submission. The pattern may generalise across others. Built DIY, each tape means a durable store, a reconciliation loop, an audit query layer, and a retention policy.

Solution

Receipt storage is built into the gateway for every tape we connect to. Each submission lands with its receipt ID in durable storage; the dashboard reports coverage and the API returns any receipt on demand.

02

Quality Score Management

Problem

Some consolidated tapes publish quality scores publicly, per venue, and those scores evolve through the life of each trade. Low scores are caused by specific, fixable data issues, missing TVTICs, late timestamps, inconsistent venue IDs. Without analytics, they remain visible.

Solution

Per-trade, per-tape score breakdown with remediation guidance. You see what's driving each score and what to change upstream, before it's visible to the market.

What a submission looks like

One inbound trade, every outbound destination.

A trade lands on the gateway through a single inbound API. The gateway derives the MiFIR transaction report, applies deferral logic against current calibration, fans the print out to every tape destination in scope, and persists every receipt to durable storage inside your perimeter.

Every outbound submission carries a receipt ID. The reconciliation question, "what did we actually report, to whom, when, with which deferral code applied?", is answered by a query against your local store.

# inbound trade, single endpoint
POST /v1/trades
{"isin":"XS2345678901","px":98.42,"qty":2500000,"venue":"XOFF","ts":"2026-04-28T09:14:22.117Z"}
# gateway derives + fans out
[ok] TXN RPT derived (65/65 fields) → NCA
[ok] TRANSPARENCY deferral=LRGS → APA publish
[ok] EU CT submitted → 3 regions
[ok] UKCT submitted → 1 region
[ok] TRACE submitted → 1 region
# receipts persisted (BYOC bucket)
receipt_id=eu-ct-7f3a... ack=2026-04-28T09:14:22.341Z
receipt_id=uk-ct-9c12... ack=2026-04-28T09:14:22.402Z
receipt_id=trace-2bd8.. ack=2026-04-28T09:14:22.498Z_

Enforcement context

Reporting failures: the cost of getting it wrong.

Transaction reporting compliance has attracted significant regulatory enforcement activity in recent years. Firms that treated reporting as a back-office checkbox rather than a front-line operational control have found that submission volume and reporting accuracy are materially different obligations. The infrastructure decision matters.

FCA

The transaction reports we receive are crucial to the work we do in combatting financial crime. Sigma's failures were serious, sustained and showed a lack of care. We will take action whenever we identify such failures.

– Steve Smart, FCA Joint Executive Director of Markets and International

Process

Three steps to go live

01

Instruct Ediphy

Tell us your requirements. We scope the integration against your existing trade API, agree terms, and assign a delivery team. Typical scoping: 2 business days.

02

We integrate, you run the service

Ediphy integrates directly with your existing trade API. We build and configure the deployment, validate end-to-end in UAT, and hand it over running in your environment. Typical delivery: 4–6 weeks.

03

Auto-connected as each tape goes live

As each new consolidated tape launches, we connect it. No further integration work on your side. Every tape that goes live, your connection is already in place.

Versus the DIY stack

Six teams, or one partner.

A bank or broker building this in-house ends up with one connection per tape, one ARM, one APA, a hand-rolled deferral engine with no formal maintenance path, and a reconciliation team holding it together.

The real cost is the integration burden, the receipt-store maintenance, and the standing engineering capacity to absorb every spec change. The Ediphy gateway collapses all of it into a single contract.

Ediphy gateway DIY multi-vendor stack
Single inbound endpoint
Bond, equity, derivatives, TRACE tape coverage 3 separate vendors
Deferral logic auto-recalibrated In-house maintenance
Receipt store inside your perimeter Per-vendor
New tape onboarded by vendor
UAT shared across destinations
One commercial relationship

Start the conversation.

Tell us about your venue and we'll walk through what the integration looks like for your setup.