Skip to main content
Corridor treasury console: hub balances, settlement network and recorded testnet flows

The treasury console, recorded from live runs on Tempo Moderato, Solana devnet and Zcash testnet.

Corridor is the payment ledger and router that licensed payment companies (PSPs, remittance operators, payout companies and the banks behind importers) run themselves for cross-border payments, starting with the trade corridors into and out of Africa. It moves stablecoin payouts over Tempo and the partners that pay out locally, and matches every payout from customer funding to beneficiary bank credit, whichever provider and chain carried it. Suppliers can be paid privately on Zcash, with a viewing key for the auditor.
Corridor is software, not a custodian or a money transmitter. It runs in the customer’s environment and signs with the customer’s own keys (Keys and signers). Customers keep their licences, their KYC, their funds and their end-customer relationships. They start read-only: no keys, nothing moves.

​
What is built and running

Everything on this site describes code in the Corridor repository, and every number below is reproducible from the live console replay, where each figure links to the transaction behind it.

0.6 s

Settlement finality on the Tempo hub.

45 / 45

Movements reconciled across Tempo, partner webhooks and Zcash.

Δ 0.000000

Treasury vault on-chain vs ledger, gas included.

2 of 3

FROST signers required to move a shielded vault.

​
How the pieces fit

Hub and spoke network with the Tempo hub at the centreHub and spoke network with the Tempo hub at the centre

Fig. 02 · Every flow is a collection into the Tempo hub or a payout out of it.

Every flow is either a collection into the Tempo hub or a payout out of it. A Nigerian importer paying a supplier in Shenzhen is a naira collection followed by a yuan payout; a diaspora transfer into Lagos is a euro collection followed by a naira payout. Adding a region means adding one partner, and it can immediately reach every other region: N integrations instead of N×N corridors.

​
Where to go next

Read-only pilot

How a payment company starts: watch the wallets it already runs and match its own payout records.

Keys and signers

One signing interface for Tempo, Base and Solana; AWS KMS today, MPC next.

What Corridor is

The product, who it serves, and exactly what is live versus simulated.

Reading paths

Curated routes for investors, CTOs, chain teams and partners.

Architecture

Ledger, route planner, saga engine and reconciliation, one engine for every lane.

Chains & partners

Tempo, Across, Base, Solana, Paj, Zcash, FROST and NEAR Intents, each doing the job it is best at.

The opportunity

$31.6T of cross-border B2B payments, under 1% on stablecoins so far, and how Corridor earns on it.

Evidence

Every testnet transaction, linked to its explorer.