Skip to main content
The first step with Corridor moves no money. A payment company shares the addresses of the wallets it already uses with its current providers, plus an export of its payout records. Corridor watches those wallets, matches every stablecoin movement against the records, and produces the morning exceptions queue.
1

Share addresses

Tempo, Solana and Base addresses, in a short config file. No keys, no API access to the company’s systems.
2

Share payout records

A CSV from the company’s core system: id, chain, stablecoin, amount, direction, counterparty, reference (if any), time.
3

Get matched payouts and exceptions

Every record is matched, short, over, pending or missing; every movement with no record is flagged. A CSV comes back for the finance team.

​
What gets observed

​
How matching works

  1. By Corridor Reference. A movement that carries a reference (Tempo memo, Solana memo) matches the record with the same reference on the same chain, exactly.
  2. By amount and counterparty. Otherwise: same chain, same stablecoin, same direction, same counterparty when the record names one, nearest in time within six hours, exact amounts first.
Amounts stay in integer minor units throughout, so nothing is rounded.

​
Run it

The example watches the demo’s real testnet wallets (Tempo Moderato treasury, Solana devnet vault, Base Sepolia relay) against eight sample records. A run on 3 October 2026 observed 22 stablecoin movements and returned: The unexpected movements are faucet mints and internal saga legs that the sample records do not cover, which is the point: a real pilot surfaces exactly these.

​
From pilot to moving money

The same observers, references and matching run unchanged when Corridor starts moving money. The difference is who signs: the company connects its own signer (Keys and signers), and Corridor’s sagas move payouts over Tempo with the reference in every memo, so matching becomes exact instead of heuristic.