A custodian integrated three months ago begins routing client assets through a newly acquired liquidity partner. Banking rails slow, then freeze. The investigation reveals the liquidity partner was flagged by two major exchanges for wash-trading activity – information available in public enforcement disclosures but never captured in the onboarding questionnaire. The business loses its payment processor, two correspondent banking relationships and four weeks of revenue while it unwinds the arrangement and demonstrates remediation to its own regulator.
Vendor and counterparty due diligence is the process by which a digital-asset business assesses the AML, regulatory and operational risk carried by the entities it contracts with – exchanges, custodians, liquidity providers, wallet infrastructure vendors, payment processors and banking partners. Under the FATF Recommendations, the Travel Rule and the major licensing regimes (MiCA, VARA, FSRA, MAS, SFC), a VASP or CASP is expected to know not only its own customers but the risk profile of every entity through which it touches client funds or transaction data. A failure at a vendor or counterparty creates direct exposure at the licensed entity: enforcement, loss of banking and, in some forums, personal liability for senior management. This guide sets out a repeatable diligence framework, the escalation and periodic-review triggers, and the decision points at which external counsel should verify the stack before contracts are signed.
Who must conduct vendor and counterparty due diligence
Any entity licensed or registered as a VASP, CASP, DPT service provider or equivalent must conduct vendor and counterparty due diligence wherever a third party handles, routes or stores client assets; processes, transmits or stores transaction data subject to the Travel Rule; or provides core technology infrastructure (hot/cold wallet services, node operation, API gateways) that affects the integrity of the compliance program. The obligation applies whether the vendor relationship is direct (your custodian) or indirect (a sub-custodian or omnibus-account provider used by your prime custodian).
In our cross-border practice, operators commonly underestimate the scope. A token issuer using a third-party staking-as-a-service provider must assess that provider if client tokens are transferred into pooled validator wallets under the provider's control. An exchange relying on an OTC desk for liquidity sourcing must verify that desk's AML framework and Travel Rule implementation. A fund administrator holding digital assets in a sub-custody arrangement must trace the chain to the ultimate custodian and confirm that each layer meets the fund's own AML and cybersecurity baseline.
Regulators in the leading hubs – ESMA under MiCA, VARA, FSRA, MAS, the Hong Kong SFC – increasingly expect the licensed entity to map its vendor dependencies in the initial application and to update that map as a material change whenever a critical vendor is added or replaced. A vendor failure is treated as a systems-and-controls failure at the licensed entity, with the same enforcement and remediation consequences.
The four-tier diligence model
The diligence model we implement for clients is a four-tier structure, assigning each vendor to a risk category and applying the corresponding assessment depth. Tier assignment is not static: a vendor moves to a higher tier when transaction volumes, custody balances or regulatory risk increase.
Tier 1 – Critical infrastructure. Custodians holding client assets above a materiality threshold; wallet-infrastructure providers with direct access to private keys or seed phrases; payment processors routing fiat settlement; core node operators. These vendors undergo full entity-level diligence before onboarding, annual full refresh and event-triggered escalation (a data breach, a public enforcement action, a change in ownership or senior management, loss of a banking relationship). The assessment includes verification of the vendor's own licensing status, its AML program documentation, Travel Rule implementation and incident-response protocols, financial-crime insurance coverage and recent audit reports (SOC 2, ISO 27001 or equivalent). In our experience, a full Tier-1 review typically requires four to six weeks from questionnaire to sign-off.
Tier 2 – Regulated counterparties. Exchanges or OTC desks providing liquidity; banking partners; sub-custodians. These entities are themselves regulated, reducing the inherent risk, but the diligence must confirm the counterparty's licence is current, covers the activities under the contract and extends to the jurisdiction(s) where your business and its clients sit. For a liquidity provider, the review includes verification that the provider applies Travel Rule screening to your transactions and that it maintains adequate controls against market manipulation. Tier-2 reviews are conducted before onboarding and refreshed biennially or on a material-change trigger.
Tier 3 – Technology and service vendors. Compliance software (transaction monitoring, wallet screening), KYC utilities, legal and accounting advisors, marketing agencies. These vendors do not handle client assets or transaction messages directly but access sensitive data or influence compliance outputs. Diligence is lighter: verification of the vendor's cybersecurity posture, data-processing agreements, and any relevant certifications (e.g. GDPR compliance for a KYC utility serving EU clients). Tier-3 reviews occur at onboarding and on a three-year cycle.
Tier 4 – Administrative and non-critical. Office services, general IT (non-crypto-specific software), HR platforms. Minimal diligence: confirmation of a valid contract, insurance and standard data-protection terms. Refreshed on contract renewal only.
A common mistake is assigning a vendor to Tier 2 or 3 based solely on the contract label ("technology partner") when the substance of the arrangement is Tier 1 (the vendor controls wallet infrastructure or processes outbound transfers on behalf of the licensed entity). Substance governs the tier assignment, not the marketing term.
The diligence questionnaire and verification process
A robust vendor questionnaire covers six domains: licensing and regulatory standing; AML and sanctions compliance; Travel Rule implementation; cybersecurity and incident response; financial stability and insurance; and any public enforcement or adverse media within the prior 24 months. For Tier-1 vendors, every answer must be verified against primary sources – the vendor does not self-certify.
The verification process begins with a request for the vendor's licence or registration certificate, issued by the relevant regulator, with an expiry date (if applicable). For EU-based vendors transitioning to MiCA, confirm whether the vendor holds a national VASP registration or an interim authorisation and, if the latter, the expected CASP application timeline. For UAE vendors, verify whether the licence is VARA (Dubai mainland) or FSRA (ADGM) and whether the scope covers the specific activities under your contract. In Switzerland, confirm whether the vendor operates under a FINMA licence, a FinTech licence or an SRO affiliation and whether the token activities fall within the scope of that authorisation.
The AML-compliance section requests a copy of the vendor's AML policy, the name and contact details of its Money Laundering Reporting Officer (MLRO), evidence of AML training for relevant staff, and a summary of its transaction-monitoring system and alert-escalation process. For custodians and exchanges, ask for a sample Travel Rule message (IVMS101 format or the vendor's proprietary structure) and confirmation of which Travel Rule solution the vendor uses (if any). If the vendor claims exemption from the Travel Rule (a de-minimis threshold or a particular transaction type), request the legal basis.
The cybersecurity domain covers: SOC 2 Type II or ISO 27001 certification (request the report and verify the auditor's name and the report date); details of the vendor's hot/cold wallet split and multi-signature configuration if applicable; incident-response plan (does the vendor notify you within a specified window if client data or keys are compromised?); and cyber-insurance coverage with limits stated. For custodians, verify whether client assets are held in segregated accounts and whether the vendor maintains a proof-of-reserves attestation.
Adverse-media and enforcement screening is conducted against the vendor entity, its beneficial owners and its senior management (CEO, CFO, MLRO, CTO if relevant). Sources include regulator enforcement databases (ESMA, FINMA, FCA, MAS, SFC, FinCEN, SEC), OFAC and UN sanctions lists, and structured media databases (not general search-engine results, which over-flag). A "hit" does not automatically disqualify the vendor but triggers escalation: external counsel reviews the enforcement action or adverse report, assesses whether it is material to your risk appetite, and advises on enhanced monitoring or contractual protections (a clawback clause, a higher escrow requirement).
For a detailed description of the AML compliance obligations that flow to the licensed entity, see Compliance, AML & Travel Rule for Digital Asset Businesses.
Escalation and the high-risk vendor track
A vendor moves to the high-risk track when any of five triggers fire: a recent enforcement action by a regulator in any major jurisdiction; loss of a banking relationship within the prior 12 months; a cybersecurity incident affecting client data or assets within the prior 24 months; a change in beneficial ownership or control; or a material gap in the diligence questionnaire (the vendor cannot provide a current licence, refuses to disclose its MLRO, or declines to share AML policy documentation).
High-risk vendors may still be onboarded, but only with enhanced controls and executive-level sign-off. Enhanced controls include: a contractual right to audit the vendor's AML and cybersecurity systems; a requirement that the vendor notify you within 24 hours of any regulatory inquiry, enforcement action or data breach; reduced transaction or custody limits (you cap the volume or value routed through that vendor until the risk profile improves); and quarterly (not annual) diligence refresh.
In our practice, we see operators attempt to onboard a high-risk vendor under standard terms because the commercial team has already negotiated the deal. The compliance function then inherits an undocumented risk and, when the regulator asks why the arrangement was approved, no contemporaneous risk assessment exists. The correct sequence: diligence runs before the commercial contract is signed, the high-risk designation is documented in writing with the rationale and the mitigants, and the board or senior management formally approves the onboarding. If the vendor refuses the enhanced terms, the contract does not proceed.
Periodic review and the refresh cycle
Diligence is not a one-time gate. Tier-1 vendors are reviewed annually; Tier-2 vendors biennially; Tier-3 on a three-year cycle. The periodic review is a lighter version of the initial diligence, covering: any change in licensing status or regulatory standing; any enforcement actions or adverse media since the last review; any cybersecurity incidents; and updated financial statements or insurance certificates. If the vendor's risk profile has materially improved (for example, it obtained a higher-tier licence or passed a rigorous third-party audit), the vendor may be moved to a lower-risk tier and the refresh cycle extended. If the risk profile has deteriorated, the vendor escalates to high-risk and the enhanced controls apply.
Event-triggered escalation requires an immediate out-of-cycle review. Triggering events include: public disclosure of a regulatory investigation or enforcement action; a data breach or cybersecurity incident disclosed by the vendor or reported in credible media; loss of a critical licence or banking relationship; a merger, acquisition or change in beneficial ownership; or any circumstance in which the vendor ceases to meet the baseline requirements that justified its initial approval. The out-of-cycle review must be completed within two weeks of the trigger event becoming known, and the business must decide within a further two weeks whether to continue, suspend or terminate the vendor relationship.
For multi-jurisdiction crypto groups managing regulatory change across several licensing regimes, see Regulatory Change Management for Multi-Jurisdiction Crypto Groups.
Documenting the diligence decision
Every diligence assessment – whether at onboarding, periodic refresh or event-triggered escalation – must produce a written record: the completed questionnaire, the verification evidence (licence certificates, audit reports, insurance declarations), the adverse-media and enforcement search results, a risk-rating conclusion (Tier 1–4, standard or high-risk), the rationale for that rating, any enhanced controls or contractual protections applied, and the name and signature of the approving officer (typically the MLRO or, for Tier-1 and high-risk vendors, a member of senior management or the board).
The documentation standard matters because regulators audit vendor files during on-site inspections. A common deficiency cited in post-inspection findings is "inadequate vendor due diligence documentation" – the business conducted some assessment but cannot demonstrate what was verified, by whom, on what date, or why a particular vendor was approved despite a known risk factor. The regulator's expectation is that an independent reviewer (the regulator's examiner or an external auditor) can open the vendor file and reconstruct the diligence decision without needing to interview the compliance officer who made it.
In our experience, the documentation failure often stems from using informal communication (email threads, Slack messages) as the record rather than a structured diligence template. The template should be a single document or a folder in the compliance management system, indexed by vendor name, with each section corresponding to a diligence domain and a final approval block. Email correspondence with the vendor is attached as supporting evidence but does not replace the structured template.
For operators working across Abu Dhabi's regulatory perimeter, the specific Travel Rule and AML expectations under the FSRA regime are analyzed in detail at AML and Travel Rule Regime in Abu Dhabi Global Market (ADGM).
The cross-border vendor stack and jurisdictional layering
A digital-asset business typically operates across multiple jurisdictions: the entity is licensed in one hub, clients sit in a second jurisdiction, banking is provided by a third, and the custodian or liquidity provider is licensed in a fourth. Each of those vendors and counterparties brings its own regulatory perimeter and AML baseline into the relationship. The diligence framework must address the layering risk – that a vendor's home-jurisdiction regime does not meet the standard required by your own regulator.
For example, a CASP authorised under MiCA in Lithuania contracts with a custodian licensed in Switzerland. The Swiss custodian uses a sub-custodian in Singapore. If the Singapore sub-custodian suffers a breach or an AML failure, the Lithuanian CASP is exposed under MiCA's systems-and-controls requirements even though the Singapore entity is not in its direct contractual chain. The diligence framework must trace the custody chain to the ultimate holder of client assets and confirm that each layer applies AML, cybersecurity and Travel Rule controls equivalent to those the CASP would apply if it held the assets directly. Where a vendor operates in a jurisdiction with a lower regulatory baseline, the contract must impose enhanced obligations by agreement (a "regulatory uplift" clause requiring the vendor to meet the higher standard).
The same principle applies to liquidity providers and exchanges. If an exchange licensed in the UAE provides liquidity to a UK-registered VASP, the VASP must verify that the UAE exchange applies Travel Rule screening to transactions involving UK-connected clients, even if the Travel Rule threshold in the UAE differs from the UK threshold. If the exchange does not apply the UK standard, the VASP must either decline the relationship or implement a compensating control (pre-transaction screening on its own side).
The cross-border interaction between licensing, banking and tax structures means vendor diligence cannot be separated from the broader compliance stack. Operators we advise routinely discover that a vendor approved by one jurisdiction's regulator is unacceptable to the banking partner in a second jurisdiction, forcing a mid-stream vendor change and a re-application of the diligence process. To avoid that outcome, map the vendor dependencies across all three layers – licensing, banking, compliance – before you commit.
When to engage external counsel on vendor diligence
In-house compliance teams manage routine diligence, but five scenarios require external legal input before a vendor relationship is finalized. First, any Tier-1 vendor onboarding where the vendor operates under a regime unfamiliar to your compliance officer (for example, a Kazakhstan AIFC-licensed custodian serving a MiCA-authorised CASP). Counsel verifies that the vendor's licence scope covers the contemplated activities and that its home-jurisdiction AML baseline is recognized as equivalent under your own regime.
Second, any high-risk vendor scenario where the vendor has a recent enforcement action or adverse-media hit. Counsel reviews the underlying enforcement decision or media report, assesses whether the issue is cured, and advises on whether the enhanced controls proposed are sufficient or whether the vendor should be declined.
Third, when the vendor relationship involves sub-custody, omnibus accounts or any arrangement where client assets commingle with the vendor's proprietary assets or with assets of the vendor's other clients. Counsel reviews the custody agreement to confirm that client assets are legally segregated, that the licensed entity retains a first-priority claim in the event of the vendor's insolvency, and that the governing law and dispute-resolution forum are acceptable.
Fourth, when the contract includes a regulatory-uplift clause or Travel Rule pass-through provisions. These clauses impose obligations on the vendor that may exceed its home-jurisdiction baseline, and they must be drafted to survive a conflict-of-laws challenge if the vendor later seeks to disclaim them.
Fifth, at any point where the regulator flags a vendor relationship during a supervision meeting, an application review or an on-site inspection. The regulator's concern may not be immediately clear from the compliance file, and counsel bridges the gap: what does the regulator expect to see, what documentation or contractual amendment is needed, and how quickly must the business act to avoid an adverse finding?
For a scoped assessment of your vendor stack and the diligence gaps, contact OBOLUS at info@oboluslaw.com.
A common assumption: diligence questionnaires from large vendors are always sufficient
A frequent objection raised by operators is that major custodians, exchanges and payment processors provide standardized diligence questionnaires as part of their onboarding, and that those questionnaires should be accepted without additional verification. The assumption is that a large, well-known vendor has already been vetted by dozens of other licensed entities and that replicating that work is redundant.
The assumption is flawed in three respects. First, the vendor's standard questionnaire is designed to satisfy the vendor's own compliance requirements (to know its customer, the licensed entity), not to allow the licensed entity to assess the vendor. The questionnaire typically omits the domains a regulator expects the licensed entity to verify – the vendor's own licensing status, its AML policy, its Travel Rule implementation, its sub-custody or omnibus-account structure. If those items are missing, the business must supplement the questionnaire with targeted questions.
Second, a vendor's reputation and market position do not insulate the licensed entity from regulatory liability if that vendor suffers a failure. Regulators in the leading hubs have explicitly stated in supervisory guidance that reliance on a "big name" vendor is not a defense to a systems-and-controls finding. The licensed entity must conduct its own verification, regardless of the vendor's profile.
Third, the fact that a vendor has been onboarded by multiple counterparties does not mean those counterparties conducted robust diligence. In the aftermath of the FTX collapse, regulators examining institutional exposure found that numerous funds, exchanges and banks had onboarded FTX based largely on its market valuation and public profile, with minimal verification of its custody, AML and financial-stability controls. The licensed entity that assumes "everyone else has checked" is the entity that inherits the undiscovered risk.
The correct approach: accept the vendor's standard questionnaire as a starting document, then append the domains that are missing, verify the answers against primary sources, and document the verification in the vendor file.
FAQ
What does this regime require from a VASP?
A VASP or CASP must conduct and document risk-based due diligence on every entity that handles, routes or stores client assets or transaction data. The diligence covers licensing status, AML and sanctions compliance, Travel Rule implementation, cybersecurity posture, financial stability and any recent enforcement or adverse media. The depth of the assessment depends on the vendor's risk tier. Tier-1 vendors (custodians, core infrastructure) undergo full entity-level diligence before onboarding and annual refresh; lower-tier vendors are reviewed on a longer cycle. The regime applies under MiCA, VARA, FSRA, MAS, the Hong Kong SFC regime and equivalent frameworks in other leading hubs.
Who must act as MLRO for a crypto firm?
The Money Laundering Reporting Officer (MLRO) is the individual within the licensed entity responsible for overseeing the AML program, reviewing transaction-monitoring alerts, filing suspicious-activity reports and serving as the primary contact for the regulator on AML matters. The MLRO must be a senior employee with direct access to the board or senior management and sufficient authority to halt a transaction or freeze an account when a money-laundering risk is identified. Under MiCA, VARA and most other regimes, the MLRO cannot be an outsourced function; the role must be filled by an employee of the licensed entity. The regulator typically requires the MLRO to hold relevant qualifications or demonstrate equivalent experience.
How do regulators audit crypto AML programs?
Regulators audit AML programs through a combination of desk-based reviews (examination of policies, procedures and transaction-monitoring reports submitted as part of the ongoing supervision cycle) and on-site inspections (interviews with the MLRO and compliance staff, testing of the transaction-monitoring system, and review of a sample of customer and vendor files). During an on-site inspection, the regulator will open vendor files at random and verify that the diligence documentation is complete, that the risk rating is justified, and that periodic reviews have been conducted on schedule. A common deficiency finding is inadequate vendor due diligence – the business conducted some assessment but cannot demonstrate what was verified or why a particular vendor was approved.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit. We structure licensing, banking and tax as one mandate rather than three disconnected workstreams. To discuss your vendor diligence framework and the regulatory gaps in your current process, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specializing in AML program design, Travel Rule implementation and vendor risk frameworks for licensed VASPs and CASPs across MiCA, VARA and MAS regimes.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.