Verification built once, called by everything.
Document checking, liveness and ongoing expiry monitoring, delivered as a shared service across APAC and Europe — accepting credentials from any country a partner product opens in.
Every border, a different document.
Identity documents vary enormously between countries — their formats, their security features, and the liveness signals that count as sufficient proof. Verification is also close to the worst place in a product to economise, because a weak check is more dangerous than no check at all: it manufactures confidence without providing grounds for it.
Maintaining classifiers internally means retraining and reconfiguring each time an unfamiliar format appears, which turns every market launch into a machine learning project. What was wanted instead was a verification and document layer that other products could simply call, containing no per-country engineering anywhere inside it.
Delegate the detection. Own the lifecycle.
Detection was handed to a vendor maintaining document templates and liveness models across more than two hundred countries, surfaced through a capture SDK that presents its prompts in whichever language the user is in. That problem belongs to whoever works on it full time.
What was built internally is the portion that is genuinely specific to the product and would never have come off a shelf: encrypted, region-segmented document storage; expiry tracking driven by structured dates rather than scraped text; and the workflows that re-check a credential when it lapses. None of that shifts according to which authority issued the document.
Compliance as a capability, not a rebuild.
Scheduled scans and background workers watch expiry dates and open re-verification without anyone having to remember. Every access to a stored document lands in an immutable audit trail that holds up to regulators in each market the platform serves.
Retention follows a strictest-common-denominator rule, with erasure rights honoured globally rather than only where they are mandated. That proved both simpler to operate and safer than maintaining a separate policy per jurisdiction. Partner products integrate against one API rather than each assembling verification of their own.
The only pieces worth owning are the ones that never vary: where a document rests, when it lapses, and what happens the moment it does.
Project record
- Client
- Withheld under NDA
- Sector
- Identity / compliance
- Regions
- APAC · Europe
- Engagement
- Full build · shared service
- Consumers
- Wallet and mobility products
- Integration
- API + native capture SDK
Confidential · anonymised
- React Native
- NestJS
- FastAPI
- Encrypted object storage
- Event workers
- Audit logging
What shipped.
The properties the system holds today, rather than the ambitions it started with.
- Vendor-delegated document and liveness checks across 200+ countries
- Encrypted storage held in region-pinned buckets
- Automated expiry scanning and re-verification workflows
- Every document access recorded in a tamper-evident trail
- Erasure rights applied globally as the baseline
- A single API consumed by multiple partner products
Other systems we have built.
Every client is under NDA. What we publish is the shape of the problem and how it was solved.
Have a system like this on your hands?
Tell us what you're trying to ship. We'll tell you honestly whether we're the right team for it — and what it would take.
Prefer email? info@triyant.sg
We reply within one business day. Your details are used only to respond to this enquiry and are never shared with third parties.