# Choose a funding strategy for stablecoin-backed cards

Compare the wallets that stablecoin-backed cards can spend from, and choose the integration that fits how your users hold funds.

Stablecoin balances fund every stablecoin-backed card. Your funding strategy determines where you hold those funds, who controls them, and when they move. Choose a strategy to find the integration guide to follow.

## Compare funding strategies

You can fund cards from a Bridge wallet, a non-custodial wallet such as a [Privy](https://docs.stripe.com/stablecoins/ecosystem/privy.md) wallet, or a Stripe financial account.

|  | Bridge wallet | Non-custodial wallet | Financial account (Private preview) |
| --- | --- | --- | --- |
| **Who controls the funds** | You, through the Bridge API | Your user, or you on their behalf, such as through a [Privy](https://docs.stripe.com/stablecoins/ecosystem/privy.md) wallet | You, through Stripe APIs |
| **Where funds are held** | A wallet that Bridge holds in custody | A wallet that Bridge doesn’t hold in custody | A financial account that Stripe holds in custody for a connected account |
| **When funds move** | Bridge pulls funds from the wallet when the card is authorized. | Bridge pulls funds onchain from the wallet when the card is authorized. | The card spends from the financial account balance. |
| **Onchain approval required** | No | Yes, before the first purchase | No |
| **Where refunds and excess funds go** | The user’s Bridge wallet | The user’s non-custodial wallet | The connected account’s financial account |
| **Balance tracking** | Bridge wallets API | Onchain. Bridge doesn’t track the wallet balance. | [Financial Accounts v2 API](https://docs.stripe.com/api/v2/money-management/financial-accounts.md) |
| **Customer verification** | Bridge | Bridge | Stripe, through Connect onboarding |
| **Program types** | Consumer and commercial | Consumer and commercial | Commercial |
| **Privy prebuilt components** | Not supported | Supported for Privy wallets only | Not supported |
| **Card parameter** | `crypto_wallet[type]=bridge_wallet` | `crypto_wallet[type]=standard` | `financial_account_v2` |

## Choose a strategy for your use case

Choose the strategy that matches how your users hold funds today:

- **Your users already hold stablecoins in their own wallets**: Use a non-custodial wallet. This fits wallet apps, crypto-native products for consumers or businesses, and platforms that use [Privy](https://docs.privy.io/) embedded wallets. Your users keep control of their funds, and Bridge pulls only the amount of each purchase.
- **You manage balances on behalf of your users or businesses**: Use a Bridge wallet. This fits programs where many cards or cardholders spend from balances that you fund and track centrally. You manage balances with the Bridge API, and you don’t need onchain approvals.
- **You run a Connect platform and want to manage financial accounts through Stripe**: Use financial accounts. This fits platforms that already onboard connected accounts with Stripe, that accept payments with Stripe and want to spend those funds, or that run fiat and stablecoin card programs together. You use only Stripe APIs.

If your users hold funds in a custodial wallet from another provider, [contact Stripe](https://stripe.com/contact/embedded-finance) to check whether the Stripe card contracts support it. Alternatively, create a separate wallet for card payments that users fund from their existing wallet.

## Wallet-sharing rules 

Program rules limit which cards can spend from the same wallet:

- **Consumer programs**: Each wallet can belong to only one cardholder.
- **Commercial programs**: Multiple cards and cardholders can share a wallet if they belong to the same business and its connected account.

## Supported stablecoins and chains

Your funding strategy determines which stablecoins and chains you can use. Review the [supported stablecoins and chains](https://docs.stripe.com/stablecoins/availability.md#issuing), and contact your Stripe account manager to confirm support for a specific stablecoin.

## Integration guides

Follow the guide for your funding strategy.

- [Bridge wallets and non-custodial wallets](https://docs.stripe.com/issuing/bridge-stablecoin-cards.md): Onboard customers with Bridge and issue cards that spend from a Bridge wallet or a non-custodial wallet.
- [Financial accounts](https://docs.stripe.com/issuing/stablecoin-cards-for-financial-accounts.md) (Private preview): Set up a Connect platform that issues cards backed by stablecoin balances in financial accounts.
- [Privy prebuilt card components](https://docs.privy.io/financial-flows/cards/pre-built-components/overview): Add consumer cards that spend from Privy wallets with Privy’s prebuilt components, which handle the Bridge and Stripe integration for you.

If you use non-custodial wallets, you also need to [set up onchain approvals](https://docs.stripe.com/issuing/bridge-stablecoin-cards/noncustodial-wallets.md) so that Bridge can pull funds from each wallet.