key
and secret
key: Same client key
secret: Same client secret
key
and secret
to check the validity of the request and make sure that this request is coming from Vault. (In more advanced scenarios HMAC-signature structure can be configured)txid
and address
of the deposit on your database as unique values
when you receive the transaction if you are relying on webhook to avoid processing transactions if you receive the webhook multiple times.is_confirmed
and is_suspicious
in the data you receive on your server. The webhook notifications are always sent when the deposit is confirmed. Often you receive the first webhook notification with status is_confirmed: false
which is used to notify about an incoming deposit. In these cases do not assume the deposit is confirmed and wait for the next webhook notifications with is_confirmed: true
before you process it.currency
is the token symbol and you can find the blockchain name in the network
field. e.g. currency: usdt, network: eth
key
and secret
.api-signature
provided along with the api-nonce
in the request header.