Migrating Merchants from 3DSecure Version 1 to Version 2

One of the milestones for 2020 will be the migration of 3DSecure Authentication to Version 2. Deadlines vary for different regions but cross border business will be impacted sooner than any regional requirements. We have been supporting integrations into version 2 for the last few months and we are seeing an upsurge in integrations now that we are in 2020.

Our sandbox and integration environment is playing an important role in successful integrations.

One of the key challenges is migrating merchants from version 1 to version 2. There are two issues to consider here, one being the migration of merchant configurations and the second being the enrolling of the merchants with the schemes.

Merchant configurations for version 2 have additional fields which are not present in version 1 and these additional fields need to be provided. These additional fields are in turn used when enrolling merchants with schemes; any changes to these fields will need to be propagated back to the schemes.

We are helping our clients with these migrations, automating the process to ensure that the process is as error free and efficient as possible.

We are also happy to announce that we now have tools in place to automate the enrollment of merchants with the schemes. This has made a significant impact on simplifying the enrollment process and cutting down the time to prepare a merchant for production.

We remain committed to providing our clients with the best solution for 3DSecure Authentication, backed up with excellent support and industry experience.