.

3DS Fact Sheet

What is 3DS?

3DS is an additional layer of security and fraud protection for card payments.  

3DS means that the card issuer (the bank who issued the card) may require the card holder to enter a code when making a payment.  The card issuer determines whether the card holder is challenged to enter a 3DS code based on various fraud control algorithms.  If challenged, a code is sent to cardholders mobile, and must be entered by customer for payment to be processed.  Once the card has been verified, payment is authorised and the transaction is completed.

3DS is applicable on all customer payment pages that are hosted by TravelPay (the URL will start with pay.travelpay.com.au) and if your software utilises the TravelPay payment plugin.  This includes TravelPay’s integrations with VTO, PowerSuite, EventsAir, Lemax and Odysseus.

Remember that not all credit cards are 3DS enabled, and this is at the discretion of the credit card issuer.

Benefits to Merchant

  • Reduced chargebacks
  • No cost or effort to implement.
  • 3DS provides additional layer of security.
  • Greatly reduces fraudulent transactions.

Benefits to Cardholders

  • Enhances card security.
  • Increases customer confidence when processing payments.
  • Easy to use.
  • Reduces unauthorised transactions.

How does it work?

3DS is triggered in the transaction process. See the below flow of how this will look:

Here is an example of 3DS being triggered from ANZ, click to see full-sized image.

3DS screenshot

FAQs 

  1. Who triggers the 3DS process?
    3D Secure is triggered by the card issuer in order to provide extra protection against unauthorised use of a card. Remember that not all credit cards are 3DS enabled, and this is at the discretion of the credit card issuer.
  1. What happens if my customer doesn’t receive an SMS?
    They will need to contact their card issuer to ensure that their contact details are correct for 3D Secure. Some Banks have not implemented 3D Secure.

  2. What if the cardholder does not get a code?
    The 3DS ‘enter your code’ fields will automatically appear when 3DS is supported and it is presented by the bank that issues the customer’s card. The bank’s fraud algorithm decides whether to 3DS challenge the cardholder or not.

  3. Is 3DS available with all card types?
    3DS is available for Mastercard, Visa and American Express cards but whether it is configured for all cards, and whether a code is required, is at the discretion of the card issuer.
  1. Why do some transactions require 3DS and some don’t?
    The card issuer determines whether the card holder is challenged to enter a 3DS code based on various fraud control algorithms. TravelPay does not determine whether the card holder is 3DS challenged, does not determine whether the code entered is correctly, and does not decide whether the transaction is approved. 
  1. What if a customer advises that they don’t want to have to enter a code and would prefer you to process their payment instead? eg. over the phone
    Under no circumstances should you process credit card payments over the phone without sighting the credit card.

  2. How does a cardholder know if they have 3D Secure?
    A cardholder will have to contact their card issuer if they wish to verify that their card requires 3D Secure.

  3. Will the same code be used every time?
    No – verification codes are one-time only. The card issuing bank will send you a new one each time.

  4. What if the code doesn’t work or the correct code was entered but the transaction was still declined?
    Customers should contact their card issuer to determine the reason the payment was declined.

  5. What payment pages and software integrations have 3DS available?
    3DS is available:
    • on all customer payment pages that are hosted by TravelPay – the URL will contain ‘pay.travelpay.com.au’; and
    • if your software utilises the TravelPay Payment Plugin integration – this includes VTO, PowerSuite, EventsAir, Lemax and Odysseus.

  6. What payment pages and software integrations do not have 3DS available?
    Integrations that utilise card APIs do not currently support 3DS – this includes the Tramada ‘Pay Now’ invoice customer payment integration.

    3DS is also not available on payment pages that are designed for travel agents to use.

    To ensure 3DS is available, use a payment page that is hosted by TravelPay – the URL will contain ‘pay.travelpay.com.au’. 
  1. Are there other names for 3DS?

    3D Secure is also known as Verified by Visa, Mastercard SecureCode and American Express SafeKey. 

Linkedin

© 2023 All Rights Reserved

Zenpay Pty Ltd. © 2023 ABN 63 056 881 942 PCI