How Riskified differs from a typical fraud check
Most merchants run their own internal fraud rules and eat the chargeback losses themselves. Riskified flips this around: the merchant sends every order to Riskified for a decision, and Riskified pays the chargeback if any approved order turns out to be fraud. Because false approvals cost Riskified money directly, it has a strong incentive to be aggressive on borderline cases.
In practice, that means Riskified-protected merchants decline orders at the slightest pattern anomaly: a residential IP in one state with a billing address in another, a freshly-created account, or a payment instrument with no history on the Riskified network. Real customers get caught by this regularly, which is why "my order was declined" support tickets are so common at Riskified-merchant sites.
When scrapers encounter Riskified
Same answer as Forter: pure data extraction is unaffected, but anything that automates checkout is in scope. Common scenarios:
- Sneaker / streetwear limited-drop automation
- Concert and sports ticket purchasing
- Limited electronics releases (consoles, GPUs)
- Luxury goods resale flipping
The failure looks the same as Forter: a silent decline at the payment step with a "please try again" message.
What works against Riskified
What helps here is operational, not technical. Aged accounts with organic activity (orders, returns, browsing) score higher than fresh accounts, no matter how clean the fingerprint. Billing and shipping addresses must match the IP geolocation. Payment instruments with a clean history at any Riskified-network merchant carry that good reputation over. The single biggest signal Riskified uses is the network effect: a card or device that was declined at one Riskified merchant gets a worse score at every other Riskified merchant, so burning an identity is permanent.