Payouts and withdrawals
Hold the risky payout. Release the rest at once.
Withdrawals, transfers and push payments are where fraud turns into loss. Kairos decides each one with the account's history, its payees and the session that came before it.
- +0:00login
- +1:37payee_added
- +2:14limit_raised
- +3:51withdrawal_requested
Review
- new_payee0.94
- unusual_amount0.81
- funds_gathered_first0.62
Events you send
- login
- payee_added
- limit_raised
- withdrawal_requested
Example signals
Signals are questions you write. Grayson answers each with a probability, and your models and policies use the answers.
- new_payeeThe payee was added recently, in this visit or in the last few weeks.
- unusual_amountThe amount is far above what the customer usually sends.
- funds_gathered_firstMoney was moved in from other accounts shortly before the payout.
- warning_overriddenThe customer went past a scam warning in a way that does not fit the payment.
What each outcome does
ApproveSend the payout.
Step upConfirm with the customer.
ReviewHold for an analyst.
BlockStop the payout.
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