Before the launch of Maxpay's own 3Ds server, merchants had the option to use acquirer's or external 3Ds servers to process 3D secure transactions. However, this way no specific information was provided in regards to 3Ds rejections, making the communication with the customers less effective.
Maxpay's 3Ds server can provide a more detailed insight into the process of 3Ds procedure for clients: from general information on the flow to possible errors and advice for clients.
In your Mportal you will now be able to see new fields that will provide additional information about 3Ds procedure. You can filter out the transactions that go through Maxpay's 3Ds server by choosing the filter 3D Auth Source - Maxpay 3D in the Transactions report.
In the available columns you can find the section 3DS Data Information and select the fields you would like to see in your report
Let's go over what each field represents:
3DS status - the outcome of the 3Ds procedure. Can be Success or Declined.
ECI - Electronic Commerce Indicator, a value returned by Directory Servers (Visa and Mastercard) indicating the outcome of authentication requested on transactions for EMV®3-D Secure. You can find out more about the possible values in our documentation.
Message version - version of the 3Ds protocol. The current value is 2.1.0
Cardholder info - contains useful information for clients in case of decline, i.e the reason for the rejection, as well as the issuer's contact information.
3DS status reason - the reason for the failed 3Ds procedure, if applicable. Can also contain some additional information on the successful 3Ds authentication, i.e. level of confidence.
Using these fields will allow you to better manage 3Ds rejections and provide accurate and useful information to your clients in case they run into any problems.