To prevent any risk rules from triggering for a certain transaction, you can set the riskdata.skipRisk parameter to true in the additionalData object of a payment request.
When you skip risk, the transaction will not be given a risk score, but the transaction will still be processed.
Any shopper attributes related to the transaction, for example shopperEmail, will still be included in the ShopperDNA. Any future payments that contain the same shopper attributes will trigger the relevant risk rules.
Example payment requests
To skip risk for a single transaction, set riskdata.skipRisk to true in the additionalData object in the payment request for that transaction.
The parameter riskdata.skipRisk is case-sensitive.
Select which endpoint you use to send in payment requests: