Blockchain infrastructure is built. The coordination layer for secure, compliant transactions isn't. Until now, every institution has built it alone.
Every institution builds its own coordination layer. Each new counterparty type, jurisdiction, use case requires a bilateral integration or a different vendor. The result is parallel systems for transaction rails, PII exchange, and reconciliation — across chains and wallet types. Engineering and operational costs compound.
Yet coverage gaps persist. Networks don't interoperate: travel rule completion remains low, transfers still go to unknown addresses. Institutions can only reach the counterparties they integrated; non-custodial wallets and agents are in a compliance deadlock. Manual input and inconsistent wallet experience push conversion down. And transfers carry residual risk: no integrity guarantee means tampering can go undetected.
OTL builds shared standards to close these gaps — so every participant can operate on one interoperable foundation, instead of rebuilding the same layer independently.
The four base layers — identity, messaging, transport, session — are modular and interoperable. They combine into end-to-end applications (the fifth layer): merchant checkout, B2B settlement, agentic payments — with pre-transaction coordination, compliance and security built in. Each layer is independently adoptable, so existing integrations keep operating.
Open Transaction Layer is a technical initiative, operating as an industry alliance. Collaboration starts from the problems we want to solve, not theoretical frameworks. Founding members gain a shared voice to engage regulators and advocate for concrete technical implementations.
The core deliverable is protocol libraries: open-source, interoperable, and designed to be agent-friendly. Work is organized in tracks, spanning multiple layers of the stack. Each track produces reference specifications and defines how existing standards interoperate.
Shape specifications before they exist. Protocols will reflect your constraints and implementation preferences.
Actively contribute to select tracks, driving the reference implementation conversation and code for that domain.