One SDK, and one call at each moment.
Engineering teams start in the sandbox, with one moment wired end to end, usually sign-up or login. The same SDK and the same decision cover every later moment, so each one you add is another call rather than another vendor.
What you measure
On your own traffic
- 01Time from sandbox access to the first decision
- 02Time to go live on one journey, sign-up or login
- 03Decision time inside your journey
- 04What the SDK adds to your app’s size and start-up
Agreed in writing before the pilot, against what you see today.
What you start with.
The first question we hear: “How much work is it?” Most teams start at login, with these modules.
Silent network verification
AuthenticationOne-tap login as the first integration: the routes, the token and your server’s redeem call.
One decision, with reasons
DecisionOne decision shape at every moment, back in the app and as an event stream.
Journey builder
DecisionJourneys changed without an app release.
What you add next.
The same SDK reads the next moment, so each one you add is checked against what is already bound.
Events
One call at each of the five moments.
The decision
The same decision in the app and in your FRM.
Security
Hosting and residency, agreed first.
Three things to know.
- One SDK for Android, iOS, React Native, Flutter and web, and one call at each key event.
- Decisions come back in the app and as an event stream to your systems.
- A sandbox before any contract.
Pages to read first.
Where to go next, in the order most engineering teams read them, then the teams who sign off with you.
See DeepID on a real phone.
We show your fraud, security and engineering leads how DeepID would run your sign-up, login or payment journey, then plan a pilot on your own traffic.