One decision id, three places
Every DeepID decision carries one id: the same in the app that acts on it, in the event your FRM receives and in the decision log an auditor reads. Here is why, and how it is wired.
How the SDK, the decision and the events behind it are built, written by DeepID’s engineers for the engineers who wire them up.
1 article, newest first.
Every DeepID decision carries one id: the same in the app that acts on it, in the event your FRM receives and in the decision log an auditor reads. Here is why, and how it is wired.
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.