Assign Deposit Customer Wallet
Customers
Assign Deposit Customer Wallet
Assigns or returns a deposit wallet for the specified blockchain engine on a deposit customer. If a wallet for that engine already exists, the existing wallet is returned.
POST
Assign Deposit Customer Wallet
Note: When using the production environment at moonpay.hel.io, set your API endpoint to
api.hel.io/v1. For the development environment, use api.dev.hel.io/v1.Authentication
This endpoint is public — it is not API-key authenticated. ThedepositCustomerToken in the path is the credential, so treat it as a secret and only expose it to the customer it belongs to.
Behavior
- Idempotent: If the customer already has a wallet for the requested
blockchainEngineType, the existing wallet is returned instead of creating a duplicate. - On-demand assignment: Use this when a customer selects a network in your UI and you need to provision (or retrieve) the corresponding deposit address.
- HYPERCORE compatibility: Requesting
HYPERCOREmay return an existing EVM wallet that is marked as compatible with Hypercore. - Restricted engines: Some engines (for example
TRON) require your company account to have that engine enabled. Otherwise the request returns400.
Path Parameters
The token associated with the deposit customer.
Body
application/json
The blockchain engine to assign a deposit wallet for.
Available options:
EVM, SOL, BTC, TRON, HYPERCORE, DOGE, TON Response
The assigned deposit wallet for the requested blockchain engine.
Unique identifier of the deposit wallet.
The wallet address for this blockchain.
ISO 8601 timestamp when the wallet was created.
ISO 8601 timestamp when the wallet was last updated.
