Improved handling of non-native English characters in authentication requests

Since August 12, Visa updated their 3D Secure authentication data requirements. We now recommend sending the following fields in any payment where you set 3ds.enabled to true, in addition to any data you already supply:

• IP address
• Email address
• Cardholder name
• Phone number (home, mobile, or work, including the country code)

Note: The API fields you’ll need to send will differ depending on whether you use our Integrated or Standalone solutions. See our 3D Secure documentation for more information.

To support these requirements, Visa has improved their handling of non-native English and other character types (such as emojis, non-Latin scripts, etc.) in the cardholder name field.

If cardholders supply one of these values, Visa’s Directory Server will no longer reject the transaction. Instead, they’ll send the authentication request to the issuer without the cardholder name, so you can supply this recommended data regardless of which market you’re in.

If you’d like more information on optimizing 3D Secure requests, or are interested in using our Standalone solution for more control of the authentication experience, please contact your Account Manager or raise a webform request and we’ll be happy to assist.