Hello!
I just would like to share some update from MEWS Support:
After further review with our experts, it seems that not all partners are updated to use the chargeable dates on the check-in day (if no activation date received in logs). Only the partners listed below follow this update.
- Agoda (always the check-in date at 6 AM local time)
- Expedia (always the check-in date at 6 AM local time)
- HotelBeds (always the check-in date at 6 AM local time)
- WebBeds (always the check-in date at 6 AM local time)
For the rest, the old rule, based on the payment policy, still applies [...]
Regarding the email, please note that the automatic failure emails for failed VCC payments will never be sent to the guest indeed. However, the "action required" email is always sent to the property like what you've received so that you are aware of any issues with the payment. Apologies for the confusion, and I’ve provided feedback to update the help guide accordingly.
and further:
In addition to the below email, Booking.com is also included in the list of partners to use the chargeable dates on the check-in day.
Well, at least now we know what’s the plan…
I guess that is the safest approach in terms of avoiding failed payment notifications. I just wished that MEWS included that change in the release notes!
Also, connecting Channelmanagers should be required by hotels and MEWS to supply VCC activation dates in the reservation details upon reservation creation. So it is adviseable to go and ask your channel managers representativ for this feature and if it’s not available yet, ask to have it added to the development queue (I did with D-EDGE, but feel free to support my request, too!)!
However, I still believe that it would be better to default to that behavior but provide a per source based setting to opt for payment policy based behavior instead. I have created a feedback post, please feel free to support it or add your comments also there: https://feedback.mews.com/forums/955604-payments/suggestions/49545311-provide-a-setting-to-opt-for-payment-policy-based
Kind regards,
Jean-Philipp.