Behind its minimalist API, Ding acts as a real-time broker and selects the optimal based on your user’s context and history. It also prevents fraud transparently, without requiring any additional configuration.
When you send an OTP code, Ding starts an authentication lifecycle. Here’s how it works:
Start an authentication
Your user enters their phone number in your application and you send it to us.
We analyze the request and check for fraud using our existing database and the Signals you provided.
If the authentication is suspicious, we don’t send any code.
Send a code
Ding compares all of the available and send a code using the best one.
If the user didn’t receive the code, you can retry the authentication by calling the Retry endpoint. Ding then switch to another route to increase the chances of the user receiving the code.
Verify the code
The user receives the code and enters it in your application.
You then send it to the Check endpoint.
If it’s correct, the endpoint returns a
valid status code.
Once an authentication lifecycle has begun, you can inspect it in the dashboard by looking at the Authentications tab or by by searching for it using the search modal.
Ding partners with many to guarantee the highest possible delivery rate at the lowest possible cost. We also use multiple to reach your users and our routing engine continuously optimize the delivery based on your user’s context and history.
At the heart of Ding’s fraud prevention system is a powerful machine learning model that assesses the risk level of each authentication in a few milliseconds. It uses dozens of signals relating to each authentication and draws on data from our vast database to predict whether a request is likely to be fraudulent.
Ding’s system is flexible and responsive, continually learning from new patterns and incorporating your feedback when users are flagged as returning.
Build a fully-functional SMS OTP flow in your application by following the steps below.