Account takeover
Spot the takeover before the money moves.
Logins, password resets and contact changes are kept as one session. Kairos decides the risky moment, such as a new payee or a payout, with the whole session in view.
- +0:00login
- +1:37password_reset
- +2:14email_changed
- +3:51payee_added
Review
- takeover_signs0.94
- new_device0.81
- details_pasted0.62
Events you send
- login
- password_reset
- email_changed
- payee_added
Example signals
Signals are questions you write. Grayson answers each with a probability, and your models and policies use the answers.
- takeover_signsA new device, a password reset or a contact change came shortly before the request.
- new_deviceThe login came from a device this customer has not used.
- details_pastedPayee details were pasted, not typed, often after switching apps.
- impossible_travelThe location changed faster than the customer could travel.
What each outcome does
ApproveLet the login or change through.
Step upAsk for a second factor.
ReviewHold the change for an analyst.
BlockLock the session.
How it decides
- 1Your product sends eventsSign-ups, logins, orders, payouts and chargebacks, from the SDK, the API or webhooks.
- 2Kairos builds the contextIt links the request to its user, devices, cards and addresses, and to their history.
- 3Models and rules decideA workflow asks Grayson, scores with your model and applies your policies.
- 4You get an answerThe outcome, a risk score from 0 to 100, and the reasons, in one response.
TriggerDecides withdrawal
Ask a decision modelGrayson · 6 questions
Score with a modelLogistic regression v6
If / elseScore is 80 or more
Create a caseHold for review
ReturnThe model decides