Skip to main content
All CollectionsFrequently Asked Questions
What compliance information can be included in transaction webhooks?
What compliance information can be included in transaction webhooks?
Support Lead avatar
Written by Support Lead
Updated over a week ago

Bitpanda Custody can now include compliance data in the body of our webhooks.

How does it work?

Whenever a Bitcoin or Ethereum transaction reaches our platform, our system will run a KYT check on it. Our platform will flag its risk level (high risk, low risk or unknown) and that information will be added to the property complianceInfo in the webhook payload.

This new property will provide useful and realtime information about any potential risky funds on any incoming transactions. Users can utilise this information at their discretion and take actions like quarantining the funds until a thorough investigation is completed.

This is an example of what complianceInfo would look like in the payload:

"asset": "BTC",
"transferReference": "b1141feb04e36090061961183a0e0137371b25dd4af1d41a66cab4e8023bd4c0:132rjmbFRDuyka9jJxrWNchhupBQjqJkB5",
"status": "SUCCESS",
"decision": "ALLOW",
"data": {
"riskRating": "UNKNOWN",
"cluster": {
"name": null,
"category": null

You can refer to our Webhook API documentation for full details.

Field Definition

Field Name



BTC / ETH or a ERC20 token such us USDT, OMG...


transactionHash : address (the address receiving funds)


SUCCESS indicates Bitpanda Custody successfully managed to query its KYT partner.


ALLOW / QUARANTINE. Bitpanda Custody will flag with a QUARANTINE warning any transactions that are high risk from one of of the following categories:

  • child abuse material

  • sanctions

  • terrorist financing

Users are advised to quarantine the received funds until they have established the legitimacy of the transaction.


UNKNOWN /HIGH/ LOW: Risk level associated with the transaction. Unknown risk means there is no known entity associated with the address


Addresses are added to clusters. This provides the general grouping of the sender of the transaction. E.g "Exchange"

Did this answer your question?