Chargeback Label And Rescore
A 4-step recipe with Sift. We can help you get access.
Recipe · 4 steps
Chargeback Label And Rescore
with Sift
Submit a chargeback event, label the user fraudulent, rescore, and read the new score.
- Record a $chargeback event for the user so the dispute is captured on the Sift timeline.
- Apply a fraudulent label to the user for the chargeback abuse type as a training signal for Sift's models.
- Force a fresh Sift Score computation so the chargeback label is reflected in the user's risk immediately.
- Read back the recomputed score to confirm the new risk value after the label and rescore.
What you'll need to have ready
- apiKey: Sift account API key sent in event and label bodies as $api_key.
- userId: The user's unique identifier ($user_id).
- analyst: Optional analyst email recorded with the label.
- abuseType: Abuse type for the label and rescore (payment_abuse, content_abuse, account_takeover, account_abuse, promotion_abuse, legacy).
For your developer
Arazzo workflow sift-com:chargeback-label-rescore, 4 operations: sendEvent → applyLabel → rescoreUser → getScore. Specs on APIs.io.