We allow for users to take 3D Secure payments. 3DS adds an extra layer of payment protection to an online transaction. This type of security is required by Europe.
In Project Settings > Payments tab scroll down to the Payment Config header and Enable 3-D Secure Payments Protocol.
By default this should be off, unless required by merchant to process payments from users in Europe.
How does it work?
When a user makes a payment in a project using BlueSnap, they are prompted with a new window with the header titled Purchase Authentication. They are then sent a text message to their mobile device with a code to enter into the prompt.
It is not recommended that admins enable this if they do not need to because it requires extra steps for the user to process a payment. This is more so for admins that process payments from users in Europe.
For a user on the front-end making a payment on a saved payment method they may or may not be prompted again to do the 3DS prompt depending on the processor, they control what happens. The 3DS sends a text to the phone that is on file with the CC company.
When an admin makes the first payment on the backend it bypasses the 3DS check to avoid the user receiving an unexpected text message and may or may not go through.