Screen Order And Transaction
A 3-step recipe with Sift. We can help you get access.
Recipe · 3 steps
Screen Order And Transaction
with Sift
Submit a create-order event, evaluate the payment-abuse score, and decision risky orders.
- Submit a $create_order event for the user with return_score=true so Sift scores the purchase synchronously for payment abuse.
- Read back the latest cached payment abuse score for the user so the workflow branches on a stable numeric value.
- Apply the configured block decision to the order entity when the payment abuse score crossed the 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 buyer's unique identifier ($user_id).
- orderId: The order identifier used in the order-decision path.
- sessionId: Optional session identifier for the checkout.
- ip: Optional originating IP address for the order.
- abuseTypes: Comma-separated abuse types to score and decision on.
- scoreThreshold: Payment-abuse score (0-100) at or above which the order is blocked.
- blockOrderDecisionId: Decision id to apply to a risky order (configured in the Sift Console).
For your developer
Arazzo workflow sift-com:screen-order-transaction, 3 operations: sendEvent → getScore → applyOrderDecision. Specs on APIs.io.