I have been showen the Ingenico Config Mrg. In this tool, it is possible to set rules around how we apply 3DSecure on transactions. Dynamic 3D Secure allows you to define transaction criteria, in rules, for which you want 3D Secure flow to be activated. We don't use this tool today as we have 3D Secure flow skipped by using flags (skip authentication) in the API. I'm trying to see if we invest in building some sophistication around setting rules in this tool for applying 3DS, what the implications are in removing the skip authentication logic completely and allowing the rules to drive how we apply 3DSecure. The benefits of using Dynamic 3DS in the config manager would be to hone how we apply 3Dsecure by market, amount and bin and hopefully end up with higher approval rates/more income on card transactions as a result.

If we were to use this tool, the first step in activating this feature is to define the criteria in rules for transactions for which we want 3D Secure to be activated and would be drawn from a) what we know about bins/issuers that like to see 3DS b) markets where we know 3DS is prevalent and c) set amount thresholds so we only perform 3DS where the cost of performing it doesn't exceed the benefit.

Once you have defined the rules, turn Dynamic 3D Secure toggle on. If a transaction meets the criteria of an active rule, the 3D Secure flow gets activated for that transaction. By default Dynamic 3D Secure is turned off, meaning that any card product enabled for 3D Secure on the platform, will have the 3D Secure flow on all transactions (unless you have defined logic in your API). So.... can FR Tech tell me what the implications would be to turn off the skip authentication logic before I invest energy into coming up with a baseline rule set that I would test out and hopefully bring live once vetted.