Apply Minfraud and velocity filters, apply scores to different codes for AVS and CVV results, and make the usual decision whether to immediately capture or to leave for manual settlement.
For AVS and CVV, we could either
- change to a two step process, normalizing Adyen-specific result codes and then assigning scores to normalized results in a gateway-agnostic way, or
- maintain the existing mapping of Adyen-specific result codes to scores.
In any case, SmashPig should return something normalized with the createPayment result.
As for Minfraud, we could continue applying it up in the DonationInterface layer since it requires a lot of browser data, or we could pass that stuff along with the createPayment result.