> ## Documentation Index > Fetch the complete documentation index at: https://docs.privy.io/llms.txt > Use this file to discover all available pages before exploring further. # Fiat-to-crypto onramps > Use the useFiatOnramp hook from @privy-io/react-auth to start a fiat-to-crypto purchase flow in your app This feature is experimental and may change as we iterate. Fiat Onramp Privy provides a `useFiatOnramp` hook in `@privy-io/react-auth` that starts a fiat onramp flow in the Privy modal. Your app can use this hook to let authenticated users buy crypto with supported fiat currencies, such as USD and EUR. Privy routes purchases through supported providers — Meld, MoonPay, and Coinbase — based on availability and user region. ## Access the hook Import and initialize `useFiatOnramp`: ```tsx theme={"system"} import {useFiatOnramp} from '@privy-io/react-auth'; const {fund} = useFiatOnramp(); ``` ## Start a fiat onramp flow Call `fund` with source currency options, and a destination wallet. ```tsx theme={"system"} await fund({ source: { assets: ['usd', 'eur'] }, destination: { asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913', chain: 'eip155:8453', address: '' } }); ``` `destination.chain` accepts a CAIP-2 identifier (for example, `eip155:8453` for Base or `solana:mainnet` for Solana). ## Parameters `fund` accepts an object with the following fields: | Parameter | Type | Description | | --------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `source` | `{assets?: SupportedFiatCurrency[]; defaultAsset?: SupportedFiatCurrency}` | Required. Source currency configuration for the fiat onramp flow. | | `source.assets` | `SupportedFiatCurrency[]` | Optional. The list of fiat source currencies your app allows. Defaults to all [supported currencies](#supported-fiat-currencies). When provided, must be non-empty. | | `source.defaultAsset` | `SupportedFiatCurrency` | Optional. The source currency selected when the flow opens. Falls back to the locale currency, then to the first item in `source.assets`. | | `destination.asset` | `string` | Required. Token address on the destination chain (for example, Base USDC: `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). | | `destination.chain` | `` `${string}:${string}` `` | Required. Destination chain in CAIP-2 format. | | `destination.address` | `string` | Required. Destination wallet address for purchased funds. | | `environment` | `'sandbox' \| 'production'` | Optional. Onramp environment for provider APIs. | | `defaultAmount` | `string` | Optional. Initial fiat amount displayed in the amount step. | ### Supported fiat currencies `SupportedFiatCurrency` accepts any of the following lowercase ISO 4217 codes. Reach out to [sales@privy.io](mailto:sales@privy.io) to request support for additional currencies. | Code | Currency | | ----- | ------------------ | | `usd` | US Dollar | | `eur` | Euro | | `gbp` | British Pound | | `mxn` | Mexican Peso | | `brl` | Brazilian Real | | `cny` | Chinese Yuan | | `jpy` | Japanese Yen | | `inr` | Indian Rupee | | `cad` | Canadian Dollar | | `krw` | South Korean Won | | `aud` | Australian Dollar | | `idr` | Indonesian Rupiah | | `sar` | Saudi Riyal | | `try` | Turkish Lira | | `chf` | Swiss Franc | | `twd` | New Taiwan Dollar | | `sek` | Swedish Krona | | `ngn` | Nigerian Naira | | `pln` | Polish Zloty | | `ars` | Argentine Peso | | `aed` | UAE Dirham | | `thb` | Thai Baht | | `zar` | South African Rand | | `dkk` | Danish Krone | | `egp` | Egyptian Pound | | `myr` | Malaysian Ringgit | | `sgd` | Singapore Dollar | | `cop` | Colombian Peso | | `php` | Philippine Peso | | `clp` | Chilean Peso | | `bdt` | Bangladeshi Taka | | `vnd` | Vietnamese Dong | | `czk` | Czech Koruna | | `ils` | Israeli Shekel | | `hkd` | Hong Kong Dollar | | `nzd` | New Zealand Dollar | | `pkr` | Pakistani Rupee | | `ron` | Romanian Leu | | `kzt` | Kazakhstani Tenge | | `nok` | Norwegian Krone | | `huf` | Hungarian Forint | | `uah` | Ukrainian Hryvnia | | `kwd` | Kuwaiti Dinar | | `qar` | Qatari Riyal | | `etb` | Ethiopian Birr | | `mad` | Moroccan Dirham | | `bgn` | Bulgarian Lev | | `kes` | Kenyan Shilling | | `npr` | Nepalese Rupee | ## Return value `fund` returns a Promise with one of the following statuses: | Status | Meaning | | ------------- | ---------------------------------------------------------------------------------------------- | | `'submitted'` | The user completed the provider flow, then exited before final confirmation finished in Privy. | | `'confirmed'` | The flow reached provider confirmation, and the user completed the success step. | ## Error handling `fund` rejects on invalid configuration or incomplete flows. Common error cases include: * `source.assets` is empty * another fiat onramp flow is already in progress * the user closes the flow before submitting a purchase * provider session or status requests fail Your app should wrap calls in `try/catch` and show clear UI feedback. ## Complete example ```tsx theme={"system"} import {useState} from 'react'; import {useFiatOnramp} from '@privy-io/react-auth'; export const BuyUsdcButton = ({address}: {address: string}) => { const {fund} = useFiatOnramp(); const [isLoading, setIsLoading] = useState(false); const onBuyUsdc = async () => { setIsLoading(true); try { const result = await fund({ source: { assets: ['usd', 'eur', 'gbp'], defaultAsset: 'usd' }, destination: { asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913', chain: 'eip155:8453', address }, environment: 'production', defaultAmount: '50' }); if (result.status === 'confirmed') { // Update post-purchase UI immediately. } if (result.status === 'submitted') { // Show pending state while the provider finalizes the transaction. } } catch (error) { // Show retry UI or an error banner. console.error(error); } finally { setIsLoading(false); } }; return ( ); }; ``` ## Use with deposit addresses Apps that already use deposit addresses to receive funds on behalf of users can pass that address directly as the `destination.address` in the `fund` call. The onramp flow purchases the specified crypto asset and delivers it straight to the deposit address, letting your app credit the user's account through your existing settlement logic. ```tsx {7-9} theme={"system"} const onFundDepositAddress = async () => { return await fund({ source: { assets: ['usd'] }, destination: { address: depositAddress, asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913', chain: 'eip155:8453' } }); }; ``` The `destination.address` does not need to be the user's own wallet. It can be any valid address your app controls, such as a per-user deposit address generated by your backend. Set `destination.asset` to the token address and `destination.chain` to the network that the deposit address expects as input. ## Stripe Embedded Components onramp Privy supports [Stripe's Embedded Components for Crypto Onramp](https://docs.stripe.com/crypto/onramp/embedded-components) as a payment option within the fiat onramp flow. Stripe provides an embedded UX that handles payment processing, KYC via [Link](https://link.com/), and crypto delivery directly to the user's wallet. Requires `@privy-io/react-auth` version **3.32.0** or later. Install the `@stripe/crypto` package as a required dependency: ```bash theme={"system"} pnpm install @stripe/crypto ``` Supported payment methods include credit, debit, Apple Pay, Google Pay, and ACH (US only). Supported destination currencies include USDC (Base, Solana, Ethereum, and Arbitrum). Available in the US (excluding New York). EU support coming soon. Official Stripe Embedded Components onramp documentation *** Looking for the legacy `useFundWallet` hook? It's still available for [EVM](/wallets/funding/legacy/evm) and [Solana](/wallets/funding/legacy/solana).