Skip to main content
Avalanche We support onramps and offramps on Avalanche C-Chain, including MEXe. Avalanche is an EVM chain, so assets are plain ERC-20 contracts. The end-to-end flows are in the Onramps and Offramps guides.

​
Supported operations

​
Asset identifiers

Avalanche assets are identified by the raw token contract address only.
Do not prefix with a symbol. A SYMBOL:0x... identifier (the Stellar-style format) fails on an EVM chain. Pass only the 0x... address, the token’s asset from GET /supported_assets?chain=avalanche.

​
Stablebond addresses

Live token-contract addresses for every stablebond on Avalanche, each linked to Snowtrace:

​
Register an Avalanche wallet

Register the wallet as a payment account with accountDetails of kind address and chain avalanche. Set $ORGANIZATION_ID to the organization that owns the wallet: your own organization or a customer organization. See Organizations in the route.
Use the returned id as the source or destination of a quote. An EVM address is valid on every EVM chain, so the account’s rails can list more than one EVM chain. Set sourceRail or destinationRail to avalanche in the quote to pick this chain.

​
Offramps

On an Avalanche offramp, the order’s fundingInstructions.rail is avalanche, and fundingInstructions.destination gives the address to send the token to. The source asset is an ERC-20 token. When preparedTransaction is present, its transaction is an unsigned EIP-1559 transaction, 0x-prefixed hex, that calls the token’s transfer from the customer’s wallet. The customer signs it, submits it and pays the gas in AVAX. Otherwise, send the order’s source.amount of source.asset to address. The prepared transaction uses the wallet’s next nonce, so it goes stale if the wallet sends another transaction first. Then call POST /organization/{organizationId}/order/{id}/funding_instructions/refresh and sign the new one. See Offramps.

Onramps

Offramps