> ## 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. # What Corridor is > The product, who it serves, what it replaces, and an exact account of what runs live today versus what is simulated. ## The product in one paragraph Corridor is the payment ledger and router a licensed payment company **runs itself, with its own keys**. A single EUR → NGN payout today crosses a bank collection, one or more stablecoin providers, several chains, a bridge, a local payout partner and the beneficiary's bank, each with its own ids and dashboard. Corridor follows each payout through all of it with a 32-byte **Corridor Reference** carried in every chain's native memo, matches it from funding to bank credit, and puts everything that did not match in an exceptions queue. When Corridor moves the money, it settles on **Tempo** and pays out through the partner that serves the destination: a Nigerian bank account, a Hong Kong supplier account, Pix in Brazil, or a shielded Zcash address. Customers start **read-only**: Corridor watches the wallets they already run and matches their own payout records, with no keys and nothing moving. ## Who it serves Cross-border payouts without a pre-funded nostro account in each country, starting with Europe → Africa (EUR, GBP, USD → NGN, KES, GHS). Businesses paying suppliers across borders, starting with African importers paying China, Hong Kong, India, the UAE and the Americas, with the option to keep supplier prices off public chains. Local liquidity providers become a spoke: one integration reaches every customer and every other region on the network. Every payout matched end to end across providers and chains, an exceptions queue, a CSV for the books, and auditor disclosures from a single console. ## What it replaces | Today | With Corridor | | - | - | | Fiat pre-funded in a bank account in every country | One pathUSD balance on Tempo, topped up when the forecast says so | | T+1 to T+3 through correspondent banks | 0.6 s finality on the hub; minutes end to end through partners | | A new banking setup per corridor (N×N) | One partner per region; every spoke reaches every spoke (N) | | Spreadsheets and statement matching across providers | Every payout matched from funding to bank credit, with an exceptions queue | | Stuck or short-paid payouts found when a customer complains | `missing` and `short` flagged the same day | | Locked into one provider's dashboard | Providers become interchangeable venues; the ledger and history stay | | Supplier prices visible on public chains | Shielded batches on Zcash, with a viewing key scoped to one customer and period | ## What Corridor is not * **Not a custodian or a money transmitter.** Corridor runs in the customer's environment and signs with the customer's own KMS or MPC keys; it never holds customer funds. The licensed customer holds the FX permissions, the KYC and the end-customer relationship. For outbound flows from regulated markets (for example Form M for Nigerian imports), Corridor carries the compliance references in the saga data and produces the reconciliation trail as audit evidence. * **Not a wallet or an exchange.** Customers do not trade on Corridor; it settles and reconciles their payments. * **Not a new chain or a new rail.** Corridor composes existing chains and providers, each for the job it does best: Tempo for settlement, Solana and Base for partner liquidity, Zcash for privacy, and payout and liquidity providers (Paj, Yellow Card, Conduit, Mansa and others) as venues. * **Not tied to one stablecoin.** USDC, USDT, PYUSD and EURC are first-class alongside pathUSD ([ADR 0010](/decisions/0010-issuer-neutral-stablecoins)). ## Live, simulated, and next This is an honest account of the build on 3 October 2026. Reviewers can verify every "live" row on-chain from [Evidence](/status/evidence). | Capability | State | Detail | | - | - | - | | Tempo settlement with memo references | **Live (testnet)** | `transferWithMemo` on Moderato, found by indexed memo topic, booked exactly once | | Settlement saga with on-chain compensation | **Live (testnet)** | Forced partner failures refunded on Tempo in reverse order | | Hub-and-spoke routing to 32 currencies | **Live** | Planner enforces the hub; tested | | Solana partner funding with SPL memo | **Live (devnet)** | Real USDC transfer with `corridor:` memo | | Paj partner adapter (API v2) and signed webhooks | **Built** | Exercised against a Paj-shaped mock with the same HMAC scheme | | Shielded batches on Zcash Ironwood | **Live (testnet)** | One transaction, three recipients, encrypted invoice memos | | FROST 2-of-3 vault control | **Live (testnet)** | Signer 2 alone refused; signers 1 + 3 co-signed | | NEAR Intents pricing for USD → ZEC | **Live quotes** | Mainnet 1Click quotes; testnet delivery is real testnet ZEC | | Across bridge Tempo → Base → Solana | **Built, mainnet pending** | Live quotes verified; testnet has no Tempo deployment, so the testnet route uses a simulated fill with the same interface | | Partner fiat leg | **Simulated** | Mock partner with Paj's lifecycle; the Paj business key is in place and verified read-only against live NGN rates | | Customer-held signing (KMS) | **Built** | One signer interface for Tempo, Base and Solana; AWS KMS adapter tested; the treasury vault signs through it on Moderato | | Read-only pilot | **Live (testnet)** | `pnpm watch:report` watches real Tempo, Solana and Base wallets and matches payout records; exceptions and CSV | | USDT, PYUSD, EURC | **Built** | Solana registry incl. Token-2022; Base registry; watch-only observers read real amounts from balance changes | The demo runs on testnets. Moving to mainnet needs a small funded float (tens of dollars) in wallets the customer controls; the Paj business key is already in place. See [Roadmap](/status/roadmap). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.