3D Secure authentication

To protect against fraud, customers will need to use a Strong Customer Authentication (SCA) called 3D Secure (3DS) authentication for some transactions.

In Europe, 3DS authentication is required for ecommerce payments by law under PSD2 (Payment Services Directive 2). In many other parts of the world, there are similar requirements.

By default, 3DS authentication is not required for phone payments. But when customers make an initial payment by phone and store a card for future payments, they must undergo a 3DS challenge authentication for their initial payment.

The 3DS authentication method depends on the issuing bank. The bank can require the user to enter a password, or a code, which can received by SMS or from a separate authentication app, or to supply a fingerprint, or use a dongle, and so on.

3D Authentication may fail for many reasons. For example, the code may expire, the customer may not understand the 3DS process, or they may not want to provide their one-time transaction code over the phone.

BillPro always requires 3DS for ecommerce payments with payment links or using the virtual terminal. But for phone payments, it does not require 3DS by default.

To save card details for future use, you must use 3DS, so you can select the 3DS Required option. If a payment is declined because Strong Customer Authentication is required, you can select the 3DS Required option, and retry the payment, or send a payment link. BillPro always processes transactions with 3DS authentication in the ecommerce channel.

To display the results of the 3DS verification process, in the order summary, go to the Related Transactions, click on the TRANSACTION UNIQUE ID and open the Transaction Details pop-up. For more details about the Transaction Details pop-up, see Display related transactions for an order.