Skip to content
Free guide: How to use AI in compliance
VASP KYC compliance guide 2026, a stylized crypto compliance icon for virtual asset service providers under MiCA and FATF regulations

VASP KYC compliance under MiCA: how to pass the audit without a central store of customer PII, and the sharded architecture that does it.

Table of contents

Key highlights

  • MiCA's transitional period for pre-existing CASPs ended on July 1, 2026 at the latest, earlier where Member States shortened it; since then, serving EU clients without authorisation is a breach of EU law.
  • The procurement choice that decides whether a VASP stays compliant at scale is no longer feature parity, it's whether the architecture survives the next IDmerit-style exposure.
  • Zyphe supports the customer due diligence and record-keeping obligations of national AML law while sharding customer documents across thousands of decentralised nodes with the end user holding the encryption key, so no honeypot exists to breach.
  • A threshold-encrypted audit trail lets the MiCA NCA confirm the check ran, the policy applied, and the timestamps without seeing the underlying document, and if the NCA asks for the document, the operator opens it with the derivative access key the user authorised at onboarding.

VASP KYC compliance under MiCA means verifying customer identity, running AML and CFT procedures, monitoring transactions, and keeping auditable records that an NCA can inspect. In 2026 it is an authorisation question more than a definitions one: MiCA's transitional period for pre-existing CASPs ended on July 1, 2026 at the latest, and the architecture you choose decides whether you pass the audit without becoming the next breach headline.

VASP KYC compliance in 2026 is an authorisation question, not a definitions question. MiCA's transitional period for pre-existing CASPs ended on July 1, 2026 at the latest; the Netherlands ended its transition in mid-2025 and Germany at the end of 2025. Since then, any entity providing crypto-asset services to EU clients without authorisation is in breach of EU law. The procurement choice that decides whether a VASP stays compliant at scale is no longer about feature parity with centralised vendors. It's about whether the architecture survives the next IDmerit-style exposure. This piece names the architecture, the cost question, and the timeline.

What does MiCA actually require of VASPs in 2026?

MiCA defines a Crypto-Asset Service Provider (CASP) as any legal person providing crypto-asset services in the EU on a professional basis. MiCA governs authorisation and conduct: its Articles 68 to 73 cover governance, information to competent authorities, safekeeping of clients' crypto-assets and funds (Article 70), complaints, conflicts of interest and outsourcing. The KYC obligations come from anti-money laundering law: the national laws transposing the AML Directive (EU) 2015/849 today, and the AML Regulation (EU) 2024/1624 from 10 July 2027. Together they set five core requirements:

  1. Verify customer identity before onboarding using government-issued documents.
  2. Establish documented AML and CFT procedures that satisfy national and EU frameworks.
  3. Perform ongoing transaction monitoring across the customer relationship.
  4. Apply risk-based due diligence with documented EDD triggers.
  5. Maintain auditable records of all verification activities for the regulator-mandated retention period.

On top of that, the Transfer of Funds Regulation (TFR, 2023/1113) layered a zero-threshold rule: every crypto transfer between CASPs requires originator and beneficiary identification, with no value cut-off. FATF Recommendation 16 (revised June 2025) extends the Travel Rule's stated objectives to fraud and proliferation financing.

For the broader regulatory direction, see our crypto KYC compliance breakdown and MiCA KYC requirements in 2026.

What's at stake after the July 1, 2026 deadline?

Three things, layered.

  1. Operational shutdown for unauthorised VASPs. After July 1, 2026, providing crypto-asset services to EU clients without MiCA authorisation is a breach of EU law. Operators face cease-and-desist orders, asset freezes, and licence-revocation cascades across other jurisdictions.
  2. Fines sized to turnover. MiCA Article 111 requires Member States to set the maximum fine for a CASP's breaches at no less than EUR 5 million or 5% of total annual turnover for a legal person, and no less than EUR 700,000 for a natural person; national law can go higher. AML and KYC failures are fined separately, under national anti-money laundering law.
  3. Banking-partner termination. Fiat on/off-ramps require KYC infrastructure that survives a banking-partner audit, and a breach at a CASP's KYC vendor can put those rails at risk before the regulator gets to the operator.

The same enforcement pattern is documented in what regulators actually fine on KYC and AML.

The compounding consequence: VASPs operating without authorisation don't just face fines. They face a cascading exit from EU operations as banking and counterparty relationships unwind.

For the broader enforcement picture, see compliance enforcement 2026: fintech takeaways.

How does Zyphe help a VASP satisfy MiCA without a central PII store?

Three architectural primitives that support the KYC obligations without recreating the breach surface the Sumsub and IDmerit incidents demonstrated.

  1. Off-chain verification with sharded user-controlled storage. The verification (NFC chip read, biometric liveness, sanctions, PEP, address, source of funds) runs through Zyphe's identity layer. The customer's documents are then sharded across a decentralised node network with the end user holding the encryption key. The VASP keeps the audit hash; nobody, including Zyphe, can reconstruct the underlying record without the customer's explicit cryptographic consent.
  2. Threshold-encrypted audit trail. Every verification event, every policy version, every decision is logged in a threshold-encrypted audit channel the operator can produce to its supervisor. The MiCA NCA can verify the check ran, the policy applied and the timestamps from the trail alone, and when it asks for the document, the operator opens it with the derivative access key the user authorised at onboarding.
  3. Travel Rule data quality at the source. The cleanly-structured verified counterparty data flows into the operator's Travel Rule integration with no transitivity gap. The receiving VASP gets a high-quality payload to screen against rather than a name string.

This is the model we unpack in our decentralised KYC explainer, and the math behind why sharded storage beats a central honeypot is in is KYC safe after the IDmerit breach.

The compliance outcome: the architecture supports the customer verification, documented AML procedure, ongoing monitoring and auditable records obligations that national AML law (and the AML Regulation from 10 July 2027) places on a CASP. MiCA Article 70 itself covers the safekeeping of clients' crypto-assets and funds, not identity verification. The breach surface that's defining 2026 procurement (centralised vendor honeypots) is structurally absent.

For the architectural detail, see Decentralized KYC and Decentralized PII Storage.

How does verification cost compare for VASPs?

Cost per verification depends on policy depth, jurisdiction mix and integration complexity, and centralised KYC vendors serving VASPs generally price higher for equivalent depth.

The cost reduction compounds with verification volume. A VASP onboarding 10,000 customers a month sees the differential most clearly on the second product launch (where reusable verification cuts cost to a fraction of the first-time rate).

For the operator-side detail, see our crypto compliance tools evaluation guide.

How does the FATF Travel Rule integrate with the Zyphe VASP architecture?

FATF Recommendation 16 (revised June 2025) requires VASPs to share originator and beneficiary identifying information on cross-VASP transfers, with an optional de minimis threshold of up to USD or EUR 1,000; in the EU the TFR applies it to every transfer between CASPs, with no threshold. The Zyphe layer produces the verified counterparty data the Travel Rule message references; the operator's Travel Rule integration handles the message routing.

For a practical walkthrough of the message flow, see our FATF Travel Rule compliance guide for VASPs.

Three operational properties worth flagging:

  1. Counterparty data quality is deterministic. Verified attributes (name, jurisdiction, sanctions clearance) are signed by the issuer and verifiable by the receiving VASP without contacting the issuer. This eliminates the "did the originator data get verified or just collected?" ambiguity that defines most Travel Rule integrations.
  2. Counterparty discovery uses the network's attestation registry. When the receiving VASP is on the Zyphe network, attestation lookup is sub-second; when the receiving VASP uses a different infrastructure, the standard Travel Rule message format applies.
  3. Audit logs at both ends are cryptographically linked. The regulator can inspect the full counterparty data flow without exposing the underlying customer document at either end.

By July 2026, 83% of surveyed jurisdictions had passed Travel Rule legislation, up from 73% a year earlier, according to the FATF's seventh targeted update. The TFR's zero-threshold rule applies to every cross-CASP transfer in the EU; the Zyphe layer is what makes the operator's Travel Rule integration economical at the volume that requires.

For the broader VASP regulatory framework, see our crypto KYC compliance breakdown.

How long does MiCA authorisation actually take?

Two timelines worth tracking.

For pre-existing CASPs operating under national regimes. The transitional window opened December 30, 2024 and closed on July 1, 2026 at the latest; Member States could shorten it, and the Netherlands ended it in mid-2025 and Germany at the end of 2025. A pre-existing CASP that has not been authorised can no longer rely on it.

For new CASPs applying after the transition. Direct MiCA authorisation, no transitional shortcut. Application timelines vary significantly by NCA and the completeness of the operator's compliance documentation.

The architectural choice matters here too: the application must describe the applicant's policies and procedures for managing money laundering and terrorist financing risks and its ICT security arrangements (MiCA Article 62(2)(i) and (j)), so the KYC architecture, and any breach history at the vendor behind it, is part of what the national competent authority (NCA) reads.

For the broader timeline detail, see our crypto KYC compliance breakdown.

What should a VASP do now?

Five concrete moves, in priority order.

  1. Confirm your MiCA authorisation status. If you serve EU clients and you're not authorised yet, the transitional period no longer covers you, so authorisation is the first project.
  2. Audit your KYC vendor's data exposure. If your vendor stores reconstructable PII for the regulated retention period, the breach surface is your liability. Sumsub's 18-month-undetected breach and the 1-billion-record IDmerit exposure Cybernews reported are the current procurement context.
  3. Stress-test your audit trail case by case. Be ready to show a supervisor how a sample of escalations and dismissals was decided.
  4. Confirm your Travel Rule data quality. Sample inbound and outbound transfers; measure counterparty data completeness. Poor data quality compounds into screening blind spots downstream.
  5. Plan banking-partner conversations. A vendor migration changes the KYC set-up your banking partners have reviewed, so treat it as a banking-relationship event, not just a procurement one.

We explain why vendor data exposure sits with you in why your KYC vendor is your biggest breach risk.

If you also onboard businesses, our KYB software guide for 2026 covers verifying entities without manual overhead.

For the detailed operator playbook, see building a robust AML strategy for crypto exchanges.

What should VASPs take away on MiCA KYC?

VASP KYC compliance under MiCA was a deadline-driven question with an architectural answer. The transitional period ended on July 1, 2026, so a CASP serving EU customers now needs its authorisation, and the procurement choice that decides whether it stays compliant at scale isn't feature parity. It's whether the architecture survives the next IDmerit and a supervisor's case-by-case review of its decisions simultaneously. The cost-per-verification differential matters, but the breach-exposure differential matters more.

If the timeline conversation belongs in your roadmap, book a 30-minute walkthrough and we'll show the verification flow plus the cost benchmark your procurement team will read first.

When is the decentralised VASP model not the right call?

If your team is still working towards authorisation, a vendor migration is a banking-relationship event, not just a procurement one, so switching architecture mid-application needs to be planned around your authorisation timeline rather than bolted on at the last minute.

The cost differential compounds with volume and shows most clearly on a second product launch with reusable verification, so a low-volume operator running a single product should weigh the breach-exposure benefit more than the headline cost gap.

  1. MiCA detail, MiCA KYC requirements in 2026
  2. Compliance, Crypto KYC compliance in 2026
  3. Architecture, Is KYC safe in 2026? After the IDmerit breach
Edoardo Mustarelli Edoardo Mustarelli (Sales Development Representative) Edoardo Mustarelli, fintech/Web3 strategist at Zyphe, driving sales growth and partnerships with global expertise across technology, finance, and strategy.

Frequently Asked Questions

VASP KYC compliance is the obligation, under FATF Recommendations 15 and 16 and the national AML laws that implement them (in the EU, the laws transposing the AML Directive, the AML Regulation from 10 July 2027 and the Transfer of Funds Regulation), to verify customer identity at onboarding, run ongoing CDD, screen for sanctions and PEP, share originator and beneficiary data on cross-VASP transfers (in the EU, every transfer between CASPs, with no threshold), and maintain auditable records. It applies to crypto exchanges, custodians, brokers, wallet providers offering custody, and CASPs in the EU.

It ended on July 1, 2026 at the latest. The transitional window opened December 30, 2024, and Member States could shorten it; the Netherlands ended it in mid-2025 and Germany at the end of 2025. Since then, any entity providing crypto-asset services to EU clients without MiCA authorisation is in breach of EU law.

The comparison is not really a unit-price one. Centralised vendors price for a retained identity store they have to secure, audit and insure, and that cost reaches the buyer whether or not it appears on the invoice. An architecture that does not retain reconstructable data removes that layer, and the gap compounds with volume and shows most clearly on a second product launch with reusable verification. Model it against your own jurisdiction mix and policy depth.

Off-chain verification produces a signed attestation; documents are sharded across thousands of storage nodes into the user's own vault; the operator keeps the audit hash and, with the user's consent at onboarding, a derivative access key, so the MiCA NCA can verify the check ran without seeing the document and the operator can open the document if the NCA asks. The architecture supports the verification, documented AML procedure, ongoing monitoring and auditable records obligations, which come from national AML law (and the AML Regulation (EU) 2024/1624 from 10 July 2027) rather than MiCA Article 70, which covers the safekeeping of clients' crypto-assets and funds.

The Zyphe KYC layer produces the verified counterparty data the Travel Rule message references; the operator's Travel Rule integration handles the message routing. Verified attributes are signed by the issuer and verifiable by the receiving VASP without contacting the issuer. Audit logs at both ends are cryptographically linked. The TFR's zero-threshold rule applies in the EU.

If the vendor keeps reconstructable PII in a central store, a breach can expose it: Cybernews reported about one billion records in an unprotected database it linked to IDmerit (which disputes the attribution), and an intrusion at Sumsub through a third-party support platform exposed mostly names and contact details. The Zyphe architecture eliminates this: each verification record is split across 100 shards with a 29-of-100 reconstruction threshold, AES-GCM-256 encrypted with user-held keys. A breached node yields encrypted noise rather than recoverable records.

Most operators hit production in two weeks. The fastest path is the no-code verification link with a preset MiCA policy: about 15 minutes from dashboard signup to first verification. Full API + webhook integrations with custom branding typically take one to two engineering days. Compliance-as-a-service is available for thin teams.

Under MiCA Article 111, Member States must set the maximum fine for a CASP's breaches at no less than EUR 5 million or 5% of total annual turnover for a legal person and EUR 700,000 for a natural person, or twice the profit gained where that can be determined and is higher; national law can go further. AML and KYC failures are fined under national anti-money laundering law rather than MiCA. Since July 1, 2026, unauthorised CASPs face cease-and-desist orders and asset freezes.

AML compliance without the PII liability

Screening, monitoring and reporting built on a privacy-first identity layer.

See Zyphe AML