Topic starter
14/07/2026 4:26 pm
TL;DR: AI-enhanced fraud is forcing identity teams toward continuous proof of personhood at the point of action, Smile Identity says. Identity checks now need to refresh when risk changes, not stop at onboarding.
Editorial analysis by NHI Mgmt Group, based on content published by Smile Identity: “Protecting Human Identity in the Age of AI”.
Key questions
Q: Why do AI-driven fraud attacks bypass traditional KYC controls?
A: Traditional KYC controls are designed to verify a person once, not to prove that the same person is still present later.
Q: What are the warning signs that identity assurance is too static?
A: Look for repeated account abuse after successful enrolment, fraud concentrated at high-value actions, and controls that only trigger at signup.
Q: How should fraud teams handle AI-generated identity evidence in onboarding flows?
A: Fraud teams should treat AI-generated evidence as potentially convincing but not independently trustworthy.
Practitioner guidance
- Redesign identity assurance for transaction time Move beyond onboarding-only KYC and require fresh assurance at login, payment, loan, or account-change events.
- Layer biometrics with anti-spoofing signals Pair liveness detection and facial comparison with device intelligence so deepfakes and synthetic identities face multiple checks.
- Define step-up rules for high-value actions Set policy for when identity confidence must rise before a transaction can complete, and make the thresholds reviewable.
Bottom line: AI-enhanced fraud is forcing identity teams to move from once-and-done verification to continuous assurance at the point of action.
Glossary terms: Proof of Personhood, Continuous identity validation, Liveness Detection, Synthetic Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
14/07/2026 4:33 pm
AI fraud turns identity assurance into a runtime governance problem: The old assumption was that a verified identity remains trustworthy until the next formal review. That assumption fails when fraud can be generated, adapted, and replayed continuously across onboarding and transaction flows. The implication is that identity programmes must govern assurance as an ongoing state, not a one-time decision.
A question worth separating out:
Q: When should organisations use stronger identity checks for customer servicing and payment activity?
A: Organisations should raise verification requirements when the action changes account risk, exposes sensitive data, or initiates value movement. Password resets, document access, payment orders, and profile changes are common trigger points. The right control is step-up authentication tied to the transaction, so legitimate users move quickly while higher-risk actions receive more scrutiny.
👉 Read our full editorial: AI-driven fraud is redefining identity verification in emerging markets