Example story: holding a coached payment before it leaves
Example story, replace before launch. The same layout for a fraud story: the payment journey, the signals read in the session, and the decision with its reasons.
In this story
Example story, replace before launchThis page shows how a customer story is laid out. The customer, the journey and every detail are placeholders: DeepID names customers only with their agreement, and publishes results only when they are measured on the customer’s own traffic.
At a glance
| Customer | Example customer (placeholder) |
|---|---|
| Kind of business | Payment aggregator |
| Market | India |
| Journey | New payee, payment |
| Modules | Scam signals, Device intelligence, Payee and mule graph |
The starting point
Replace this with the customer’s own account of the problem, in their words and with their agreement: the journey, what their existing checks saw, and why it mattered to them.
What changed in the journey
Replace this with what DeepID read at each moment, and the actions the customer’s policy chose. Keep to the modules on the platform page.
How it was measured
Replace this with the criteria agreed in writing before the pilot, the period and the method. Publish a figure only with its method, its dataset and its date.