ID Verification confirms who is signing before they sign, by checking a government ID and the person holding it. The signer photographs their driver's license or passport and takes a selfie, inside the same signing flow. Verdocs checks that the document is genuine, that the selfie matches the ID photo and shows a live person, and, when you require it, that the ID belongs to the recipient you meant to send to.
It works for signers anywhere in the world, and you switch it on per signer, only for the documents that need it.
ID Verification Plus is coming soon. It adds checks against identity data and the signer's phone account, and it is designed toward NIST IAL2.
The signer photographs their ID and takes a selfie without leaving your signing flow.
Four things, and each answers a different question.
They run together because no one check covers the others. A face match does not prove the document is genuine, and a genuine ID can still belong to the wrong person.
Every check has to pass before the document opens.
It answers the question the other checks cannot: is this the person you meant to send the document to? When you know who should sign, require the match, and a genuine ID belonging to someone else will not pass. When you do not know the identity in advance, as with an open or ad hoc request, ID Verification still checks that the ID is genuine and that the person holding it is the one in the photo.
A valid ID is not enough on its own. When you require the match, it has to be the ID of the person you sent to.
KBA asks the signer questions drawn from public records, and it works for US signers. ID Verification checks a physical document and the person presenting it, so it works wherever your signers are. It does not look the signer up in identity databases; it relies on the document, the selfie, and the details you supplied. ID Verification Plus adds those data checks.
When a disputed signature would be expensive and you need to know a real person holding a genuine ID signed: payment and payee changes, claim releases, account changes, and signers outside the US where KBA is not available. Like the other authentication steps, it is a choice you make per document, not a setting for everything you send.
Worldwide, with driver's licenses and passports. ID Verification checks the authenticity of the document itself, so it does not depend on the signer's country having a national eID scheme.
ID Verification Plus is coming soon. It includes everything in ID Verification, then adds three checks:
ID Verification Plus is designed to meet NIST SP 800-63A-4 Identity Assurance Level 2 (IAL2). Conformity has not been established yet: implementation, testing and assessment of the full workflow come first.
Plus builds on the same ID and selfie checks, then corroborates the identity and the phone the signer controls.
Choose per document, to match the stakes. ID Verification tells you a real person holding a genuine ID signed. Plus is for workflows that also need that identity corroborated against data and a phone the person controls, such as account opening and lending, insurance applications and policy changes, claim releases and other sensitive authorizations.
| ID Verification | ID Verification Plus | |
|---|---|---|
| Document authentication | Included | Included |
| Selfie-to-ID face comparison | Included | Included |
| Passive liveness | Included | Included |
| Recipient matching | When the sender requires it | When the sender requires it |
| Identity-data validation | Not included | Included |
| Phone-account association | Not included | Included |
| Phone control, by secure SMS link | Not included | Included |
| NIST IAL2 | No claim | Design target; assessment pending |
| Availability | Now, on paid plans | Coming soon |
| Price | $2.50 per attempt | Set at launch |
ID Verification is $2.50 per attempt. Each attempt is charged, including one that fails. It is available on paid plans and activated for your account on request, with no setup fee. ID Verification Plus will be priced when it launches.
Add ID Verification to a recipient's authentication methods (auth_methods) through the API. Verdocs runs the authentication steps in a fixed order, and a failed step stops the signer. The Recipient Auth Ladder guide in the developer documentation covers the order and the webhooks.
Not every insurance document needs the same signer check, and document type alone should not decide it. A starting matrix for matching checks to the signer, the requested action, and the money involved.
Read the post2026-08-23IRS Publication 1345 requires KBA and also points at a NIST assurance level. Reading both documents carefully shows why that question has no clean answer.
Read the postPrices sit with the other identity add-ons on the pricing page.
Talk to us about itGeneral information, not legal advice; consult your own advisors for the signature level your documents require.