A record of what was decided, and why.
Compliance teams start with the record: every decision logged with its reasons and the message the customer saw, every face check signed and replayable, and every policy versioned. Each control maps to a dated rule, market by market.
What you measure
On your own traffic
- 01Decisions logged with their reasons and the message shown
- 02Time to answer a disputed transaction with its record
- 03Rules mapped to a control, market by market
- 04Policy changes, and when each one applied
Agreed in writing before the pilot, against what you see today.
What you start with.
The first question we hear: “Can we show a regulator what we did and why?” Most teams start at the payment, with these modules.
One decision, with reasons
DecisionReason codes on every decision, logged with the message shown to the customer.
Journey builder
DecisionPolicies and thresholds versioned per market, so you can show what applied and when.
Liveness and face match
VerificationA signed record of every face check, replayable for audit.
What you add next.
The same SDK reads the next moment, so each one you add is checked against what is already bound.
The rule map
Seven markets, dated and sourced.
RBI’s 2027 liability framework
What changes on 1 January 2027.
Silent network verification
Beyond SMS codes, as each market’s rule says.
Three things to know.
- Each control maps to the rule it supports, market by market.
- Every decision is logged with its reasons and the customer message shown.
- DeepID supports compliance and never guarantees it.
Pages to read first.
Where to go next, in the order most compliance teams read them, then the teams who sign off with you.
Start with what your history can show.
A free retrospective on 30 to 90 days of your own transactions shows the payee and mule links in them. Session signals follow in a shadow proof, once the SDK runs.