Topic starter
30/10/2026 8:52 pm
TL;DR: Fintech KYC checks based only on Credit Reference Agency data can wrongly reject genuine thin-file customers, according to OneID, while UK rules still require reliable and independent identity evidence. Wider matching across banks, mobile, insurance and public-sector data recovers more good applicants without weakening customer due diligence.
Editorial analysis by NHI Mgmt Group, based on content published by OneID: “Fintech KYC: onboard more without weaker checks”.
Key questions
Q: Why do credit-only KYC checks reject genuine thin-file customers?
A: Credit-only checks depend on enough matching records in bureau data to confirm identity.
Q: When should fintechs use a second wash in onboarding?
A: Use a second wash when the first-pass identity check fails because the applicant has limited bureau visibility, not because the person has already been assessed as high risk.
Q: How do organisations keep KYC strict without excluding thin-file customers?
A: Use multiple independent data sources to verify identity, then keep customer due diligence, sanctions screening and ongoing monitoring as separate controls.
Practitioner guidance
- Review false-reject patterns in onboarding Separate genuine thin-file applicants from high-risk failures by analysing where identity checks stall, which sources fail to match, and which customer segments are most affected.
- Add a second-pass evidence layer Re-run failed records against additional independent sources such as bank, mobile, insurance and public-sector data before escalating to manual review.
- Keep due diligence controls separate Preserve sanctions screening, risk assessment, source-of-funds checks and ongoing monitoring as distinct controls rather than treating identity verification as a complete CDD process.
Bottom line: Thin-file customers can fail fintech KYC even when they are genuine because credit bureau data does not always provide enough independent evidence to clear them.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
31/10/2026 9:40 am
Thin-file rejection is a verification design flaw, not a customer quality signal. When a fintech treats credit bureau visibility as the main proof of identity, it confuses financial depth with identity trust. That assumption breaks for younger adults and newcomers who have a valid identity but limited credit history. The practical conclusion is that onboarding governance must distinguish evidence scarcity from risk.
A question worth separating out:
Q: What is the difference between customer identification and customer due diligence in AML compliance?
A: Customer identification establishes who the customer is, usually by confirming core identity details and supporting documents. Customer due diligence goes further by assessing risk, understanding the purpose of the relationship, and applying enhanced checks where needed. Identification answers whether the customer is real, while due diligence answers whether the relationship is acceptable and under what conditions.
👉 Read our full editorial: Thin-file fintech KYC fails when credit data is too narrow