ID document verification
Canadian and US driver's licences, passports, PR cards and provincial ID, read front and back, with the barcode or passport zone cross-checked against the printed fields.
Condo corporations
Condo corporation identity verification for boards and managers.
A new owner registering at closing, a tenant a unit owner has leased to, a resident asking for fob access: ShieldID verifies the government ID, matches the live face and keeps a record, so your board and your property manager know who is actually on file.
The problem, in your words
You are registering people you did not personally meet at the door.
Closings happen through lawyers, leases are filed by mail or email, and access requests come in from names on a spreadsheet. Three patterns come up again and again.
Borrowed or unverified ID
A registration form arrives with a photocopy or a photo of an ID. There is no reliable way for a property manager to tell, by eye, whether it belongs to the person named or whether it has been altered.
Tenants the corporation never sees
A unit owner leases to a tenant and files the lease; the corporation is asked to register someone it has never met, sometimes for fob or amenity access, without any way to confirm who that person actually is.
Fraud and disputes at a distance
A remote or investor owner, a subletting arrangement, or an access dispute at the front desk: the corporation needs an answer about who is entitled to be there, and needs to be able to show its work later.
A worked example
How it plays out for a fictional condo corporation.
Lakeview Towers Condominium Corporation is a fictional 180-unit building managed by a third-party property manager. A unit sale closes, and the new owner registers a tenant. Here is one registration, start to finish.
The registration form arrives
The new owner's lawyer files the closing paperwork, and separately the owner submits a tenant registration for the unit, as the corporation's bylaws require.The manager sends a verification link
The property manager emails the tenant a ShieldID hosted verification link, or hands over a QR code at the front desk when the tenant picks up their fob.The tenant verifies on their own phone
They photograph their ID, take a short liveness challenge and give their consent, in a few minutes, without a trip to the management office.The manager reviews per-field verdicts
Name and date of birth are checked against what the tenant registration form states, cross-referenced against the barcode and the printed document, with a face match reported against a fixed decision line.A dispute at the next AGM
An owner challenges whether a particular occupant was ever properly registered. The manager pulls the Activity Ledger entry: when the link was sent and opened, the verified result, and who on staff reviewed it. The ID image itself has long since been purged; the record that the check happened has not.
What matters most for this
The checks that support owner and tenant registration.
Every check below runs on every verification, on every plan. None of it is an optional extra.
Face match
The selfie taken on the resident's own phone is compared with the document portrait and reported against a fixed decision line, so a registration is not accepted on the strength of a document alone.
Liveness detection
A short guided challenge, tracked on 478 facial landmarks over at least ten frames, so a static photo cannot stand in for the resident.
No refusals by document type
An international owner's passport or an out-of-province licence is read field by field rather than rejected outright, so remote and newcomer owners get the same evidence as anyone else.
A kept record
Every step around the check is entered in the Activity Ledger, append-only and enforced by the database, useful when a board decision or an access dispute is later questioned.
English and French
The verification flow and the portal are available in both languages, useful for a Quebec condo corporation or a bilingual building.
For governance and disputes
What the Activity Ledger gives a board and its manager.
A verification without a record is just something someone remembers happening. Every action around a ShieldID verification is entered in an append-only Activity Ledger, enforced by the database: entries can be added, never edited or deleted, not by staff and not by us.
What's on the record
- Today
- When a registration link was opened, when consent was given, the verified or failed result, and who on the management team reviewed it — each with a timestamp.
- Why it matters here
- An AGM eligibility challenge, an access dispute or an owner's complaint about how their tenant's ID was handled can be answered from the ledger instead of a manager's memory.
- Reading the evidence is itself logged
- Opening the network and device detail behind an entry needs a written reason of at least twelve characters, and that request is itself recorded.
On the way
- Per-image view and download events
- Exactly who opened the ID photo itself, separate from the result summary.
- Decision events
- The board or manager's own registration decision, and the reason, recorded against the verification.
- Purge receipts
- A ledger entry each time an image is automatically deleted on its retention timer.
- CSV export
- A spreadsheet export for board packages — the Activity Log is currently readable only through the JSON API, with no dedicated export feature yet.
How it fits your building
Three ways to plug it in.
Pick the one that matches how your corporation already registers owners and tenants.
Hosted link or QR code
Email a registration link ahead of move-in, or show a QR code at the front desk when a fob or amenity access is issued. No app install, and the front desk never needs a camera of its own.
API
One REST API for a property management platform's registration workflow: create a session, send the link, receive a signed webhook when the result is in. Sandbox sessions are never billed.
Crown Ledger
ShieldID powers identity verification inside Crown Ledger, our condo governance product, for corporations that manage owner and tenant records there.
Privacy and consent
What to know before you ask a resident for ID.
This is background, not legal advice. What a condo corporation may collect, and for how long it must be kept, is set by your provincial condominium legislation, your corporation's governing documents and applicable privacy law. Check with your own counsel before you set a policy.
- The resident's consent to the check is captured on their own device, before capture begins.
- ID images are purged automatically on a short timer, seven days by default, configured for the service as a whole; keep your own board or management file note if your corporation's record-keeping needs a longer trail.
- ShieldID reports verdicts and evidence, not a registration decision. Whether to register an owner or tenant, and on what terms, stays with the board or its manager under the corporation's own bylaws.
- Data is processed and stored on Crown Stack's own self-managed servers; ShieldID does not publish a physical location, city or data-centre name, and holds no PIPEDA certification.
How this compares
Against a photocopy handed across the front desk.
Categories, not vendor names. "Typical enterprise IDV" describes what we found across the identity-verification market broadly; your mileage will vary by vendor.
| Capability | ShieldID | Typical enterprise IDV | Manual checks |
|---|---|---|---|
| Confirms the ID itself is genuine, not just a legible photocopy | Yes | Usually | No |
| Confirms the resident is the person in the photo, live | Yes | Usually | No |
| Works for an owner or tenant you will never meet at the office | Yes | Usually | No |
| Reads an unfamiliar or foreign document instead of refusing it outright | Yes | Rarely | Depends on staff |
| Leaves a searchable record for an AGM or access dispute | Yes | Not offered to the customer | A filing cabinet, maybe |
| Available in English and French | Yes | Depends on the vendor | Depends on staff |
Objections, answered
What boards and property managers ask first.
Straight answers, including where the answer is "check your own governing documents."
Can our condo corporation require ID verification from owners and tenants?
That depends on your province, your corporation's governing documents and how the requirement is applied. This is not legal advice — check your provincial condominium legislation and your corporation's own counsel before you set a policy.
Will this slow down move-ins?
The check runs on the resident's own phone in a few minutes, on their own schedule, not queued at the management office. A QR code at the front desk works just as well as an emailed link.
What about an owner who lives abroad, or an unfamiliar foreign document?
ShieldID reads whatever it can from any document and reports each field's own verdict instead of rejecting it outright because the layout is unfamiliar — the same evidence for a remote owner as for anyone else.
Who can see the ID once it's submitted?
The image is purged automatically on a short timer. Access to the verification record is logged in the Activity Ledger; per-image view logging is coming soon.
We already use Crown Ledger for governance. Do we need this separately?
No. ShieldID is the identity-verification layer built into Crown Ledger's owner and tenant records. If you use Crown Ledger, this is already part of your workflow.
What you see
Owners and tenants verified, and the board can see how.
A new owner or tenant verifies from the registration link. The manager sees the fields read from the ID and a verdict for each check.
Questions
Straight answers for boards and managers.
Try it before your next registration
Run one sandbox verification before you send it to a resident.
Sandbox sessions are never billed. See the report your board or manager would actually receive.
Already run governance through Crown Ledger? This verification is already built in.