Watch one verification, start to finish.

Every business that meets its customers at a distance has the same problem. A tenant application. A new borrower. A seller signing up. You need to know who they are.

And you may never meet them. So you ask for a photo of the ID. Here is one. The licence is real. It just isn't hers. So you ask for a live selfie. Here is one. It is a video, played to the camera.

And this one was never a person at all. A generated face, built to pass a photo check. And the document itself can be edited: a photo swapped, a date of birth changed, a barcode that no longer says what the print says.

Most checks cannot tell. So businesses do one of two things. They trust too easily. Or they keep a copy of every ID and every face they were ever sent, which is a risk of its own.

Trust too easily, or store too much. Is Avery really Avery? Someone on the other end of this link needs to know. Avery opens it on their own phone. At the bottom: verified by ShieldID.

No account, no app to install. The front of the licence, then the back. Now Avery's face, and a short guided challenge: turn slowly to the left, and back. Done. Avery is verified, and the screen says the ID photos are deleted after seven days, by default.

Simple for Avery. Harder for the business, which may never meet Avery. That is the gap. ShieldID closes that gap. Privacy-first, built in Canada. Identity verification that shows its work.

Most providers hand you one score, and keep the images for years. ShieldID hands you twelve verdicts, each with its evidence, and deletes the images after seven days by default.

Most keep your applicants' data outside Canada. ShieldID processes and stores ID data in Canada. Most are priced for millions of checks a year. ShieldID is sized for teams that need a few dozen a month.

So what just happened? Six stages. One record. One product doing the work of many. Capture: a link or a QR code, both sides of the ID, and the face. ShieldID extracts what Avery's licence says, front and back,

barcode included, then compares it all, field by field. Sources that disagree are flagged, never averaged. Next, a live check that a real person is present right now,

not a photo, a screen or a mask. The industry calls it liveness. Turning is not enough: the head has to come back to centre, which a flat photo cannot do. Then face match: is this the same person as on the document?

One face, one portrait, never a search through other faces. Pass or fail, against a decision line the company sets. Three more checks look at the selfie: for a printed photo or a screen, a synthetic face, and a mask.

The document gets a tamper signal, advisory and not yet calibrated. Each signal is reported on its own, and no plan or setting turns one off. When checks fail, the rows say so.

Here the advisory tamper signal is flagged, and the face and the name do not match. You make the call. Last, the record: twelve per-field verdicts, written to the business account and delivered by a signed webhook.

The images are purged on a timer. The result stays. And Avery is back where they started. Now look underneath. Document capture frames and crops the ID on the phone.

A link, a QR code or a message starts the session. Crop and field models find the document and each printed field. A document reading engine reads the printed side.

Barcode reading decodes the back of the licence. Machine readable zone reading checks a passport's check digits. Cross-source checking compares every source against every other.

Liveness asks a real person to blink, turn and nod. Face match compares the selfie to the document portrait. Anti-spoof, deepfake and mask detection check the selfie three ways.

A document tamper signal is reported for review: advisory, not yet calibrated. Watchlist screening, an add-on, checks public sanctions lists. Secure image storage encrypts the images and purges them after seven days by default.

Secrets and encryption protect personal data and sign every webhook. A model inference runtime runs the detection and matching models. Sign-in and API keys control access to the service.

Hosting and TLS keep the service in Canada and every connection encrypted. API docs, in English and French, show developers how to call it. ShieldID is built from seventy-three components wired into the live service.

They come from forty-eight outside projects, vendors and data services. Grouped, that is eighteen kinds of capability a business would otherwise have to source separately.

Identity verification takes many components from many different sources. And ShieldID delivers them as one product and one integration, privacy first and hosted in Canada.

On the other end of the link: you. Every field read from the ID, with its source, and a verdict for each check. ShieldID reports what it found. You make the call.

Everything the decision needs. Nothing it doesn't. Avery's ID photos, selfie included, are deleted automatically after seven days by default. The record of the check stays.

Hosted in Canada: Canadian data, hosted in Canada. Designed to align with PIPEDA and provincial privacy law. Built for the businesses the big vendors ignore. Avery could be a tenant, a client, a condo owner, a borrower, a seller or a signer.

And ShieldID already runs inside Crown Stack's own products: RentKey, Crown Ledger and Trust Ledger. For the team building it: one REST API. Create a session. Send the link, or a QR code.

Receive a signed webhook, and read the result. Sandbox sessions are never billed. Go live in an afternoon. Start free in sandbox, or book a demo. Avery's part was simple.

The call is yours. ShieldID shows its work. shieldid.ca. Book your twenty minute demo today.