Cryptopay API
  • Welcome
  • Guides
    • Introduction
    • Environments
    • Creating a Test Account
    • API Credentials
    • API Basics
      • Responses
      • Date formats
      • Authentication
        • How it works
        • Signature
        • Creating a signature. Code samples
      • Callbacks
    • API Client Libraries
    • API Reference
    • Cryptocurrency Payments
    • Currencies
      • Supported Currencies
      • Currency Icons
    • Confirmations
    • Tools for accepting payments
    • Prebuilt integrations
      • E-commerce payment plugins
      • Payment and software providers
    • Channels
      • Channel payment
      • Payment statuses
      • Channel payment sequence
      • Create a Channel
      • Visual representation at Cashier
      • Channel hosted page
      • Channel payment callbacks
    • Invoices
      • Invoice statuses
      • Invoice payment sequence
      • How to handle unresolved invoices
        • Underpaid
        • Overpaid
        • Paid late
        • Illicit resource
        • Invoice refunds sequence
      • Create an invoice
      • Visual presentation at Cashier
      • Invoice hosted page
      • Online checkout
        • How-to
      • Payment links
      • Invoice callbacks
    • Payouts
      • Payout statuses
      • Payout sequence
      • Payout fees consideration
        • Network fees
      • Create a Coin Withdrawal
        • Possible errors
        • Withdrawals from fiat accounts
        • Withdrawals from cryptocurrency accounts
        • high_risk_address error message
      • Visual representation at Cashier
      • Minimum transaction amount
      • Coin Withdrawal callbacks
      • Travel Rule Compliance
    • Email Billing
      • Create an email billing
      • Email billing callbacks
    • Testing
      • Channels
      • Invoices
      • Payouts
    • Risks
    • Customers
    • Transactions types and Statuses
Powered by GitBook
On this page
  1. Guides

Risks

PreviousPayoutsNextCustomers

Last updated 6 months ago

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).

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.

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

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

Related documentation:

Invoice statuses
Payment statuses
Customers
596KB
Merchant Guidance v07102020.pdf
pdf