Connected systems
- Your institution’s systems send and read TEDs over HTTPS and receive the events.
- Operators and administrators run the queue, the deadlines and the policies through the API.
- Access Manager validates the token and the permission of each call.
- Midaz holds, settles and releases the amounts, calculates fees and answers account and holder lookups.
- Lerian SPB carries the messages to and from the STR over the RSFN.
- Streaming Hub delivers the events to your institution’s subscription.
Service and data
What runs inside TED Lerian and where each piece of data lives. The API and the background workers are one service.
- TED service. Answers the
/v1API and runs the background workers: reconciliation, incoming TEDs, the daily cycle and the event relay. Each institution’s data is isolated. - PostgreSQL keeps transfers, incoming TEDs, returns, policies, the event outbox and the inbox of STR facts.
- MongoDB keeps the audit trail.
- Valkey keeps idempotency records, rate-limit counters and usage-limit counters.
- Events. Each status change writes its event in the same database transaction (outbox), and a relay publishes it on the platform event backbone. Streaming Hub delivers it from there.
- STR facts. Lerian SPB publishes what the STR reported (settlement, rejection, incoming TED, schedule changes, closing balance) on the event backbone. The TED service reads them through an inbox that never applies the same fact twice.
Components of the TED service
The service has four domains, each with its own rules, data and endpoints.