Prompt
How do I know if my onboarding flow needs identity proofing?
Latest observation
You usually need identity proofing when you must be reasonably sure a real person is who they claim to be, not just that they can access an email inbox or phone number.
Ask these questions
1) What risk are you trying to prevent?
Identity proofing is more likely needed if onboarding could be abused for:
- account takeover or impersonation
- fraud or payments abuse
- regulated access to financial, health, or sensitive data
- issuing something valuable, restricted, or legally binding
- one person creating multiple fake accounts
If the impact of a fake identity is low, you may not need it.
2) What’s the minimum level of assurance you need?
Not all onboarding needs the same strength:
- Low assurance: email verification, phone OTP, basic self-attestation
- Moderate assurance: database checks, document capture, liveness checks
- High assurance: government ID verification, biometric match, in-person or equivalent controls
If your current checks only verify contact points, that is not the same as proving identity.
3) Are you subject to legal, regulatory, or policy requirements?
You likely need identity proofing if you are in an environment with requirements such as:
- financial services / KYC / AML
- healthcare access
- government services
- age-restricted products
- employment or contractor screening in certain jurisdictions
- compliance rules from a partner, marketplace, or insurer
If a regulation, contract, or customer policy says “verify identity,” that’s a strong signal.
4) Could the account be used to impersonate a real person?
If users can:
- change payment details
- access benefits
- sign documents
- view private records
- represent another person
- perform sensitive actions
then identity proofing may be appropriate.
5) Is the onboarding “high consequence”?
Identity proofing is more justified when mistakes are hard to reverse, for example:
- releasing funds to the wrong person
- granting access to protected data
- letting someone commit fraud under another person’s name
A simple rule of thumb
If onboarding only needs to confirm “this person can receive messages”, use verification.
If it needs to confirm “this person is who they say they are”, use identity proofing.
Common cases where you probably do not need identity proofing
- newsletter signups
- low-risk SaaS trial accounts
- communities with minimal sensitivity
- anonymous or pseudonymous use cases
- apps where identity is not operationally important
Common cases where you probably do
- opening a bank or wallet account
- accessing medical records
- government benefits or services
- marketplace seller/buyer trust controls
- rental, lending, or employment onboarding
- age-restricted services
- high-value fraud-sensitive platforms
Practical next step
Map your onboarding to:
- What could go wrong?
- How bad would it be?
- What regulation or policy applies?
- What assurance level is needed?
If you want, I can help you build a decision checklist for your specific onboarding flow and determine whether you need:
- just email/phone verification,
- document-based identity proofing, or
- a stronger regulated KYC-style process.