The seven
Binding mechanisms
How AlgoVoi knows that a specific on-chain transaction satisfies a specific checkout:Memo binding (Algorand, VOI, Hedera)
Transactions carry a note or memo field. AlgoVoi putsalgovoi:{token} in the memo. The verifier matches by memo content.
Short text memo (Stellar)
Same as memo binding, but Stellar capsMEMO_TEXT at 28 bytes. AlgoVoi uses a shortened av:{token[:20]} form.
Reference pubkey (Solana)
Solana doesn’t have arbitrary memos, so AlgoVoi uses Solana Pay’s reference mechanism. A fresh ed25519 pubkey is generated per checkout and included as a non-signer account in the transaction. The verifier looks up the settling tx viagetSignaturesForAddress(reference).
Amount-only (Base, Tempo)
EVM ERC-20 / TIP-20 transfers don’t carry memos. AlgoVoi binds checkouts by amount uniqueness: each checkout’s amount is slightly randomised so two open checkouts for the same target amount can be distinguished.Stablecoin notes
USDC has 6 decimals on every chain except Stellar (7 decimals).
Native asset support
Every chain also supports native-asset payments (ALGO, VOI, HBAR, XLM, ETH, SOL). Native payments are less common because the price is volatile, but they’re useful for chain-only environments where stablecoin issuance hasn’t arrived yet.Picking a chain
If you’re starting from zero:- Cheapest fees: Solana (
$0.00025) or Algorand ($0.0002) - Fastest confirmation: Solana (sub-second) or Base / Tempo (~2s)
- Most existing wallets: Base (any EVM wallet) or Solana (Phantom et al)
- If your customers already have tokens on a specific chain: just enable that chain
See also
- Per-chain detail pages, one per chain in the navigation under Chains
- x402 protocol for the multi-chain quote shape