|
|
|
|
| The case for 3DSecure |
3DSecure allows a card holder to authenticate himself while making an online payment. It allows 3 domains to work elegantly together.
Domain 1: The card holder has the peace of mind that his card is not used without his authorization.
Domain 2: Merchants are protected from fraud and can provide the product and service without delay or extra costs.
Domain 3: Banks see that the transaction has been authenticated and are more likely to approve the transaction, to the convenience of the card holder.
|
| Background |
In a traditional credit card transaction, a payment request is presented to the issuing bank for authorization. The Issuing bank authorizes the transaction based solely on the funds available to the card holder.
With card present, the magnetic strip on the card can be read and a signature collected. This process has now been largely superseded by Chip and PIN which gives the card holder the opportunity to identify himself via a secret PIN code.
An Ecommerce transaction is conducted online, without the possibility to access the card physically. Un-authorized usage and fraud are therefore more likely.
This is bad for the card holder who risks having his card number stolen and his funds blocked. It is bad for the merchant who has to carry the ultimate responsibility of theft. It is bad for the banks who have to expand considerable resources handling the litigation between card holder and merchant, a process known as chargeback.
The risk has been partially mitigated with the addition of an extra 3 digit security number referred to as CVV/CVC; this number was introduced because a decade ago it was common to print the card number on every purchase receipt and this security number can never be printed or stored and has become mandatory for ecommerce.
3DSecure allows transactions to be conducted in safety online, greatly reducing the risk of fraud and chargebacks.
|
| Verified by Visa |
The implementation of 3D Secure by Visa is called Verified by Visa.
|
| MasterCard Secure Code |
The implementation of 3D Secure by MasterCard is called Secure Code.
|
| Amex SafeKey |
The implementation of 3D Secure by Amex is called SafeKey.
|
| JCB J/Secure |
The implementation of 3D Secure by JCB is called J/Secure.
|
| How it works |
When a payment request arrives at the merchant or payment gateway, the Merchant Plug In (MPI) component is activated. The MPI talks to Visa or MasterCard to check if the card is enrolled for 3DSecure. If the card is not enrolled, this means that either the bank that issued the card is not yet supporting 3DSecure or it means that the card holder has not yet been registered for the service.
If the card is enrolled, the MPI will redirect the card holder to the 3DSecure authentication web page for the issuing bank; the card holder will then identify himself. The MPI will evaluate the reply from the bank and, if successful, allow the transaction to proceed for authorization. The transaction could still fail for lack of funds or other reasons but is more likely to be approved because of the authentication.
|
|
