Verify Who's Actually Showing Up

Most authentication systems only verify that someone knows a password or controls an email address. For regulated industries, marketplaces, healthcare platforms, and fintech — that's not enough. You need to know who the person actually is.

DVLY integrates identity verification into your onboarding and authentication flows so that verified identity attributes flow directly into your user records and access decisions.

Document Verification

Government-issued IDs from 190+ countries — passports, driver's licenses, national IDs, and residence permits. NFC chip reading for high-assurance passports.

Medical Provider ID Verification

NPI lookup, DEA number validation, state medical license verification, and board certification checks for healthcare platforms requiring provider credentialing.

Selfie & Liveness Detection

ISO 30107-3 PAD Level 1/2 compliant liveness checks — passive and active challenge modes. Selfie-to-document comparison with confidence scoring.

Know Your Business (KYB)

Business entity verification: incorporation records, registered agent, beneficial ownership (UBO), and business health checks across US and international registries.

Sanctions Screening

OFAC SDN, EU, UN, FATF, and custom watchlist screening for both individuals and business entities. Continuous monitoring available.

CIAM Integration

Verification results flow directly into Auth0 or Okta user metadata. Progressive verification — only ask for what you need, when you need it.

Healthcare & Regulated Platforms

Healthcare platforms face a specific verification challenge: you need to verify that someone is both who they claim to be and that they hold the credentials they claim. DVLY handles both layers.

Provider Credentialing Workflows

We build end-to-end credentialing flows that verify government ID, match it to NPI records, validate active state licensure, and flag expired or sanctioned providers — all before granting access to your platform.

Patient Identity Assurance

For patient-facing platforms, DVLY implements NIST 800-63-3 IAL2-aligned verification workflows — including in-person or remote supervised identity proofing where required by your use case.

HIPAA-Aligned Data Handling

We work with verification vendors that are HIPAA-eligible and ensure that PII and verification artifacts are handled, retained, and disposed of in accordance with your compliance requirements.

Frequently Asked Questions

What identity documents can DVLY verify?

DVLY's identity verification integrations support government-issued IDs from 190+ countries including passports, driver's licenses, national ID cards, residence permits, and visas. We also support NPI verification for US medical providers.

How does liveness detection work?

Liveness detection uses passive or active challenges (following a dot, blinking) to confirm a live person is present during selfie capture. We integrate with certified ISO 30107-3 compliant liveness solutions to meet high-assurance requirements.

What is Know Your Business (KYB) verification?

KYB verifies the legitimacy of business entities — confirming incorporation records, beneficial ownership, registered agent information, and checking against sanctions lists like OFAC, UN, and EU. It's required for financial services, marketplace platforms, and regulated industries.

Can DVLY integrate identity verification into our existing Auth0 or Okta flow?

Yes. We specialize in integrating verification providers (Persona, Onfido, Vouched, Socure, and others) into Auth0 Actions, Okta Hooks, or custom onboarding workflows. Verification results can gate access, trigger progressive profiling, or populate user metadata.

Is DVLY's identity verification HIPAA or SOC 2 compliant?

DVLY designs verification flows to meet the compliance requirements of your industry. We work with verification vendors that are HIPAA-eligible, SOC 2 Type II certified, and ISO 27001 compliant, and we implement the access controls and audit logging your compliance posture requires.

Know your users. Really know them.

Let's talk about what your use case requires and which verification approach fits.

Talk to DVLY