Riskified, founded in Israel in 2013, sells chargeback liability shift rather than fraud tooling alone, letting merchants tune approval strategy to their risk tolerance while guaranteed fraud chargebacks are absorbed by the provider, alongside account takeover protection and checkout failure remediation.
Provider
1 resultsArticle
3 resultsChargeback Playbook: Match Evidence to Reason Codes and Win More Disputes
Knowing the chargeback process is easy; submitting the right documents before the deadline is not. This playbook breaks down reason codes by dispute type, gives an evidence checklist you can reuse, and explains how Visa and Mastercard prevention tools plus 3DS liability shift change the maths.
3D Secure 2 in Practice: Flows, Exemptions, and Liability Shift
3D Secure 2 is not a switch where turning it on makes you safe and turning it off saves money. It is a mechanism you keep tuning between chargeback liability and conversion rate. This article covers how 3DS1 and 3DS2 differ, the frictionless and challenge flows, the four conditions that make liability shift valid, PSD2 SCA requirements and common exemption types, when to trigger and when to exempt, hosted versus self-built 3DS Server integration, the two-sided effect on success rate and chargebacks, and a tuning checklist.
Layering 3DS, Risk and Chargebacks: Get the Order Wrong and All Three Underperform
Many teams treat 3DS, risk rules and chargeback handling as three things to optimise separately, and the metrics get worse the harder they optimise - because they are three stages of one decision chain. Get the order or the decision rights wrong and tuning any one layer pushes the other two the wrong way. This article covers the division of work, the correct sequence, the real preconditions for liability shift, and how to derive the combination from chargeback structure.