> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.bridge.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Prefunded wallets

Prefunded wallets are Bridge Wallets designed to hold developer-funded liquidity for payments across multiple customers.

* **Prefunded Wallets** can be used as the source of outbound transfers for multiple customers by setting `on_behalf_of` to the customer for each transfer.
* **Bridge Wallets** can only be used as the source of an outbound transfer when `on_behalf_of` is the same `customer_id` that owns the wallet.

The destination can be an external account, crypto address, or another customer's Bridge Wallet. This source-wallet restriction applies to outbound transfers, including off-ramps and crypto-to-crypto transfers.

Prefunded wallets allow you to maintain a balance of funds to power **instant on-ramps and off-ramps** for your customers. These wallets hold a stablecoin of your choosing, and can orchestrate into any Bridge-supported asset.

This can be useful in payroll scenarios where you may want to disperse ACH payments for multiple employees using one general liquidity wallet.

### **Funding a prefunded wallet**

Prefunded wallets can be funded with any Bridge-supported source asset. Use any of our [Orchestration products](https://apidocs.bridge.xyz/platform/orchestration/overview) with a Bridge wallet destination to add funds to your prefunded wallet.

### **Tracking prefunded wallet activity**

Subscribe your webhook endpoint to `bridge_wallet.activity` to receive events when a prefunded wallet balance changes. These events use the Bridge Wallet activity schema and include fields such as `bridge_wallet_id`, `available_balance`, `source`, `destination`, and `type`.

If you fund a prefunded wallet through fiat deposit instructions, Bridge may also emit `virtual_account.activity` or `static_memo.activity` webhooks for the fiat instruction lifecycle. Use `bridge_wallet.activity` when you need to know when the prefunded wallet balance itself has been credited or debited.

### **Paying out from a prefunded wallet**

A prefunded wallet can be debited via our [Transfers API](/platform/orchestration/transfers/transfer-features), with the Bridge Wallet ID and relevant asset as the source for the transfer.

## **Common use-cases**

**1. Instant On-Ramps:** For use-cases where speed is paramount, developers can leverage prefunded wallets to hold a balance with Bridge and instantly draw down on it, via API, and facilitate payments out to many end-users.

**2. Card Acquiring:** Card transactions typically settle on a T+2 basis, meaning funds aren't available for 1–2 business days after a user swipes. For developers building card-to-stablecoin flows, this delay creates a poor user experience. By holding a balance in a prefunded wallet, developers can instantly credit users with stablecoins at the moment of purchase, long before card settlement completes.

**3. Liquidity Management** Developers with complex liquidity management needs leverage prefunded wallets to settle batched payments to Bridge and trigger many payouts from their balance. These batches lower per-transaction fees by spreading fixed fees across many payouts.