Deposit callbacks
Sent to your callback URL whenever the status of a deposit changes.
crypto_address.foreign_id — the same foreign_id you provided when calling /v2/addresses/take. For deposits to addresses created in the portal, which have no foreign_id, use crypto_address.title instead — the name you gave the address when creating it.
- Sender address — adds the sender’s blockchain address as
transactions[].sender.address. - Business wallet transactions — if enabled, callbacks are also sent for deposits to addresses created in the portal and to merchant top-up addresses. These callbacks include the
originfield and, instead offoreign_id, the address name ascrypto_address.title. - Deposits less than minimum amount and Cross-currency deposits callbacks are enabled by default and can be disabled.
Body
Internal transaction ID, the same ID used in /v2/transactions/info.
Deposit type:
deposit: standard depositdeposit_exchange: deposit with automatic conversiondeposit_wallet_client: deposit to a merchant top-up address. Sent only if business wallet transactions callbacks are enabled.
deposit, deposit_exchange, deposit_wallet_client Details of the address the funds were deposited to.
Transactions related to the deposit. Every deposit has one blockchain or internal entry, and deposits with automatic conversion have an additional exchange entry. The transaction_type field shows what each entry is:
blockchain: the incoming transaction on the blockchaininternal: the incoming transaction for an off-chain deposit, which is never sent to the blockchainexchange: the conversion of the deposited currency, present only for deposits with automatic conversion
- blockchain
- internal
- exchange
Fees charged for the deposit. Empty while the deposit is processing and for cancelled deposits.
The reason the deposit was cancelled. Empty string for confirmed and processing deposits. Possible values:
Transaction amount less than minimum deposit: the deposited amount is lower than the minimum allowed for that currencyDouble spend: conflicts with transaction <hash>: the deposit conflicts with another transaction, where<hash>identifies the conflicting transaction. You can look it up in your transaction history to see how it was processed
Deposit status:
confirmed: the deposit has been confirmed and can be treated as final on your side. At this stage, it is safe to perform business actions such as adding funds to the customer's balancenot_confirmed: the transaction has been detected but is still being processed. Wait for theconfirmedcallback before treating the deposit as final. Currencies that support instant confirmations may skip this status. See How deposits are confirmedcancelled: the deposit was cancelled and will not be added to your balance. Sent when the deposited amount is lower than the minimum (no fees are charged), or when the deposit conflicts with another transaction sent to the same address in a double-spend scenario. For a double spend, theerrorfield identifies the conflicting transaction, which you can look up in your transaction history to see how it was processed. Since this transaction is not considered valid, do not add funds to the customer's balance
confirmed, not_confirmed, cancelled The end_user_reference you provided when creating the address via the API. Absent for addresses created in the portal.
For cross-currency deposits, the currency originally assigned to the address, that is, the one you expected to receive. See API currency codes. Absent for other deposits.
The currency and amount sent by the customer. Absent from cancelled deposits.
The currency and amount received after processing or conversion. Absent from cancelled deposits. For deposits with conversion that are still processing, the amounts are 0.
Present for deposits to addresses created in the portal and to merchant top-up addresses. Only present if business wallet transactions callbacks are enabled.
business_wallet