Solana

​

At a glance

​

Solana Pay reference binding

Solana doesn’t support arbitrary memos in the way Algorand or Hedera do. Instead, AlgoVoi uses Solana Pay’s reference mechanism: a fresh ed25519 public key generated per checkout, included as a non-signer account in the settlement transaction. For each Solana checkout:

1. AlgoVoi generates a new ed25519 keypair. Only the public key is stored in the database.
2. The Solana Pay URL on the checkout page includes ?reference={pubkey} alongside amount and spl-token.
3. The wallet builds a transaction that includes that pubkey as a non-signer account.
4. The verifier looks up the settling tx via getSignaturesForAddress(reference) against a managed RPC.
5. The match is cryptographic: no other transaction can satisfy this checkout, even if it sends the right amount to the right address.

This is the same mechanism Solana Actions and Blinks use to bind a Blink to a specific checkout.

​

Associated token accounts

Like SPL tokens generally, USDC requires an associated token account (ATA) on the recipient side. AlgoVoi auto-detects whether the payout’s ATA exists and creates it as part of the first transfer if needed (paying the small rent fee, which is reimbursed from the next confirmed payment).

​

Wallets

• Phantom
• Solflare
• Backpack

​

xChain — pay from MetaMask, settle on Solana

Tenants on solana_mainnet automatically get the xChain tab on every hosted checkout. A customer holding USDC on any of seven EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB, Avalanche) can pay the Solana checkout from MetaMask without installing Phantom or any other Solana wallet. Default routing: Circle CCTP V2 Fast Transfer. End-to-end ~50-90s (~30s source-tx confirmation + ~30s Iris attestation + ~5-10s relayer claim). Zero pool slippage — the customer pays the bridge amount and the merchant receives it minus only Circle’s small Fast Transfer fee (capped at 14 bps), absorbed by AlgoVoi’s slippage tolerance. Allbridge Core is available as a fallback for any source chain CCTP doesn’t support (e.g. BNB Chain) — ~90-120s, ~0.3% combined pool fee. The merchant sees a normal Solana payment land at their payout wallet; the AlgoVoi facilitator’s standard SolanaVerifier confirms the destination transaction the same way it confirms direct Solana Pay payments. No extra integration work for the merchant. See xChain payments for the full flow + bridge-source list.

​

See also

• Solana Actions and Blinks for the Blink rendering
• x402 protocol for the payment protocol layer
• xChain payments — pay Solana checkouts from MetaMask, no Phantom required