Changelog
The ShieldID changelog.
What shipped, and when. Entries are written for the people integrating against the API, not as an internal engineering log.
Release notes
Customer portal and dashboard
Usage, keys and results in one dashboard, in English or French. Customer sign-in is coming soon; until then, request a sandbox key through the contact form.
How ShieldID reads unfamiliar documents, and how it is built
Formalized a rule that already ran in the pipeline: ShieldID never refuses a document because it doesn't recognize the type or issuer — it extracts and verifies what it can, field by field, instead of rejecting at the door. ShieldID is also built as a standalone identity-verification service that products like RentKey, Trust Ledger and Crown Ledger integrate with through the same API as any other customer.
Fixed a result-display bug on face match
A reference confidence figure could appear on a result that should have failed outright on a clear document mismatch. Fixed so the figure only ever reflects which side of the decision line the result actually falls on.
Improved deepfake and mask/replay detection
Fixed a configuration issue in the deepfake detector and a scoring bug in mask and screen-replay detection that could let some spoof attempts pass. Both checks run on every verification, as always.
Get changelog entries in your inbox.
Email subscriptions for the status page will cover changelog updates too, once that feed is connected.
Questions
Changelog FAQ.
Keep building
See what's next in the API reference.
The reference always reflects the current behavior; this page tells you what changed to get there.