Identity proofing methods are the concrete techniques an organization uses to establish who a new applicant really is, from a clerk examining a passport at a counter to a phone reading the signed chip inside an electronic ID. Each method has strengths, weaknesses and costs that suit some services far better than others.
This guide compares the main methods side by side. It is meant for people who design or operate onboarding processes and want to choose a sensible mix, and for curious users who wonder why one service asks for a selfie while another sends them to a post office or a bank.
Why No Single Method Fits Every Service
Services differ in what they protect and whom they serve. A tax portal holds information that could enable serious fraud, while a library account holds very little. A rural benefits office serves people with limited internet access, while a fintech app serves mostly smartphone users. One method cannot satisfy all these needs.
Methods also fail in different ways. A counter clerk may miss a high-quality forgery but is hard to fool with a screen replay. An automated remote check may scale to millions of users but can be targeted by manipulated images. Knowing these failure patterns is the starting point for any choice.
For that reason, mature programs rarely depend on one technique. They choose a primary method suited to most users, add fallback routes for people the primary method cannot serve, and layer extra checks for higher-risk cases. The rest of this guide explains the building blocks.
How to Judge a Proofing Method
Before comparing techniques, it helps to agree on the criteria. Teams that skip this step often choose whatever a vendor demonstrates first. A short, shared checklist keeps the discussion focused on the service’s actual risks and the people it serves.
- Strength: how hard the method is to defeat with stolen, forged or manipulated evidence.
- Reach: how many legitimate applicants can complete it, including those without smartphones or common documents.
- Privacy footprint: how much personal and biometric data it collects and retains.
- Cost and speed: staff time, vendor fees and how long applicants wait for a decision.
- Auditability: whether decisions can be reviewed, explained and appealed later.
No method scores highly on every criterion at once. In-person checks are strong and auditable but slow and costly. Fully automated remote flows are fast and cheap but need careful defenses. The right balance depends on the assurance level the service requires and the population it must reach.
In-Person Proofing at a Counter
The oldest method is still one of the strongest. The applicant visits an office, a trained officer handles the physical document, checks its security features under suitable lighting, and compares the photo with the face in front of them. Many programs also capture a new photo or fingerprint at the visit.
Physical presence makes several attacks harder. There is no camera feed to manipulate, and an officer can ask questions, request a second document or call a supervisor when something feels wrong. For the highest assurance levels in frameworks such as NIST SP 800-63, in-person or equivalent supervised processes are expected.
The drawbacks are practical. Applicants must travel during office hours, organizations must staff and train counters, and officer skill varies. Networks of partner locations, such as post offices or bank branches, can extend reach, but they require consistent procedures and oversight to keep quality even across sites.
Remote Proofing Techniques
Remote methods let applicants complete proofing from a phone or computer. They have grown quickly because they are convenient and scale well, but each technique carries different risks. Three approaches appear most often.
Document Capture with Selfie Comparison
The applicant photographs an identity document and takes a short selfie or video. Software checks the document for signs of tampering and compares the face with the document photo. Liveness detection checks that a real person is present rather than a photo or replay. This method is fast but depends heavily on the quality of these defenses.
Supervised Video Sessions
A trained agent joins a live video call, guides the applicant through showing the document from several angles, and observes them throughout. The agent can ask spontaneous questions and request specific movements. Supervision raises confidence compared with fully automated flows, though it costs more and requires scheduling, language support and secure handling of recordings.
Authoritative Record Checks
Instead of examining a document, the service checks the applicant’s claimed details against a trusted record, such as a government registry or an account at a bank that already proofed them. This confirms that the identity exists and the details match, but it does not prove the person typing is that identity, so it is usually paired with another method.
Digital Credentials and Chip Reading
A growing set of methods relies on cryptography rather than visual inspection. Electronic passports built to ICAO specifications carry a chip whose data is digitally signed by the issuing country. A phone with NFC can read that chip and verify the signature, confirming that the data has not been altered since issuance.
Mobile driver’s licenses that follow ISO/IEC 18013-5, and credentials held in digital identity wallets, work on a similar principle. The issuer signs the data, and the verifier checks the signature. Some formats allow the holder to share only specific attributes, which supports data minimization during proofing.
Signature checks prove that the data is authentic, not that the person presenting it is the rightful holder. Good designs therefore combine chip or credential checks with a binding step, such as comparing a live face with the signed photo or requiring the holder to approve the presentation on their own secured device.
Trusted Referees and Vouching
Some applicants lack the standard documents most methods require. Refugees, people leaving institutions, survivors of domestic abuse and young adults may not hold a passport or driver’s license. Excluding them entirely can cut them off from essential services at the moment they need help most.
Trusted referee methods address this gap. A trained person, such as a caseworker, notary or designated official, reviews alternative evidence and confirms the applicant’s identity based on their professional judgment. Vouching schemes let a known, verified person attest that they know the applicant, under defined rules and accountability.
These routes need careful controls. Referees must be trained, their decisions logged and reviewed, and the number of vouches any one person can give should be limited. When run well, they widen access without becoming an easy shortcut for people attempting to create false identities.
Knowledge Questions and Why They Have Faded
For many years, services asked applicants questions drawn from credit or public records, such as previous addresses or loan amounts. The idea was that only the real person would know the answers. This approach, known as knowledge-based verification, was cheap and required no documents.
Its weakness is that the answers are no longer secret. Data breaches, social media and data brokers have made much of this information available to criminals. Current NIST guidance no longer accepts knowledge questions as a way to verify an applicant’s identity, and many organizations have phased them out.
Knowledge questions may still appear as a minor supporting signal in some processes. They should not stand alone as proof of identity for anything sensitive. Our separate guide on knowledge-based verification explains the problems in more depth and the alternatives that have replaced it.
Combining Methods into Layers
The most reliable programs blend methods so that the weaknesses of one are covered by the strengths of another. A record check confirms that an identity exists, a document check confirms the evidence is genuine, and a binding check confirms the applicant is its rightful holder.
- Use a primary remote method for most applicants, chosen for reach and speed.
- Add a supervised or in-person route for higher-risk cases and failed attempts.
- Provide a trusted referee path for people without standard documents.
- Apply context signals, such as repeated attempts, to decide when to escalate.
Layering should not mean piling every check on every applicant. Escalate only when risk or uncertainty calls for it. This keeps the experience smooth for most people while focusing scrutiny, cost and data collection where it actually reduces harm.
Accessibility and Inclusion Considerations
A method that most users can complete may still exclude significant groups. Selfie capture can be difficult for people with certain disabilities, document reading requires a compatible phone, and video sessions may not suit people with hearing impairments unless captioning or sign language support is available.
Inclusion is also a fairness and legal concern. Automated face matching can produce uneven results for different populations, skin tones or camera setups. Organizations should test methods with diverse users, monitor failure rates by method, and investigate patterns rather than assuming that applicants who fail are attempting fraud.
Clear instructions, plain language, multiple languages and a visible route to human help make a large difference. Every proofing program should be able to answer a simple question: what happens to the applicant who cannot complete our main method, and how long will they wait?
A Method Selection Scenario
Consider a hypothetical city government launching an online portal for housing assistance. The service handles sensitive data and payments, so it needs moderate to high confidence. Many applicants are older or on low incomes, and some lack a current photo document.
The city chooses remote document capture with selfie comparison as its primary method, backed by a record check against its own resident registry. Applicants who fail or cannot use a phone can book an appointment at a library branch with trained staff, where an officer completes in-person proofing.
For people without documents, caseworkers act as trusted referees under a written policy and audit trail. The city deletes raw images after a defined period, publishes a plain-language privacy notice, and reviews failure statistics each quarter to adjust instructions or methods where problems appear.
Building a Method Mix That Can Adapt
Proofing methods change faster than most organizations expect. Mobile driver’s licenses and wallet-based credentials are spreading, attack techniques such as deepfakes keep improving, and standards bodies revise their guidance. A method mix chosen today will need adjustment within a few years.
Design for that change from the start. Keep proofing logic separate from the rest of the application, use contracts that allow switching providers, and record which method was used for each applicant so you can re-verify specific groups if a weakness is discovered later.
Revisit the decision regularly as well. Review fraud cases, failure rates and user complaints, track updates from NIST, eIDAS authorities or your national digital identity program, and adjust the mix so that strength, reach and privacy stay in balance as conditions evolve.