Deutsch
English
Español
Français
NederlandsThe Mews Booking Engine is where your guests or bookers book online reservations at your property. While booking their stay, guests or bookers can pay for certain reservations directly in the Mews Booking Engine.
Reservations made via the Mews Booking Engine are eligible for payment during the booking process if they meet the following criteria:
- Have only automatic rates with settlement triggers in the past, or
- Have the "On confirmation" settlement trigger without any settlement offset value
Note: You cannot charge manual rates or rates with future settlement triggers through the Mews Booking Engine.
Whether the payment is successful or not, Mews displays a confirmation or error message in the Booking Engine and sends an email to the booker. These messages can help the booker understand what went wrong and how to fix it.
In this article you can learn about:
Confirmation messages
On successful completion of the reservation steps, the Mews Booking Engine displays a confirmation message in the booking engine and sends a confirmation email.
Successful payment
If the guest must pay for their reservation on confirmation and their payment is successful, they see the following messages.
Successful preauthorization
If the guest must pay for their reservation at a later date and their preauthorization is successful, they see the following messages.
Note: The preauthorization places the customer’s balance on hold to ensure that you can capture their funds later.
Error messages
The Mews Booking Engine notifies the guest when there is an error with their payment. These messages change depending on the type of error, for example, card errors or 3DS authentication errors. The guest then receives an email that explains the error and invites them to try again.
Payment failed
If the guest must pay for their reservation on confirmation but the payment fails, they see the messages below. This can be due to insufficient funds, an expired card or incorrect data. Mews then holds this reservation for up to 24 hours or until the payment is successful. The guest can try their card again or use a different payment method by:
- Clicking on Try again in the booking engine message, or
- Clicking on Check in online in the email.
Automatic settlement failed
Mews notifies the guest when an automatic settlement fails either because there is no card attached to the reservation or the attached card fails. Mews then holds this reservation for up to 24 hours or until the payment is successful. The guest can try their card again or use a different payment method by:
- Clicking on Try again in the booking engine message, or
- Clicking on Check in online in the email.
3DS authentication errors
3DS is an authentication solution that provides an extra layer of security for payments. It requires guests to authenticate payments by entering a code, password or by using their fingerprint to unlock their device.
Card verification needed
If the guest must pay for their reservation on confirmation but the card verification fails, they see the messages below. Mews then holds this reservation for up to 24 hours or until the card is verified. The guest can try to verify their card again or use a different payment method by:
- Clicking on Try again in the booking engine message, or
- Clicking on Verify payment in the email.
Payment verification failed
If the guest must pay for their reservation at a later date but their preauthorization or 3DS authentication fails, they see the messages below. Mews then holds this reservation for up to 24 hours or until the card is verified. The guest can try to verify their card again or use a different payment method by:
- Clicking Try again in the booking engine message, or
- Clicking Verify payment in the email.
After sending this email, Mews automatically resends the ‘Card verification needed’ email so guests can try again.
You can learn more about all emails sent to guests here.