Require a government ID and a selfie before the document unlocks. You compare them against the person on live video and approve — so a lease, a transfer or a six-figure agreement is never signed by whoever happened to have the link.
For the signings where the wrong signer would be a disaster
How it works
Identity platforms hand you a score. This hands you the evidence — the document, the face, and the live person — and records the judgement you made.
Your signer photographs a government-issued photo ID — licence, passport, provincial card — with the phone already in their hand. No app, no account, no reader hardware.
Submitted in-browserThey take a selfie in the signing room itself, at the moment of signing — not a photo from their camera roll taken who-knows-when by who-knows-whom.
Taken live, in sessionYou see the ID, the selfie and their live video tile side by side, and either approve — a verified badge appears for everyone in the room — or send it back with a reason.
Approve or request resubmitRequired or optional
Set identity checks to Required and nobody can put a signature on the document until you have approved their ID. Set them to Optional and guests join and sign freely. It is a per-session choice, because a $200 waiver and a property transfer do not need the same ceremony.
Signers always see which mode they are in and what is expected of them — no surprise demand for a passport halfway through.
See the signing room →
The resubmit loop
Nobody's first attempt is perfect. A licence catches the flash, a selfie crops the chin. Instead of failing the signer with an error code, you return it with a plain-language reason — "the expiry date is cut off" — and they simply try again.
Every round trip is logged, so the record shows not just that identity was confirmed, but exactly how many attempts it took and why.
Read the walkthrough →
Identity, intent, integrity
An ID check on its own proves who was there. Pair it with a recorded live session — where consent is spoken out loud — and a tamper-sealed PDF, and you have the full set: identity, intent, and integrity.
That is the difference between a signature you can point to and a signature you can defend.
How the seal works →
Audit & privacy
Every verification event — submitted, approved, resubmit requested — is written to the Audit Report with who did it and when, and exports to CSV with the rest of the record.
The ID images themselves are stored under a session-scoped path, served only to the authenticated host, and destroyed when the verification purpose ends. Collect what the job needs, keep it while the job needs it, then let it go — the principle behind PIPEDA and Quebec's Law 25, and the reason we publish a Privacy Impact Assessment.
PIPEDA & Law 25 →
Why this is different
Identity platforms are built for engineering teams verifying strangers at scale. This is built for the property manager, broker, agent or attorney checking one person, today, in a room they are already hosting.
The ID, the selfie and the live face, side by side. Not a confidence score you have to take on faith and cannot explain later.
The person is on camera while you review. A stolen ID and a stolen selfie still have to get past a live face.
Required mode locks the sign button. The check cannot be skipped, ignored or clicked past by an impatient signer.
Included with Pro at $9.99/month. Dedicated identity vendors quote per check on an annual contract — fine at scale, absurd for six signings a month.
No SDK, no API keys, no sandbox, no developer. Turn it on for a session and it is running.
Verification events sit in the same Audit Report as the signing itself and export together — one evidence file, not two systems to reconcile.
A bad photo gets a sentence explaining what to fix, not a rejection. Fewer abandoned signings, fewer support calls.
ID images are session-scoped, host-only, and destroyed when the purpose ends. Holding identity documents forever is a liability, not a feature.
Designed around PIPEDA and Quebec's Law 25, with a published Privacy Impact Assessment rather than a compliance page that says "trust us".
Honest comparison
We are not trying to be Jumio. If you are onboarding ten thousand strangers a month, buy a dedicated identity platform. If you are verifying the people you are already meeting to sign a document, this is the better tool.
| What you need | EZ PDF Editor Pro | Dedicated identity platform |
|---|---|---|
| ID document + selfie capture | Included | Included |
| Checked against a live human on video | Yes — that is the model | Rarely; usually async |
| Automated document forensics & liveness scoring | No — you review it yourself | Yes, their core strength |
| Watchlist / AML screening | Not offered | Usually available |
| Tied directly to a document signing | Same session, same record | Separate system to integrate |
| Engineering work to deploy | None | SDK / API integration |
| Pricing model | $9.99/mo, unlimited checks | Per verification, annual contract |
| Good for thousands of checks a month | No — built for hosted signings | Yes, built for scale |
Right-hand column describes the common shape of dedicated identity-verification vendors as of August 2026, generalised on purpose — capabilities and pricing vary by vendor and tier. Everything in the EZ PDF Editor column is live today.
Pricing
Identity verification lives inside the Video Signing Room, which is part of Pro. There is no per-check fee and no annual commitment.
Questions
No, and that is deliberate. There is no black-box authenticity score, no liveness algorithm and no watchlist screening. You see the ID, the selfie and the live person, and you make the call — and the record shows who approved, when, and on what basis. If you need automated document forensics at scale, a dedicated identity platform is the right tool.
Any government-issued photo ID — a driver's licence, a passport, a provincial ID card. They photograph it in the browser with the device they already have.
You send it back with a plain-language reason and they resubmit. The loop is part of the flow, not an error state, and every round is logged.
Yes — it is a per-session setting. Required locks the sign button until you approve. Optional lets guests join and sign without a check. Guests always see which mode applies to them.
They are stored server-side under a session-scoped path, served only to the authenticated host, and destroyed when the verification purpose ends. Details are in the privacy policy and the Privacy Impact Assessment.
No. They open their link, submit the ID and selfie, and sign — no app, no account, no watermark. Only the host needs a Pro account.
Yes. Submitted, approved and resubmit-requested events all land in the Audit Report, which exports to CSV, and the signing itself produces a tamper-sealed PDF anyone can verify.
Canadian law recognises electronic signatures broadly; what decides a dispute is the evidence behind one. An ID check, a recorded session and a sealed file make that evidence considerably harder to argue with. This is general information, not legal advice.

Turn on identity checks for your next signing — government ID, selfie, live face, your approval, all in the record.
Included with Pro — $9.99/mo, unlimited checks. See pricing.
Keep reading