riskified decision stuck in review after order created
Handles a Riskified order decision that stays in review after the order is created. Covers review timelines, order-data completeness, the decision webhook, and holding fulfillment until approval. Not for declined decisions, and not for orders never submitted to Riskified.
TL;DR
Review takes time and needs complete order data, so first confirm the order was submitted with full customer and payment details. Do not fulfill until the decision webhook arrives; use the webhook rather than polling. If the review exceeds the expected window, check the order data for gaps and contact Riskified with the order id.
riskified decision stuck in review after order createdUse this when
- An order sits in review longer than expected.
- The decision webhook never arrived.
- You need to decide whether to ship an order under review.
Not for this skill when
- The decision came back declined. Handle the decline, not the wait.
- The order was never submitted to Riskified. Submit it first.
- You want instant decisions. Review is part of the product.
Steps
- Confirm the order was submitted via the checkout or order API with full details: customer, payment, and line items. Verify: the Riskified dashboard shows the order with complete data.
- Check the decision webhook endpoint for delivery failures. Verify: recent deliveries show 2xx responses.
- Put the order on hold in your fulfillment system until the decision arrives. Verify: the order cannot ship while in review.
- If the review exceeds the normal window, look for data gaps like missing AVS or device data and resubmit if needed. Verify: the order record is complete.
- Contact Riskified support with the order id if it remains stuck. Verify: you have the order id and submission timestamp ready.
Variant phrasings
riskified order stuck in manual review
Manual-review phrasing.
riskified review taking too long
Timeline phrasing.
riskified decision pending after checkout
Checkout-focused phrasing.
Compatibility: Riskified order submission and decision webhook. Review timelines vary by order risk and data completeness.
Why it happens
Riskified reviews the riskiest orders manually, and manual review needs complete data. Thin orders with missing customer or device details take longer because analysts have less to work with. Polling does not speed it up; complete data does.
Edge cases / pitfalls
- Shipping during review voids the guarantee. The hold must be enforced in the fulfillment system, not just in policy docs.
- Webhook signing or URL changes silently break decision delivery. Verify the endpoint after any deploy.
- Resubmitting the same order can create duplicates. Update the existing order instead of creating a new one.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_BLXM5lyu7bqIYJi69xQ6Pg