Integration overview

Sentinel gives you a few building blocks. You choose how customers get verified, how your systems receive the outcome, and how your team operates day to day. This page maps the surfaces and shows how they fit together.

How customers get verified

Every verification runs inside a Sentinel-hosted experience, so you never handle raw biometric data. The hosted verification link is the standard way to deliver it. Your backend requests a session and receives a responsive link that you can place on a web page, send by email or SMS, present as a QR code, or open inside your own app in a web view. It adapts to any screen and is the fastest path to integrate, with no native app changes.

A fully native React Native SDK is also available as a premium option for mobile teams, by consultation.

How you receive outcomes

When a verification resolves, you learn the result in one of two complementary ways.

• Webhooks push to you: Sentinel calls your endpoint as a customer's status changes, so you react in near real time. Recommended as the primary signal for most integrations.
• Result retrieval pulls on demand: query a customer's current status and result whenever you need it. Useful for reconciliation, retries, or if you prefer to poll.

Most integrations use webhooks as the primary signal and result retrieval as a fallback and for reconciliation.

How your team operates

The operations dashboard is where your team reviews verifications, inspects results, resolves items held for review, and configures your tenant, including accepted documents, webhook settings, and re-verification policies. Roles separate staff who can act from those who can only view.

A typical integration

Putting the surfaces together, a common end-to-end integration looks like this.

Division of responsibilities

Sentinel runs the verification itself. You connect it to your product.