The mirror ledger is the mechanism that lets ClearBox approve a payment at a Web3-blind terminal before the underlying blockchain has confirmed anything. It’s why a customer can tap and walk away with their coffee while settlement completes asynchronously.Documentation Index
Fetch the complete documentation index at: https://docs.clear-box.io/llms.txt
Use this file to discover all available pages before exploring further.
The problem it solves
On-chain confirmation is slow relative to a checkout counter. Waiting for a block to finalize can take minutes, which is unworkable when a guest is standing at a register. Legacy point-of-sale terminals also expect a fiat-style authorization response in well under a second — they have no concept of a pending transaction hash.How it works
The mirror ledger maintains a real-time internal balance for each wallet that mirrors the on-chain state. When an authorization request arrives, ClearBox decides against the mirror, not the chain.Authorization request
The card network routes an authorization request for a given amount to ClearBox.
Validate against the mirror
ClearBox checks the wallet’s mirrored available balance — for example, “is 100.00 balance?” — and places a hold.
Approve in real time
If funds are available, ClearBox returns an approval (typically in roughly 0.2 seconds) and the terminal completes the sale.
Why it’s safe
The hold placed at authorization prevents double-spending the same balance across concurrent transactions. The mirror is continuously reconciled against the chain, so any divergence is detected and resolved. Because the wallet is non-custodial, the on-chain settlement is the authoritative record — the mirror is an accelerated view of it, not a replacement for it.The mirror ledger is a ClearBox-internal system. Its internal reconciliation endpoints are not part of the public API; integrators interact with it only indirectly, through the authorization and settlement flow and webhooks.