TL;DR: Customer verification standards are being standardised across the EU from 2027, with IDnow saying the fallback pathway, vague trust-service wording and weak anti-deepfake controls could undermine assurance. Onboarding journeys need named assurance levels, explicit trust-service rules and anti-spoofing checks that hold up under audit.
Editorial analysis by NHI Mgmt Group, based on content published by IDnow: “Europe’s AML Rules are Being Rewritten. Here’s What the July 10 Deadline Means for You.”.
By the numbers:
- AMLA will submit its draft Regulatory Technical Standards on July 10, 2026.
- The standards will apply directly across all 27 member states once adopted.
- AMLA’s public hearing in March 2026 drew over 1,600 stakeholders.
Key questions
Q: Why does enhanced due diligence need ongoing monitoring after onboarding?
A: Because risk does not stay fixed after the initial review.
Q: How should organisations strengthen remote identity proofing without increasing fraud or bias risk?
A: Organisations should use identity proofing methods that verify a real person remotely with high assurance, strong spoof resistance, and measurable error rates.
Q: What breaks when customer verification rules allow weaker fallback identity checks?
A: Weaker fallback checks create a trust gap that fraudsters can exploit with synthetic documents, deepfake overlays or manipulated biometric feeds.
Practitioner guidance
- Map every verification journey to a named assurance level Classify each onboarding path against eIDAS 2.0 Low, Substantial or High so teams know which evidence is sufficient and where current methods fall short.
- Remove any implicit reliance on fallback-only verification If a customer journey can pass with remote document scanning alone, treat that as an exception that needs business approval, stricter evidence and explicit anti-spoofing controls.
- Require anti-deepfake and injection detection for remote capture Enforce presentation attack detection, liveness checks and camera-origin validation wherever remote biometric or document capture is part of the proofing chain.
Bottom line: The article’s central warning is that EU customer verification is being standardised, but a weak fallback path and vague trust-service language could undermine the assurance the regulation is meant to create.
Glossary terms: Customer Due Diligence, Qualified Electronic Attestation Of Attributes, Presentation Attack Detection (PAD), Continuous Monitoring
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Assurance harmonisation is the real regulatory shift, not simply a new checklist. The article shows that AMLA is turning customer verification into a cross-border assurance regime where identity proofing, evidence quality and monitoring consistency must all align. That is structurally similar to other programmes where fragmentation creates control drift, because one accepted exception can undermine the integrity of the whole decision chain. Practitioners should treat harmonisation as a governance redesign, not a documentation exercise.
A question worth separating out:
Q: How should organisations govern qualified trust services across EU onboarding flows?
A: Treat named trust services as policy decisions, not informal assumptions. Define which services are acceptable for which customer types, make that decision explicit in workflow logic, and ensure legal, compliance and technical teams use the same acceptance criteria. If the rule is vague, providers will interpret it differently and cross-border consistency will fail.
👉 Read our full editorial: AMLR customer verification standards tighten identity proofing in 2027