A demo has one happy path. Production has expired documents, bad lighting, a country you had not planned for, and an agent on the phone with a customer who needs an answer now.
The integration is designed around that gap rather than around the demo.
One API, not a second integration
Document verification, biometrics and open-source intelligence share the same base URL, the same bearer token and the same JSON shape. Adding a capability means calling another endpoint group, not starting a new project.
- REST over HTTPS, with the same authentication everywhere.
- Synchronous answers for the checks that are fast, callbacks for the ones that are not.
- Every response carries the identifier you will use to find it again in the audit record.
It runs where your systems already run
Thin clients, virtual desktops and bespoke core systems are the normal case, not the exception. Deployment is built to sit beside what you have rather than ask you to replace it.
If the workflow requires new hardware at every counter, it is not an integration. It is a migration wearing one.
The report is the contract
What comes back is not a boolean. It is the outcome, the confidence, the checks that ran and the ones that could not, so your own rules can decide what a borderline case means for your risk appetite.
Two institutions reading the same report will reasonably draw different lines. The report exists to let them, instead of hiding the decision inside our threshold.
What we expect from you
A test environment, a list of the document types and countries you actually see, and someone who can say what your operations team does today when a check comes back uncertain. That last one shapes the integration more than anything technical.