TL;DR: Fraud often appears after onboarding, so static KYC can miss the later account changes that matter, according to IDnow. Identity assurance has to be governed as a live relationship if it is to be re-checked when risk shifts.
Editorial analysis by NHI Mgmt Group, based on content published by IDnow: “The Identity Check is Dead. Long Live the Identity Relationship.”.
By the numbers:
- The European Anti-Money Laundering Authority is required to submit its draft regulatory technical standards on customer due diligence in July 2026.
- Fraudulent payment transactions across the EEA totalled €4.3 billion in 2022, according to the joint ECB/EBA report on payment fraud cited by IDnow.
- By 2024, fraudulent credit transfers had risen 16% year-on-year to €2.2 billion, with card fraud adding another €1.3 billion on top, according to the EBA-ECB’s 2025 payment fraud report cited by IDnow.
Key questions
Q: When should organisations re-check customer identity instead of relying on the original KYC result?
A: They should re-check identity when a customer changes payment details, activity patterns, account limits, or any other signal that changes the risk profile.
Q: What are the signs that static KYC controls are failing?
A: Common signs include repeated identity artefacts across channels, successful logins after suspicious onboarding, and fraud cases that become obvious only when data is compared with other organisations or prior attempts.
Q: Why do onboarding checks fail to catch later eKYC fraud?
A: Because fraud often appears after the initial proofing decision, when attackers exploit account changes, transaction requests or weaker review paths.
Practitioner guidance
- Replace one-time KYC with lifecycle verification Map onboarding, re-verification and step-up events into a single customer identity journey so trust can be reassessed after compromise indicators appear.
- Define event triggers for re-verification Trigger review when the customer changes device, logs in from a new geography, resets credentials or shows signs of SIM swap or email compromise.
- Align fraud and compliance controls Make AML, authentication and customer due diligence operate on the same evidence set so compliance decisions reflect live risk, not stale identity proof.
Bottom line: The core weakness is not bad onboarding checks but the assumption that trust stays valid after the first verification.
Glossary terms: Continuous Identity Assessment, Identity relationships, Event-Driven Re-verification
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
One-time KYC is a conceptual failure in modern fraud governance. The article is right to frame the issue as structural rather than technological. A single verification event cannot govern a relationship that changes over time, especially when device, channel and credential state can all be altered after onboarding. The security control is not failing because it is poorly tuned; it is failing because it was never designed for post-onboarding risk. Practitioner implication: move identity assurance from a checkpoint to a lifecycle control.
A question worth separating out:
Q: How should teams prepare for eIDAS 2.0, AMLR and PSD3 together?
A: Treat them as one operating change, not three isolated obligations. The practical response is to redesign customer identity assurance so it can accept new evidence types, re-check trust after change events, and support strong authentication and due diligence from the same control model.
👉 Read our full editorial: Continuous identity assurance must replace one-time KYC checks