What are Database Checks and how do they differ from document verification?
Database Checks verify identity by cross-referencing submitted attributes against authoritative third-party databases including government registries, credit bureaus, and telco records. No document photograph is required. Document verification asks users to photograph a physical ID, then applies OCR and authenticity checks. Database Checks are faster, have higher completion rates, and eliminate the attack surface created by document image upload.
Which countries and sources does passive database verification cover?
Shufti’s passive database check network covers 237 active sources across 27+ countries. Source types include government population registries, national credit bureaus, telco subscriber records, commercial aggregators, utility databases, and consumer data sources. Key markets include Australia (95%), Costa Rica (99%), India (95%), Chile (98%), Spain (95%), Germany (75%), and 20+ additional countries across Europe, LATAM, APAC, and Africa.
What is the difference between passive and active database verification?
Passive verification checks submitted identity attributes against structured databases in the background with no user action required beyond entering their details. Active verification accepts a digital credential issued by a government authority and validates it against the issuing source in real time. Where the authority supports biometric matching, active verification confirms the correct person is presenting the credential.
Are Database Checks accepted for KYC compliance?
Database-level identity verification is accepted under KYC frameworks in multiple jurisdictions including the UK (FCA), EU (AMLD), Australia (AML/CTF Act), Singapore (MAS), and UAE (CBUAE). Active eIDV at eIDAS Level of Assurance High meets EU Substantial and High assurance CDD requirements. Acceptance varies by jurisdiction and use case.
What happens if a user is not covered by passive database sources?
The verification flow automatically routes to the next available layer: active eIDV if the country has a supported digital identity scheme, or standard document verification as a fallback. No user is lost to missing coverage. Fallback routing rules are configurable via the Journey Builder without API changes.
What is 1x1 and 2x2 verification logic?
1x1 logic verifies identity against a single data source, suitable for low-risk flows where speed is the priority. 2x2 logic cross-references two independent data sources and requires both to confirm the same attribute, suitable for regulated financial services onboarding where corroborated evidence is required.
How quickly does a database check return a result?
Passive database checks against structured government and credit bureau APIs typically complete in under two seconds. Active eIDV response time depends on the issuing authority’s infrastructure. Shufti’s end-to-end verification time is under 15 seconds across all supported markets.
How long does API integration take?
Standard REST API integration takes 2–5 days. SDK integration (iOS, Android, Web) takes 1–3 days. Sandbox access is available within 24 hours without a commercial agreement. All three verification layers route through the same API endpoint, so adding coverage after initial integration requires no additional development work.