Münzen API
  • Home
  • Getting Started
  • API Overview
    • API Reference
    • API Requests
    • API Authentication
    • Environments
    • Errors
    • Callbacks (Webhooks)
    • Currencies, Confirmations, and Limits
    • How to accept crypto payments
    • Proof of Funds
    • AML & Compliance Checks
  • Testing
    • How to check integration
  • Invoices
    • What is Invoices
    • Create an Invoice
    • Invoice Statuses
    • Invoice Callbacks
  • Channels
    • What is Channels
    • Create a Channel
    • Channel Payment Statuses
    • Channel Callbacks
  • Payment Widget
    • What is Payment Widget
    • Integration Guide for Payment Widget
      • Params for Channel Widget
  • Payouts
    • What is Payouts
    • Create a Payout
    • Payout Statuses
    • Payout Callbacks
  • Useful Information
    • Testnet Faucets
Powered by GitBook
On this page
  1. API Overview

AML & Compliance Checks

  1. When receiving a deposit from a wallet identified as "bad" by our AML service, the funds will be "frozen," and the invoice or payment through the channel will be put in the on_hold status with the reason being a high-risk score (high_risk_score). A webhook with the event deposit_on_hold will be sent.

  2. Munzen will conduct a manual review of these deposits and their corresponding source of funds. As a result, the deposits will be kept in a hold status for a reasonable period necessary for the manual review process. During this period, Munzen may request necessary information, data, and/or documents to facilitate the manual review. In all circumstances, Munzen will conduct its activities in strict accordance with the applicable laws and regulations.

  3. If the source of funds from a "bad" wallet is confirmed to be "horrible", the transaction/wallet will be transferred by Munzen to the rejected status due to a high-risk score.

PreviousProof of FundsNextHow to check integration

Last updated 1 year ago