Fiat Off-Ramps
Fiat off-ramp providers enable you to trade Sui-native tokens (SUI, WAL, DEEP, and others) for fiat currency that can be withdrawn to a user's bank account, card, or payment method. Embedding an off-ramp provider into your app allows users to convert their Sui assets to traditional currency without leaving your interface. Verify current provider capabilities before integrating.
The following table summarizes providers that document Sui off-ramp support. All columns refer to Sui chain and Sui asset support specifically. Provider asset support and regional availability change frequently, so confirm current capabilities with your chosen provider before launching an integration.
Off-ramp coverage is evolving. Provider asset support and regional availability change frequently. Confirm current capabilities with your chosen provider before launching an integration.
| Provider | Supported assets | Documentation |
|---|---|---|
| Banxa | SUI | Banxa docs |
| Bridge.xyz | USDSui | Bridge docs |
| Coinbase | SUI, USDC, WAL, DEEP | Coinbase CDP docs |
| Alchemy Pay | AUSD, SUI, USD | Alchemy Pay docs |
| CoinVoyage | Sui Dollar | CoinVoyage docs |
| Onramper | SUI | Onramper docs |
| Meld | SUI, USDC, CETUS, NAVI | Meld docs |
See Fiat On-Ramps for the full on-ramp provider list.
Asset limitations
When you choose off-ramp providers, be aware of the following limitations:
-
USDC off-ramp on Sui: USDC off-ramp coverage on Sui is available through fewer providers than SUI, such as Coinbase and Meld. If your users need to off-ramp USDC, confirm provider support directly.
-
SUI sell limits: Off-ramp providers might enforce sell limits. Confirm limitations with the provider directly.
-
KYC requirements: Off-ramp flows likely require Know Your Customer (KYC) verification. Factor this into your user experience design.
How does a fiat off-ramp integration work?
Before you start, you need a backend that can call the provider's API and API credentials from your chosen provider.
Most off-ramp providers follow a similar integration pattern:
- Your app collects the user's wallet address and the asset they want to sell.
- Your backend generates a signed session or redirect URL using the provider's API and your API credentials.
- The user completes the off-ramp flow in a hosted widget or redirect, including KYC verification if required.
- The provider transfers fiat to the user's bank account or card.
The specific parameters, authentication method, and webhook events differ by provider. Review the provider's documentation before building.
Which off-ramp provider should you choose?
Provider selection depends on your users' geography, the assets you support, and your integration preferences. Consider the following when evaluating:
- Asset coverage: Only some providers support assets beyond SUI. If your app uses USDC, DEEP, or other tokens, confirm the provider supports those assets on Sui specifically.
- Regional availability: Off-ramp payouts (bank transfers, card withdrawals) are subject to local financial regulations. Confirm the provider supports your target markets.
- Integration model: Some providers offer embeddable widgets; others use redirect-based flows or headless APIs. Choose the model that fits your app's user experience.
- KYC handling: All fiat off-ramp flows require identity verification. Some providers handle KYC entirely within their hosted flow; others require you to collect and pass user data. Understand your compliance obligations before integrating.