Stellar

​

At a glance

​

Memo binding

Stellar’s MEMO_TEXT field is capped at 28 bytes UTF-8. The standard algovoi:{token} (32-char token plus prefix) doesn’t fit. AlgoVoi uses a shortened form: av:{token[:20]} for Stellar checkouts, which fits inside the 28-byte limit. The verifier reads this short prefix from MEMO_TEXT and looks up the token in the active links table. MEMO_HASH and MEMO_ID are not used.

​

Trustlines

Stellar requires a trustline for any non-native asset. A new payout address must establish a trustline to USDC (Circle issuer GA5ZSEJY…) before receiving payments. The dashboard validates the trustline when you save the address. For multi-asset support (USDC plus XLM payouts), you need separate trustlines for each non-native asset.

​

Path payments and fee bumps

Stellar’s path_payment and fee_bump_transaction operations are supported by the verifier. If your customer pays in EURC and you accept USDC, the on-chain path-payment delivers USDC to your address and the verifier sees only the destination leg.

​

Wallets

• Lobstr
• Freighter (browser extension)
• Solar Wallet

​

xChain — pay from MetaMask, settle on Stellar

Stellar xChain is live on mainnet (since 2026-05-05). Tenants on stellar_mainnet get the xChain tab on every hosted checkout, letting customers holding USDC on EVM chains (Base, Arbitrum, Polygon, Optimism, Ethereum, BNB Chain, Avalanche) pay a Stellar checkout from MetaMask without ever installing a Stellar wallet. Two routing protocols:

• Allbridge Core ✅ live mainnet — calls Allbridge’s swap-and-bridge route, which invokes a Soroban swap pool that auto-converts to canonical Stellar USDC at Circle’s classic issuer (GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN) and credits the merchant’s Stellar address directly. Any Stellar wallet supports this asset — no Soroban-aware wallet required (Lobstr, Solar, Stellarport, LumenWallet, Freighter etc. all work). ~60-120s end-to-end.
• Circle CCTP V2 🟡 awaiting Circle mainnet — will deliver native Circle USDC via mint_and_forward once Circle ships Stellar mainnet contracts publicly. ~50-90s, zero slippage. Code path is stubbed.

Both protocols share the same xChain attempts pipeline. The merchant sets xchain_destination_chain = 'stellar' (via dashboard or PATCH /internal/tenants/{id}/xchain) and provides a Stellar payout address (G… classic account); AlgoVoi picks the right bridge protocol per attempt and the destination-side scanner verifies delivery by polling Horizon for an account_credited effect against the merchant’s address. See xChain payments for the unified flow.

​

See also

• x402 protocol for the payment protocol layer
• Concept: chains overview for cross-chain comparison
• xChain payments — pay Stellar checkouts from MetaMask (live via Allbridge Core)