Deposit callback
Data received after a deposit is made to one of your created wallets (addresses)
Last updated
Was this helpful?
Data received after a deposit is made to one of your created wallets (addresses)
Last updated
Was this helpful?
To receive callbacks make sure you registered your URLs on . There are three options, one for pending , one for confirmed deposits, and one for failed deposits.
Pending Deposits: Receive callbacks as soon as the (Layer 1) transaction is registered on and , but before it has been confirmed on the L1 network (i.e. before nodes have verified it or enough blocks have been created/mined on top)
Deposits: Receive callback when the transaction is confirmed (through sufficient blocks/nodes) on Layer 1 . Transactions that failed to confirm will also be included here. As for L2 transactions, since they are near-instant they will also be included here.
Failed Deposits: Receive callbacks if the transaction fails to complete on Layer 1, even though it might have been registered/broadcast. In this case, funds should not be credited.
We recommend always setting the Deposit URL. If you'd like more control and to receive information earlier, also set the URL for pending deposits - but be aware that deposits that show up as pending are not final and may still fail (albeit rarely). (They could be the same URL!)
Note: If the response to the callback has a status code >= 400, the callback is retried up to 15 times with increasing delays up to around 10hrs since the first attempt.
If you are managing the balance of users in your system, please note that the amount in the callback does not include the charged on you. If you would like to credit your user with the actual available funds you should subtract internalFee.deposit
from the amount.
Note:
l2Txnhash
(the "L2-hash") should always be used as the unique identifier of a transaction. This is a unique transaction-hash for any transaction on . It is present for Confirmed deposits and Pending/Confirmed payouts. This is particularly important for the case of transactions, which will not have a Layer 1 hash (txHash
)
Note:
internalFee
refers to the associated with transactions on AkashicChain.
Note: Deposit callbacks are not sent for Layer 1 deposits with a value less than 1 USDT.
Note the lack of l2TxnHash
Refer to "Pending" above. Differences pointed out
Note that because of the fees, the actual funds under your control are: 10.0 - 0.1 = 9.9
If user is sending assets from , it will be executed in , which is our Layer 2 blockchain to reduce the gas fee and cost in Layer 1.