Transaction Score And Decide
A 4-step recipe with Sift. We can help you get access.
Recipe · 4 steps
Transaction Score And Decide
with Sift
Submit a transaction event, evaluate the score, and block or hold for review.
- Submit a $transaction event with return_score=true so Sift scores the payment synchronously for payment abuse.
- Read back the latest payment abuse score for the user so the workflow branches on a stable numeric value.
- Hard-block the user with the configured decision when the payment abuse score is at or above the block threshold.
- Hold the session for review with the configured decision when the score is borderline but below the hard-block threshold.
What you'll need to have ready
- apiKey: Sift account API key sent in the event body as $api_key.
- accountId: The Sift account identifier for the Decisions API path.
- userId: The payer's unique identifier ($user_id).
- sessionId: The session identifier used for the hold-for-review decision.
- ip: Optional originating IP address for the transaction.
- abuseTypes: Comma-separated abuse types to score the transaction on.
- blockThreshold: Payment-abuse score (0-100) at or above which the user is hard-blocked.
- reviewThreshold: Payment-abuse score (0-100) at or above which the session is held for review.
- blockUserDecisionId: Decision id applied to the user on a hard block.
- reviewSessionDecisionId: Decision id applied to the session on a hold-for-review.
For your developer
Arazzo workflow sift-com:transaction-score-decision, 4 operations: sendEvent → getScore → applyUserDecision → applySessionDecision. Specs on APIs.io.