> ## Documentation Index
> Fetch the complete documentation index at: https://corridor.udokaam.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Corridor

> Cross-border stablecoin payouts for licensed payment companies: moved over Tempo, matched from funding to bank credit, on the company's own keys. Starting with Africa's trade corridors.

<Frame caption="The treasury console, recorded from live runs on Tempo Moderato, Solana devnet and Zcash testnet.">
  <img src="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/product/console-overview.jpg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=e83f45a1454070ea9c82d82164f72dfa" alt="Corridor treasury console: hub balances, settlement network and recorded testnet flows" width="2200" height="1161" data-path="images/product/console-overview.jpg" />
</Frame>

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.

<Note>
  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](/architecture/keys-and-signers)). Customers keep their licences, their KYC, their funds and their end-customer relationships. They start [read-only](/flows/read-only-pilot): no keys, nothing moves.
</Note>

## What is built and running

Everything on this site describes code in the [Corridor repository](https://github.com/Udoka-AM/corridor), and every number below is reproducible from the [live console replay](https://corridorapp.udokaam.dev/console/), where each figure links to the transaction behind it.

<CardGroup cols={4}>
  <Card title="0.6 s" icon="timer">
    Settlement finality on the Tempo hub.
  </Card>

  <Card title="45 / 45" icon="check-check">
    Movements reconciled across Tempo, partner webhooks and Zcash.
  </Card>

  <Card title="Δ 0.000000" icon="scale">
    Treasury vault on-chain vs ledger, gas included.
  </Card>

  <Card title="2 of 3" icon="key-round">
    FROST signers required to move a shielded vault.
  </Card>
</CardGroup>

## How the pieces fit

<Frame caption="Fig. 02 · Every flow is a collection into the Tempo hub or a payout out of it.">
  <img className="block dark:hidden" src="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/diagrams/hub-and-spoke-light.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=ac953b5172901b19c2932c79d07215b9" alt="Hub and spoke network with the Tempo hub at the centre" width="1200" height="640" data-path="images/diagrams/hub-and-spoke-light.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/diagrams/hub-and-spoke-dark.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=36715e8f107696f4ed090a38a815aeee" alt="Hub and spoke network with the Tempo hub at the centre" width="1200" height="640" data-path="images/diagrams/hub-and-spoke-dark.svg" />
</Frame>

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

<CardGroup cols={2}>
  <Card title="Read-only pilot" icon="eye" href="/flows/read-only-pilot">
    How a payment company starts: watch the wallets it already runs and match its own payout records.
  </Card>

  <Card title="Keys and signers" icon="key-square" href="/architecture/keys-and-signers">
    One signing interface for Tempo, Base and Solana; AWS KMS today, MPC next.
  </Card>

  <Card title="What Corridor is" icon="info" href="/start/what-corridor-is">
    The product, who it serves, and exactly what is live versus simulated.
  </Card>

  <Card title="Reading paths" icon="map" href="/start/reading-paths">
    Curated routes for investors, CTOs, chain teams and partners.
  </Card>

  <Card title="Architecture" icon="layers" href="/architecture/overview">
    Ledger, route planner, saga engine and reconciliation, one engine for every lane.
  </Card>

  <Card title="Chains & partners" icon="network" href="/integrations/overview">
    Tempo, Across, Base, Solana, Paj, Zcash, FROST and NEAR Intents, each doing the job it is best at.
  </Card>

  <Card title="The opportunity" icon="globe" href="/market/global-opportunity">
    \$31.6T of cross-border B2B payments, under 1% on stablecoins so far, and how Corridor earns on it.
  </Card>

  <Card title="Evidence" icon="file-check" href="/status/evidence">
    Every testnet transaction, linked to its explorer.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.