This article is specific for clients that ChargeAutomation is facilitating the 3D Secure transactions for. If you are unsure if you fall in this category, please contact support.
One of the requirements for seamless 3D Secure transactions is the collection of merchant details. In this article, we will explore the reasons behind ChargeAutomation's request for merchant details and how it contributes to a more secure and reliable payment experience.
The Importance of 3D Secure:
3D Secure is an additional layer of security that adds an extra authentication step for online credit card transactions. It helps protect both merchants and customers from fraudulent activities by verifying the cardholder's identity during the payment process. By implementing 3D Secure, merchants can significantly reduce the risk of chargebacks and fraudulent transactions.
3DS authentication is an activity initiated by the merchant. Just like processing a card payment, an organization must be registered with an acquirer as a "merchant" to carry out these actions.
Why Does ChargeAutomation Request Merchant Details?
ChargeAutomation's request for merchant details is a crucial step in facilitating 3D Secure transactions. Here are the key reasons behind this requirement:
Verification and Authentication:
Some banks verify the merchant information of the charge request with the merchant information of the 3DS authentication. Using the same merchant information for both charge and 3DS authentication requests will reduce the risk of a failed charge.
Compliance with 3D Secure Protocols:
The 3D Secure protocols, such as Verified by Visa, Mastercard SecureCode, and American Express SafeKey, require specific merchant information to function effectively. These details are collected and transmitted to the appropriate 3D Secure service providers, enabling seamless authentication processes and reducing the risk of unauthorized transactions.
The 3DS challenge displayed to customers shows the name of the merchant performing the authentication. If you provide us with your merchant information, the name displayed will be your own.
Required Fields Explanation:
Merchant Display Name: Official merchant name with Acquirer
Merchant Website Base URL: URL that was provided during registration with the payment processor or acquirer (for 3DS merchant account) or the website url where the property is listed for booking.
Acquirer Name: Name of your acquirer
For the different card types, please only provide the fields for the card types you wish to process 3DS authentication for