Skip to main content
TemplateFREE⏱️ 2-3 hours

Identity Verification Template for PMs

A product planning template for identity verification with KYC/KYB requirements, verification tier design, vendor evaluation, and fraud prevention.

Updated 2026-03-05
Identity Verification
#1
#2
#3
#4
#5

Edit the values above to try it with your own data. Your changes are saved locally.

Get this template

Choose your preferred format. Google Sheets and Notion are free, no account needed.

Frequently Asked Questions

How long should we retain identity verification data?+
Retention periods depend on your regulatory framework. BSA/AML (US) requires 5 years after the account is closed. UK AML regulations require 5 years after the business relationship ends. GDPR requires you to delete data when it is no longer necessary for the purpose it was collected. Build your data retention policy around the strictest applicable requirement, and automate deletion at the end of the retention period.
What verification pass rate should we expect?+
First-attempt pass rates vary by method and geography. Database checks (name + DOB + SSN) typically pass 85-92% of US users on the first attempt. Government ID + selfie flows pass 80-90% on the first attempt. The remaining users usually fail due to poor photo quality, expired documents, or data mismatches (maiden name vs. married name). Providing clear camera guidance and allowing retries brings total pass rates above 95%.
Should we verify business entities differently than individuals?+
Yes. Business verification (KYB) is more complex than individual KYC because you need to verify the business entity itself, its beneficial owners (UBOs), and potentially its financial standing. Start with business registry lookups to confirm the entity exists, then verify each UBO with the same individual KYC flow. The [data requirements template](/templates/data-requirements-template) can help you map the data fields needed for KYB.
How do we handle users in countries where we do not support verification?+
Be transparent. Show the list of supported countries during onboarding and inform users early if their country is not supported. Do not let users complete the entire flow before rejecting them for geographic ineligibility. If you plan to expand coverage, collect waitlist signups for unsupported countries. ---

Related Tools

Explore More Templates

Browse our full library of PM templates, or generate a custom version with AI.