Payments gateways can initially have decision manager processes, but they're not always efficient. Riskified acts as a second step of verification — that's usually why it's implemented. We just do a couple of initial sessions between our payment gateway platform, our solution, the clients, and Riskified. We define what type of verification will be required, what type of payment methods will need to go through the Riskified process. For example, for us, it was mainly for PayPal and Credit cards (Visa, MasterCard, Amex). They have other payment methods methods that can also be implemented but overall, we define what type of mapping will be used for each order lifecycle key stage. When you have one order, you can send it once or multiple times to Riskified, depending on the Business/order lifecycle. For the first checkup, if you update the order, the question is, do you still want to send it to Riskified? What if you cancel the order? It all comes down to the business, and what the client needs. We define the business scope, the flow, and according to that, and based on that, Riskified provided us the mapping that they need for each trigger in the life cycle.
