Skip to main content
A deposit account gives a wallet a dedicated set of bank details. Creating one requires a verified entity on the wallet — see setup.
To create a fiat deposit account for a wallet, make a POST request to:
See the API reference for the full request and response schema.In the body of the request, include the following fields:
'bridge'
required
Provider to orchestrate the deposit account with.
'production' | 'sandbox'
Provider environment to use. Defaults to production.
object
required
The fiat the account receives.
object
required
The crypto the deposit is converted into and delivered as.
object
Who sends deposits into the account, for EU travel rule compliance. Omit when the verified entity on the wallet sends deposits from its own bank account. See travel rule.
Deposit accounts are persistent, billed resources at the provider. Pass a privy-idempotency-key header so a retried request returns the original response instead of failing or provisioning a second account. See idempotency keys.
Below is a sample cURL command for this request:
A successful response includes the following fields:
object
The deposit account.
Display deposit_instructions to the user so they can send a transfer from their bank. No memo or reference code is required — the account is dedicated to this wallet.

Travel rule

EU rules require the provider to record who is on each side of a transfer between a bank account and a wallet. Privy fills in the wallet side from how the wallet is owned. Your app describes the bank side, the sender of the deposits, with travel_rule.source. For example, to specify that a business other than the verified entity funds the account:
Privy passes travel rule information to the provider when it creates the account. If the wallet already has an account with the same currency, asset, chain, environment, and fee, a request without travel_rule returns that account. A request with travel_rule returns a 409 error. To change an existing account’s travel rule information, update the account instead.

Update travel rule information

To change who sends deposits into an existing account, make a PATCH request to:
See the API reference for the full request and response schema. The request body accepts a required travel_rule object with the same source fields as creation. Privy replaces the account’s travel rule information at the provider and derives the wallet side again. The response returns the deposit account, unchanged. The update applies to deposits the account receives afterward. Deposits the account already received keep the travel rule information they were recorded with.
Accounts created before travel rule support have no travel rule information on file. EUR deposits above €1,000 require it. Send {"travel_rule": {"source": {"type": "self"}}} to record the verified entity as the sender and have Privy fill in the wallet side.
Switching an account back to a sender it had before is not currently supported. The provider keeps the most recent sender in place. Update an account only to a sender it has not had.

Next steps

Get deposit accounts

Read a wallet’s deposit accounts and their bank details

Deposit lifecycle

Follow a deposit from bank transfer to on-chain settlement