You can learn more about the SCA background here, but it's designed to improve payment security and reduce your customer's vulnerability to fraud. 

This article explains how SCA might affect the way your customers make payments.


Changes to payment processes

Each of our supported payment gateways (Stripe, PayPal and Worldpay) has taken different approaches to implement the SCA requirements.

Below is how the new requirements may affect payments on each payment gateway.

Stripe

  • Customers may also be asked to enter the postcode/zipcode registered to their card. 

  • Previously saved card details will need to be re-entered and not be saved for future transactions. The previous "Remember Me" feature - where the customer could pay using a code sent to their mobile phone - is no longer available as it doesn't meet SCA rules.

  • Some customers may also be required to complete an additional security check with their bank to complete the transaction (sometimes referred to as 3D Secure or 3DS).

PayPal

  • Checkout remains the same, but customers may be required to complete an additional security check with their bank to complete the transaction (sometimes referred to as 3D Secure or 3DS).

Worldpay

  • Checkout remains the same, but customers may be required to complete an additional security check with their bank to complete the transaction (sometimes referred to as 3D Secure or 3DS).


How will this affect my customers?

Transactions that require additional information or security checks should be in the minority. Many customers won't experience a change or will only be asked for further details occasionally. 

Those subject to additional SCA requirements will mean providing a little more information, as explained in the section above. There is always a small chance a transaction might fail or be blocked with the requirement for extra details. Either because:

  • A customer enters incorrect information. For example, they added the wrong postcode/zipcode for their card.

  • A customer doesn't successfully validate their transaction using their bank's 3D Secure check and, for example, entering the wrong passcode in their bank's security form.

Customers should be given a chance to re-enter their details if they make a mistake. So it shouldn't stop a customer from paying, providing they have the correct information. 

If you have any questions on the updates, please email support@bookwhen.com.

Did this answer your question?