How a pilot runs. Proof on your own data, before you commit.
Every DeepID engagement follows the same four steps, from trying it on your own number to live decisions on one journey. Each step ends with results you can check, and nothing acts on a customer until the last.
Four steps, each with a result you can check.
The retrospective is free. Terms for the shadow proof are agreed in writing before it starts.
| Step | What happens | Scope | What you get |
|---|---|---|---|
| 1. Try itBefore any contract | We set up a short session with you on your own number. You sign in on your own phone, on your own carrier, and see which check confirms it. Your engineers can have sandbox access to wire one moment end to end. | Your own number, then the sandbox | A session on your own phone, and sandbox access for your engineers |
| 2. RetrospectiveFree | DeepID reads your own transactions and closed cases and shows the payee and mule links it would have seen at the time. | 30 to 90 days of your history | Findings presented to your team |
| 3. Shadow proof6 to 8 weeks | The SDK runs on one journey and scores it without acting, so completion, login success, codes sent and fraud caught are measured on your own customers. | Live traffic, no action taken | Results reviewed against the criteria you signed |
| 4. Limited production8 to 12 weeks | Live decisions on the first journey, such as sign-up, login or a new payee, with a rollout plan, then the next moment. | Live decisions on one journey | Live results and a rollout plan |
Success is agreed before the proof starts.
Both sides know what a good result looks like before anything runs. We publish no figures for these: they are measured on your own traffic, against what you see today.
- Detection lift
- The fraud DeepID found that your existing controls missed.
- False-positive change
- Genuine customers flagged, before and after.
- Review-queue impact
- The effect on your analysts’ workload.
- Latency
- Response time inside the journey.
Onboarding and login teams measure on the same terms: completion at sign-up, login success, codes sent and fraud caught.
Where each industry starts.
Each one begins with a free analysis on your own data, the same one its industry page describes: what it looks at, and what it shows.
| Industry | The journey most at risk | The first analysis | What it shows |
|---|---|---|---|
| Banks | A new payee followed by a first payment | A free retrospective on 30 to 90 days of your payments and closed scam cases. | The payees your confirmed cases paid into, the mule links between them, and which were still active on the last day of the period. |
| Digital banks | Remote sign-up, then the first device change | A deepfake and injection test on your own onboarding flow, run as a shadow proof on live sign-ups with no action taken, because history cannot show a camera or a device. | The sessions that came through a virtual camera or an emulator, and the faces that appeared on more than one application, against the outcomes you already know. |
| Lenders | Application and disbursal | A free retrospective on 30 to 90 days of applications, disbursals and early repayment. | The defaulted loans that shared a face, device or payout account with another application, and whether that link was visible before disbursal. |
| Payments | Wallet or merchant onboarding, then the payout | A free retrospective on 30 to 90 days of wallet openings, merchant applications and payouts. | The wallets and merchants linked by a face, a device or a settlement account, and the value that passed through them before each was offboarded. |
| Insurance | A claim backed by photo or video evidence | A free retrospective on a sample of closed claims, with their media, devices and payout accounts. | The paid claims that shared a device, a repairer or a payout account with another claim, and the documents that carried edits. |
| Capital markets | The first transfer from a new investor | A free retrospective on 30 to 90 days of account openings, funding and withdrawals. | The accounts that shared a face, a device or a funding account, and the withdrawals that left through accounts already carrying those links. |
Who you deal with.
One agreement and one team, from the first call to the rollout plan.
One agreement.
Customers deal only with DeepID, from the first call to the contract, billing and the product.
One team.
The regional team for India, APAC or the Gulf runs the pilot with your fraud, security and engineering leads, from the first call to the rollout plan.
Settled in writing first.
Hosting, data residency, retention and sandbox access are agreed with your security team before the pilot starts.
What you can hold us to.
Four commitments we make to you.
Proof before you commit.
A retrospective and a shadow proof on your own data come first.
Reasons with every decision.
No score reaches your team without the signals behind it.
Evidence on request.
Any figure we quote comes with its method, its dataset and its date.
Compliance supported, never guaranteed.
DeepID supports your compliance with named rules and does not claim regulator approval.
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.