Resources
Everything you need to understand ShieldID.
Plain-language explainers for the people who buy identity verification, and reference material for the people who build with it. No sales call required to read any of it.
Everything in one place.
Blog
Notes on identity verification, privacy law and how the pipeline actually works, written from the facts, not the marketing.
Read the blogGuides
A practical “how to run identity verification” walkthrough for each industry ShieldID serves.
Browse guidesCase studies
How real teams put ShieldID to work. We publish these once a customer signs off, not before.
See case studiesFAQ
Straight answers to the questions buyers, developers and compliance leads ask before they trust us with an applicant's ID.
Read the FAQGlossary
Liveness, MRZ, PIPEDA, false match rate and the rest of the vocabulary, defined in plain language.
Open the glossaryContact
Talk to a person about a plan, an integration question or anything the docs did not answer.
Get in touchStart here
Two ways in, depending on what you're doing.
Pick the path that matches your job today. Both end at the same product.
I'm a developer
Skip the marketing pages and go straight to the API.
I'm evaluating a vendor
Understand what ShieldID does, what it costs and how it compares before you talk to anyone.
From the blog
Recent explainers.
Three posts to start with, each drawing only on our published research.
What PIPEDA means for ID verification
The ten PIPEDA principles, translated into what a business collecting ID actually has to do.
How active liveness detection works
Why a guided challenge beats a single selfie, and what a presentation attack looks like.
Reading a PDF417 barcode
What's actually encoded on the back of a North American driver's licence, and how it's checked.
From the guides
One guide per industry.
How to run identity verification for the businesses ShieldID is built for.
Questions
About these resources.
Get started
Ready to see it work?
Create a sandbox session and run a verification on your own phone to see the result and the signed webhook it sends.