The 3 Domain (3D) Secure payment protocol is designed to reduce fraud and chargebacks during e-commerce transactions, and is rapidly becoming a widespread industry standard. It is supported by most card issuers and provides an extra layer of security by authenticating the customer's identity at the point of sale. We use 3D secure protocol for cryptocurrency purchases to ensure compliance and maximum security.
3D Secure allows Mastercard and Visa card issuers to provide an extra level of protection
It authenticates the customer's identity at the point of sale.
Non-3D vs 3d
Non-3D is the regular type of charge you use when shopping at most brick-and-mortar stores and 3D charge is a newer type of charge that involves your card issuer 2FA-ing the charge request. 3D Secure charges are fast becoming industry standard and will soon be required for online payments in Europe under PSD2 regulations that take effect this year.
3D charges are more secure because of the built-in user authentication with the issuing bank. 3D charges involve a little more work integration wise (handling 3D card enrollment response and iFrame/Form setup) but we help make it simpler with our guides below. The result is a more secure transaction for both the user and merchant.
New PSD2 SCA regulations in the European Economic Area take effect 09/14/2019
Strong Customer Authentication (SCA) is a major component of the second Payment Services Directive (PSD2). The goal behind the regulations is to benefit consumers by driving payment innovation and data security.
3D Secure satisfies the requirements of SCA
3D Secure Flow
For the end-user, 3-D Secure protocol is nonintrusive and adds little friction.
User enters their payment information
The user is redirected to the card issuer's Access Control Server (ACS)
After the user is authenticatd by the ACS, the transaction is processed and the user is redirected to a confirmation screen
Implementing 3D Secure
On the next page you will find detailed instructions for integrating our credit/debit cryptocurrency purchase api, including redirecting users to their respective ACS.
For testing purposes, we also provide a 'dummy' ACS that will automatically process sandbox transactions, unless directed to throw an error.