How do the default dynamic 3D secure rules work?

3D Secure rules can be set to either one of these: 

If the Rule is set to ALWAYS

Adyen will actively trigger 3DS on every transaction as long as the MID is enrolled for 3DS, the necessary information is passed in the API call (i.e browserInfo and userAgent) and the Issuer supports 3DS

If the Rule is set to PREFER NO

Adyen will not actively trigger 3DS on every transaction unless the Issuer mandates 3DS authentication for a successful authorization

 

You can set these up in the Customer Area > Risk > 3D Secure.

Was this article helpful?
0 out of 0 found this helpful