Skip to main content
Deposit destinations are crypto addresses that your customers or external parties can use to send funds directly. When a deposit arrives, the corresponding account’s balance is credited automatically. A destination can also act as a liquidation address, automatically converting incoming funds into a different asset before crediting the account. This is the primary mechanism for receiving inbound crypto payments into your custodial accounts.

​
How deposit destinations fit your integration

  1. Create a deposit destination for a specific account and network.
  2. Optional: Set a target to liquidate incoming funds into a different asset.
  3. The API returns a blockchain address for that network and account.
  4. Share that address with the sender (customer, invoice payer, counterparty).
  5. When funds arrive on-chain, the account’s balance is credited automatically.
  6. A payments.transfers.completed webhook fires when the deposit settles.
In the API, the resource is called a “deposit destination.” The CDP Portal UI displays the same concept as a “deposit address.”

​
Deposit destination types

TypeBehavior
Deposit (no target)Receives the asset on the specified network and credits the account balance in the same asset
Liquidation (target set)Receives the asset, then liquidates it into the target asset on the target account

​
Supported assets and networks

Supported assets, networks, and settlement behavior depend on your entity configuration and environment. Use Supported networks and assets as the source of truth for what you can hold and move in each environment.
Only send supported assets to your deposit destinations. Sending unsupported assets or using unsupported networks may result in permanent loss of funds.If you accidentally send unsupported crypto, you may be able to recover it using Coinbase’s asset recovery service.

​
Core API operations

OperationWhat it does
Create deposit destinationPOST /v2/deposit-destinations — provision a new crypto address tied to an account (optional target, optional metadata)
Get deposit destinationGET /v2/deposit-destinations/{depositDestinationId} — fetch a single deposit destination by ID
List deposit destinationsGET /v2/deposit-destinations — paginated destinations for your entity (filter by account, network, or address)

​
Metadata

You can attach metadata to any deposit destination to track the purpose or source of deposits. Metadata is returned with the deposit destination object, transfer records, and webhook notifications.

Quickstart

Create a deposit destination and simulate an inbound deposit

REST API reference

Full API reference for deposit destination operations

Transfers

Move funds from an account to an external address or payment method

Webhooks

Subscribe to deposit events in real time