Payout callback
Data received after a payout is made from one of your created wallets (addresses)
To receive callbacks make sure you registered your URLs on AkashicPay.com.
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.
Example
Payout (L1Transaction)
A note on withdrawal fees
There are a few different components in play regarding fees when doing a withdrawal. These are:
Akashic Fee (
internalFee.withdraw
in callback), always in the same currency as the transaction. I.e. ETH for an ETH transfer, USDT for a USDT transfer, etc. Normally 0 unless "fee delegation" happens, see below.Gas Fee (
feesPaid
in callback), always in native coin (e.g. ETH for a ERC20 USDT transfer, TRX for a TRC20 USDT transfer, etc.). Charged by the L1 networks (Ethereum, Tron, etc.)"Fee Delegation". The Akashic system lets you pay for the aforementioned native fee in tokens instead of native coin to simplify matters. If this is done,
feeIsDelegated
will betrue
in the callback. All withdrawals done using the SDK should be "delegated" while withdrawals initating from AkashicLink will not by default. The extra token-amount needed to "delegate" the fee is ininternalFee.withdraw
Using this, to calculate the total amount spent by a user we can do (assuming callback data of the form shown above is in txCallback
):
Note that the above is pseudocode. You would probably need to take extra care of handling potential undefined/null values like internalFee
as well as parse the numbers safely and correctly, following normal practices in your chosen programming language.
Last updated