> For the complete documentation index, see [llms.txt](https://developers.cryptopay.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.cryptopay.me/guides/risks.md).

# Risks

Cryptopay uses screening tools that monitor illicit cryptocurrency addresses and tag addresses that interact with them. These tools inform us with a high degree of certainty if cryptocurrency transactions we process have been connected to (or originated from) illicit activities online (terrorist funding, ML, dark marketplace activities, trafficking, etc).

{% file src="/files/-MJ1Dlu-KthXvu025Sb3" %}

We take the data, received from these tools, very seriously, as it helps us to comply with all compliance procedures in accordance with AML standards in the context of payment processing. The purpose of monitoring these transactions/addresses is to avoid processing funds, associated with illicit addresses, as we do not wish to be involved with these funds, and neither do merchants.

A callback `level` attribute that we send to a merchant's server regarding all transaction-related events, dictates how close the transaction received is linked to the illicit addresses (e.g. was it sent directly from a 'bad' address, or there are a few hops in between).

We expect you to contact us at <risk@cryptopay.me> for further instructions in case you get a High-Risk payment.&#x20;

| Value    | Description                                                                                                                                             |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `low`    | No red flags                                                                                                                                            |
| `medium` | No red flags but we recommend to look closely at a user whom the transaction relates to and inform your Fraud Prevention / Transaction Monitoring teams |
| `high`   | Red flags. We highly recommend to restrict the user's account and immediately inform your Fraud Prevention / Transaction Monitoring teams               |

{% tabs %}
{% tab title="Invoice callback" %}

```javascript
{
  ...
    "transactions": [
      {
        "txid": "502e6de0c3b1d129974c55e6cd127fd548e4501ff8e8d9330ea9a30a83dbd16e",
        "risk": {
          "score": 0.0,
          "level": "low",
          "resource_name": "Bitstamp",
          "resource_category": "Exchange"
         }
      }
    ],
  ...
}
```

{% endtab %}

{% tab title="ChannelPayment callback" %}

```javascript
{
  ...
    "risk": {
      "score": 0.0,
      "level": "low",
      "resource_name": "Bitstamp",
      "resource_category": "Exchange"
    },
  ...
}
```

{% endtab %}

{% tab title="CoinWithdrawal callback" %}

```javascript
{
  ...
    "risk": {
      "score": 0.0,
      "level": "low",
      "resource_name": "Bitstamp",
      "resource_category": "Exchange"
    },
  ...
}
```

{% endtab %}
{% endtabs %}

Related documentation:

{% content-ref url="/pages/-MIPdx4YsVtBWHkwfmsE" %}
[Invoice statuses](/guides/invoices/invoice-statuses.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MIPVEcBZ761kwhgQkIx" %}
[Payment statuses](/guides/channels/payment-statuses.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M6-AHzQXmaYwwP7YpOh" %}
[Customers](/guides/customers.md)
{% endcontent-ref %}