Strong Customer Authentication (SCA), a rule in effect as of 14 September 2019, as part of PSD2 regulation in Europe, requires changes to how your European customers authenticate online payments. Card payments require a different user experience, namely 3D Secure, in order to meet SCA requirements. Transactions that don’t follow the new authentication guidelines may be declined by your customers’ banks.
SCA may not affect you, depending on what booking sites you use and which payment methods are set on each site.
SCA only applies when Uplisting processes guest credit cards on your behalf, via Stripe. Most transactions are SCA ready/compliant. See the table below.
|Booking source||Payment method||SCA ready/compliant||Solution||Stripe API used|
|Uplisting direct booking website||Guest credit card||Yes||No action necessary.||Payment intents|
|Guest credit card||Yes||No action necessary||Payment intents|
|Booking.com||Payments by Booking.com (Booking.com takes payment)||Yes||No action required||None|
|Booking.com||Payment via Guest credit card||No||Booking.com are not currently providing a solution for these credit card payments.|
These transactions are likely to fail.
The solution is to move to Payments by Booking.com or send guests the Uplisting booking confirmation page to update their credit card.
All credit card entries via the Uplisting guest facing pages are SCA compliant.
|Booking.com||Virtual credit cards||Yes||No action required||None|
|Vrbo||Guest credit cards||Yes||No action required||Payment intents|
|Airbnb||Not applicable||Airbnb processes payments on your behalf. No action necessary.||None|
I'm taking payments directly from a Booking.com guest credit card. What happens if they update their card on Booking.com?
No credit cards, updated or not, coming from Booking.com are 3DS. The solution is to move to Payments by Booking.com or send guests the Uplisting booking confirmation page to update their credit card.
Updated about 1 year ago