HK AML Playbook: FATF, IRA and CRA for Crypto Firms

    StanCompliance
    October 15, 2025
    Hong Kong AML
    FATF compliance
    Institutional Risk Assessment
    Customer Risk Assessment
    Virtual Asset Service Providers
    CDD and record-keeping
    OTC and custody regulation
    HK AML Playbook: FATF, IRA and CRA for Crypto Firms

    Introduction If you run a crypto exchange, OTC desk, or custody provider in Hong Kong, the AML conversation in 2025 boils down to three letters: FATF, IRA, and CRA. Hong Kong is aligning tightly with the Financial Action Task Force (FATF) standards, and the government has consulted on bringing both OTC virtual asset activities and stand-alone custodians into scope with explicit AML/CTF obligations, including customer due diligence (CDD) and record-keeping, plus investor protection requirements like safe, segregated custody, financial soundness, and controls to avoid conflicts of interest. That translates into practical expectations on your Institutional Risk Assessment (IRA) and Customer Risk Assessment (CRA).

    Why FATF matters right now

    • FATF is the inter-governmental standard-setter for AML/CTF, founded in 1989, with Hong Kong participating as Hong Kong, China. See FATF’s site.
    • FATF revised Recommendation 15 in 2019 to require jurisdictions to regulate virtual asset service providers (VASPs) for AML/CTF risks. Hong Kong has moved accordingly: SFC licensing for VA trading platforms is in force, and the Financial Services and the Treasury Bureau (FSTB) has consulted on regulatory regimes for OTC VA activities and virtual asset custodians, both explicitly referencing AML/CTF duties like CDD and record-keeping and investor protection guardrails.
    • Policy-wise, Hong Kong is tracking international norms beyond FATF, including IOSCO’s crypto market recommendations, the FSB’s global framework, and the Basel Committee’s prudential approach to crypto exposures.

    A professional, tech-inspired image shows a person’s outstre...
    A professional, tech-inspired image shows a person’s outstre...

    Institutional Risk Assessment (IRA): what “good” looks like Your IRA (also called business-wide risk assessment) should quantify inherent ML/TF risk across products, customers, geographies, delivery channels, and technologies, then evidence how controls reduce that to residual risk within your board-approved risk appetite.

    IRA domainIllustrative metrics (for demonstration)Typical controls expected in HK
    Customer types% retail vs. corporate; % PEPs; % high-risk sectorsRisk-based CDD, EDD for PEPs, source of funds/wealth, adverse media
    Geography% flows touching sanctions/grey-list jurisdictionsCountry risk scoring, sanctions screening, blocking/wallet blacklists
    Products/VA types% privacy-centric coins; % stablecoin vs. volatileAsset whitelist/blacklist, restricted features (mixers/tumblers)
    Channels% OTC cash-in; % remote onboardingFace-to-face verification rules, stronger KBA, biometric checks
    Custody model% omnibus vs. segregated walletsSegregated wallets, reconciliation, key management, access logs
    Counterparties# VASP counterparties; risk ratingsCounterparty due diligence, periodic reviews, contractual clauses
    Alerts & SARsAlert rate (e.g., 1.2% of transactions), SAR conversion rate (e.g., 8% of alerts)Tuning/testing, QA, MLRO review, audit trail

    What to capture and show:

    • A documented methodology, data sources, scoring scales, and heat maps.
    • Board approval and version control (review at least annually or upon material change).
    • Linkage from risks to controls to testing results and issues tracked to remediation.

    Customer Risk Assessment (CRA): making it bite-sized and defensible CRA is your per-customer risk score used to calibrate onboarding depth, transaction monitoring scenarios, and ongoing review cadence.

    Key elements:

    • Attributes: KYC data, occupation/industry, PEP status, geography, source of wealth/funds, wallet behavior, VA types used, device/IP hygiene.
    • Scoring: Transparent weighting with explainability. Avoid black-box models that your MLRO can’t defend.
    • Triggers: Automatic EDD when thresholds breach (e.g., unusual cash-in at OTC, new high-risk jurisdiction, or switch to privacy coins).
    • Record-keeping: Under Hong Kong’s AMLO (Cap. 615), keep CDD and transaction records for at least five years. Store decisions, not just data, so reviewers see “why,” not only “what.”

    OTC and custody specifics to get right

    • OTC: Expect CDD and record-keeping as baseline; enhanced checks for cash-heavy flows; stronger sanctions/chain analytics; clear scripts to avoid structuring. Maintain surveillance that recognizes location-based risks (e.g., store-front OTC vs. online).
    • Custody: Safe and segregated custody is not optional. Enforce multi-person approvals, key sharding/HSMs, independent reconciliation, and conflict-of-interest policies to separate client and house assets. Financial soundness matters—stress test liquidity and insurance limits.

    A compact 90-day plan

    • Weeks 1–2: Refresh FATF alignment and map to Hong Kong regimes (SFC rules; FSTB consultations for OTC/custody). Inventory gaps in CDD, record-keeping, and investor protection controls. Links: FATF; SFC VA platforms; FSTB consultations.
    • Weeks 3–6: Rebuild IRA with current data; set risk appetite statements; approve at board level. Tune monitoring scenarios to VA-specific typologies.
    • Weeks 7–10: Roll out CRA 2.0 with clear scoring, EDD triggers, and adverse media/sanctions integrations. Validate on a historical sample (e.g., 1,000 accounts).
    • Weeks 11–13: Evidence: testing, QA, training logs, and an internal audit plan. Implement dashboarding and MI for the MLRO. Store everything with five-year retention.

    One last point If it isn’t documented, in the regulator’s eyes it didn’t happen.

    Conclusion Hong Kong’s message is consistent: align with FATF, prove your enterprise-wide IRA is real, and make your CRA proportionate and explainable. For OTC and custody, add safe segregation and conflict controls to the AML core. Do this, and you won’t just pass inspections—you’ll actually catch the risks that matter.