Stellar is fully supported for onramps, offramps, and swaps. It also has the most chain-specific setup of any supported network — assets require trustlines, wallets need a small XLM balance for reserves and fees, and pre-built transactions expire quickly. This page covers everything Stellar-specific; the end-to-end flows live in the Onramps, Offramps, and Swaps guides.
Supported operations
| Operation | Supported |
|---|---|
| Onramp (fiat → token) | ✓ |
| Offramp (token → fiat) | ✓ |
| Swap (token → token) | ✓ |
Asset identifiers
Stellar assets useCODE:ISSUER format — e.g. CETES:GC3CW7EDYRTWQ635VDIGY6S4ZUF5L6TQ7AA4MWS7LEQDBLUSZXV7UPS4.
Stablebond addresses
Live asset issuers for every stablebond on Stellar, each linked to Stellar Expert:Wallet & gas requirements
Holding and receiving Stellar assets requires XLM for the account reserve and per-asset trustlines. These are Stellar network requirements, not Etherfuse fees:- ~1 XLM base reserve to create the account on-chain.
- ~0.5 XLM additional reserve per trustline (so ~1.5 XLM for an account holding one asset).
- A few stroops per transaction for the network fee — keeping ~0.01 XLM on a wallet covers thousands of transactions.
Self-custody wallets hold their own XLM. A bring-your-own Stellar wallet must currently hold its own XLM to cover reserves and fees, except on onramps quoted with
walletAddress, where Etherfuse prices account creation and the target trustline into the quote fee and funds the wallet as part of the onramp (see Onramps: first-time wallets below). (Gasless offramps are available on EVM chains; see Base. Centralized gas sponsorship for self-custody Stellar wallets is on the roadmap.)Embedded wallets are the exception: Etherfuse fee-bumps every transaction and folds account reserve and trustline setup into the ramp fee on the wallet’s first onramp (quote with walletAddress). The partner never sends XLM; see Embedded Wallets.Trustlines
A wallet must hold a trustline for any asset it will receive. For onramps, Etherfuse can create the trustline for you (see below). For offramps and swaps, the wallet must already have the trustline and enough XLM before you create the order.Onramps: first-time wallets are handled automatically
When onramping to a wallet that doesn’t yet exist on-chain or lacks the target trustline, passwalletAddress in the quote request. Etherfuse funds the account and adds the trustline for you, folding a one-time cost into the quote fee, and delivers the tokens as a claimable balance the user signs for afterward. This sponsorship applies to onramps only; offramps and swaps require the wallet to already exist and be funded.
See Onramps → Stellar: First-Time Wallet Onramp for the full claimable-balance flow (stellarClaimableBalanceId + stellarClaimTransaction).
Offramps and swaps: fund the wallet first
Transaction expiry and regeneration
Pre-built Stellar transactions (burn, swap send, and claim XDRs) are short-lived — roughly 1–2 minutes. Submitting a stale one returnstx_too_late from Horizon.
Regenerate a fresh transaction instead of reusing an expired one:
- Offramp —
POST /ramp/order/{order_id}/regenerate_tx. Returns202; the newburnTransactionarrives over theorder_updatedwebhook. - Swap —
POST /ramp/swap/{order_id}/regenerate_tx. Returns202; the newsendTransactionarrives over theswap_updatedwebhook. - Onramp claim with a stale sequence number — if the user transacted on Stellar before claiming, the stored claim XDR’s sequence number goes stale. The same
POST /ramp/order/{order_id}/regenerate_txrebuilds it and returns200with a fresh XDR, also updating the order’sstellarClaimTransaction.
Anchor mode (SEP-24)
For Stellar offramps you can use anchor mode (useAnchor: true) instead of the default burn-transaction flow — Etherfuse returns a destination account + memo and you build the payment yourself. See Offramps → Anchor Mode.