crypto_wallet parameter. Bridge supports two funding strategies for the Stripe integration:
| Strategy | crypto_wallet[type] | Description |
|---|---|---|
| Noncustodial | standard | Funds pulled just-in-time from a wallet your customer controls. Requires an onchain approval to Bridge’s smart contract. |
| Bridge Wallet | bridge_wallet | Funds pulled from a Bridge-custodied wallet you manage via the Bridge API. |
| Stripe Financial Account | N/A | Funds held in a Stripe-managed financial account. This is a Stripe-native feature that doesn’t require Bridge. See the Stripe Financial Accounts documentation for details. |
Noncustodial
With the noncustodial strategy, Bridge pulls funds directly from a wallet controlled by your customer at the time of each card authorization. The customer (or your application) must first set up an onchain approval granting Bridge’s smart contract permission to spend from the wallet. Bridge supports direct pulls from noncustodial wallets on Tempo, Solana, Base, Linea, and we are continually adding support for more EVM chains. This strategy works well when your customers already hold stablecoin balances in their own wallets and you want them to spend directly without maintaining a separate card balance.For Solana, pass the wallet owner address—not the associated token account address. Bridge derives the token account automatically from the owner address and currency.
Bridge Wallet
With the Bridge Wallet strategy, funds are pulled from a Bridge Wallet that you control via the Bridge API. You’re responsible for funding and managing the wallet balance. This strategy works well when you want centralized control over card balances or when integrating cards into an existing Bridge wallet product.address is the address of the Bridge Wallet you want to fund the card from. Once the card is activated, Bridge debits the wallet balance at the time of each authorization.