Digital Twin · Real-time ledger
D
Real-time transaction ledger

A multi-balance ledger your channels and processors integrate with.

Digital Twin sits beside the Core, authorizing transactions and adjusting balances in real time — 24×7, whether the Core is up or down. This site documents how digital channels, card & payment processors, and blockchain custody integrate with it, over REST and over Kafka.

◈

Built for stablecoins: 24×7 by nature and carrying 6 or more decimal places — two requirements that generally disqualify traditional DDA systems. Digital Twin handles crypto and fiat side by side.

Overview

Digital Twin in the integration landscape

Digital Twin is not a customer-facing product. It exposes its capabilities to digital channels, card processors, payment processors and other systems — never to the end user directly. Those systems send transactions; Digital Twin adjusts one or more balances across one or more accounts and returns an authoritative, real-time result.

12k+
TPS across 145M accounts
3k+
TPS in a single account
24×7
Available even when the Core is down
Why Digital Twin

Two value propositions — that combine

Digital Twin delivers two things to the bank. It can do either one alone, or both together — and that's why it's worth reading on.

Proposition 1
Batch DDA → real-time for the user
Shadows the mainframe DDA and makes it available 24×7 from the user's point of view — even when the mainframe's batch processing is down.
Proposition 2
Stablecoins & crypto side-by-side with fiat
Adds stablecoins and other cryptos as new 24×7 assets, with the same banking experience — without needing to shadow the mainframe.
Combined: USD and USDC sit 24×7 side by side, shadowing USD into Digital Twin. Or the bank starts with crypto-only 24×7 — great for POCs — and adds fiat later.
Explore the docs
Architecture & cloud →
How Digital Twin is deployed and who talks to it.
Ledger model →
Multi-balance accounts and transaction codes.
REST APIs →
Synchronous endpoints for posts and reads.
AVRO / Kafka messages →
Asynchronous topic-based integrations.
Matera · Digital Twin — integration documentation