Non-Document Verification in the Netherlands: Fast KYC Without Document Uploads
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
Non-document identity verification in the Netherlands uses a citizen’s nine-digit BSN, biometric liveness selfie, and real-time matching against the government’s BRP population register to verify identity without requiring passport or ID uploads. The approach is presented as a faster alternative to traditional document-based KYC, avoiding issues such as poor image quality, expired documents, manual review delays, and document fraud while typically delivering decisions in under 30 seconds. The BRP, managed by the RvIG and covering roughly 96% of residents, alongside the country’s DigiD digital identity infrastructure, provides the data foundation for this model. It is positioned as supporting Wwft anti-money-laundering and customer-due-diligence obligations enforced by Dutch regulators DNB and AFM, while improving onboarding conversion, fraud resistance, and scalability. Didit promotes its platform as an API-based provider of this service, offering liveness detection, AML and sanctions screening, ongoing monitoring, global document-verification fallback, and a stated per-verification price of $0.30, with the first 500 monthly checks free.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Real-time | 1 | 13,979 | 3,441 | 296 | +113% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.