Improove 3D secure confirmation as per EU Regulation.
At the moment this is what happens:
-The guest makes the reservation.
-The system sends him the confirmation
-The system sends a second email where it asks to authorize the payment.
What happens if the guest does not authorize the payment?
We can cancel the reservation but if the guest will arrive and we will not have the room available for him we would miss our commitment because he will have in his hands our confirmation.
On the other side, if the guest will make a no-show and we will charge him, the same guest will have the right to get the refund because we do not have the double confirmation as per PSD2 directive EU.
It is clear and logical that the hotel should get the authorization to charge the credit card before sending the confirmation to the guest.
For this reason, this is what should happen:
-The guest makes the reservation
-The system asks to the guest to authorize the payment for the accommodation
-After the authorization by the Guests, the system sends him the final confirmation.
Thank you
L.
Luca Sebastianelli
shared this idea
Hello,
Thank you for your feedback.
Mews is fully optimized for processing payments under the PSD2 regulation.
We are maximizing payment acceptance by asking the guest to authenticate the payment whenever the bank is requiring the authentication.
In the booking engine flow, for example, the guest will see a bank’s page pop-up as a part of the check-out flow, if the payment is not successfully authenticated, according to the PSD2 rules, Mews won’t be able to charge the guest. If payment is authenticated, in guest profile you will be able to see that the payment is successful.
If you’re charging the guest on the card that was not previously authenticated by the guest, if the bank, at the time of the payment is requiring the biometric or SMS acceptance via bank code, as the guest is not present at the time of the payment, Mews is sending the email to the guest to verify that payment, which may result in successful payment reflected in Mews. If the payment is not successful, we are not going to cancel reservation but rather leave the opportunity for the hoteliers to charge the guest e.g. via Mews terminal.
For more info, here’s the FAQ in our help guide. https://help.mews.com/s/article/psd2-and-3ds-faq?language=en_US
Curious to hear if you have more information about this flow, feel free to replay!
Kind regards,
Jovana
Mews Product Team
-
Femke van der Meer
commented
Hey Jovana,
Where does the MEWS booking engine sits this process?
And how can we make sure the payments are 3D secure per reservation without work arrounds of pulling seperate reports?
I am suprised by the low number of bookings which go through the 3D secure for our properties and high amount of chargebacks.
We expected when sending "payment requests" via MEWS these would always go through the 3D secure if above 30 euro but this doesnt seem the case (anymore?).
Kind regards, Femke