Invoice Callbacks
First, read general information about callbacks: Callbacks (Webhooks).
We will send a callback on the following events:
deposit_completed
This event happens when we receive a deposit from the customer and successfully transfer this money to your account.
Since we receive a deposit in the channel from your customer, we will send a callback to your server. Here is an example of callbacks by their status:
Below are explanations for some specific fields:
paid_amount
: the amount transferred by the client.paid_amount_minus_fee
: the client's amount after deducting fees.For
received_amount
:In integrations without auto-conversion to USDT, this value will be the same as
paid_amount_minus_fee
.In integrations with auto-conversion, it will be the amount of
paid_amount_minus_fee
converted to USDT, minus the auto-conversion fee.
The amount in
fiat_amounts
may not match the amount specified in the invoice. This is because the invoice amount is calculated at the exchange rate at the time of invoice creation, while the amount infiat_amounts
is calculated at the time of receiving the payment from the client.The difference between fiat/crypto and crypto/crypto pairs is that the
exchange_rate
field is not applicable for crypto/crypto pairs.
Callback Examples with Auto Conversion
If your project has enabled the auto conversion feature, received_currency
and receivied_amount
will contain USDT values. Here is an example:
Auto-conversion. The key distinction when the "auto-conversion" feature is activated lies in the
received_currency
field. In this scenario, the particular stablecoin to which all deposits are converted is consistently specified in this field. Furthermore, a conversion fee is incurred, details of which are outlined in thefees.conversion
field.
Last updated