Skip to main content

​
At a glance

​
Memo binding

Algorand transactions can carry a 1KB note field. AlgoVoi uses this to bind on-chain payments to specific checkouts. Every hosted-checkout link generates a memo of the form algovoi:{token} (where {token} is the 32-character link token). Senders must include this memo for the transaction to count. The verifier reads the memo and matches against the active links table. Self-payments (payer address equals payout address) are blocked at this layer.

​
Payout addresses

A payout address is just a regular Algorand wallet address (58-character base32). The address must have opted in to USDC ASA 31566704 (or 10458941 on testnet) before receiving USDC. Algorand requires opt-in for any non-native asset. If you set a payout address that hasn’t opted in, payments will fail at the chain level. The dashboard validates opt-in when you save the address.

​
Wallets

Most popular Algorand wallets work for both senders (your customers) and receivers (your payouts): For programmatic settlement (running a server-side wallet that sweeps incoming payments), the algosdk and py-algorand-sdk cover the standard library surface.

​
Account abstraction

Algorand supports rekeying: an address can hand control to a different signer without changing the address. AlgoVoi’s facilitator does not require this, but it’s available if you want to delegate signing for high-volume tenants.

​
xChain — MetaMask payments

Algorand mainnet checkouts support xChain: MetaMask users on any EVM chain can pay without an Algorand wallet. Their EVM address maps to a deterministic Algorand LogicSig address; they sign an EIP-712 message in MetaMask to authorise the Algorand transaction. If they need to fund the address first, Allbridge Core bridges USDC from Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, or Avalanche in ~2–4 minutes. No merchant action is required — the xChain tab appears automatically on every Algorand mainnet hosted-checkout page. Full xChain documentation →

​
Agent-to-agent settlement on Algorand

Algorand signs its own State Proofs with Falcon, the same post-quantum signature family AlgoVoi uses to authenticate agents. The chain is securing its consensus against quantum attack; AlgoVoi Mesh secures the two agents transacting across it. Chain and agent speak the same post-quantum scheme, which makes Algorand the most natural home for post-quantum agentic payments. AlgoVoi Mesh settles a payment directly between two autonomous agents on Algorand. Each agent verifies the other offline with a Falcon-1024 credential, the pair negotiates Algorand as the settlement chain, and the authorized decision lands in the transaction note as one content-addressed execution_ref. There is no facilitator, no per-transaction fee, and no AlgoVoi service in the trust path at settlement time. Proven on-chain. A mutually verified Falcon-1024 pair negotiated Algorand and settled once: Open it and read the note. It carries algovoi-mesh:sha256:c49ae862..., the exact execution reference that run’s handshake produced. Recompute it yourself from the raw fields with a stock RFC 8785 (JCS) implementation and SHA-256; no AlgoVoi software is involved in checking it. The chain never verifies Falcon. It only carries the 32 byte anchor, which is why the same agent trust works on Algorand and on every other chain the pair could have chosen. The same key and the same code path also settle on VOI mainnet, a different AVM network, with nothing changed but the endpoint. See AlgoVoi Mesh for the mutual handshake, the signed chain-offer negotiation, and the full eight-chain proof.

​
See also

  • xChain payments — MetaMask → Algorand via ECDSA LogicSig and Allbridge bridge
  • VOI is a fork-and-go cousin with the same SDKs and a different fee model.
  • Quickstart uses Algorand testnet as the default first integration.