Skip to main content

Hello, 

Just checking if I’m the only one here having this issue? 

Normally speaking, when we receive a reservation via Booking.com, the credit card details are automatically loaded into Mews (in the payment methods). 

Now this is not the case, and we have to do it manually. 

Anyone else with this issue? 

I thought this might be an issue on the side of the channel manager, but other OTA cards load in correctly. 

Thank you.

I am experiencing the same issue; I opened a ticket regarding this matter yesterday. The problem seems to stem from Booking.com, which is not sending the credit card details. We also work with Cubilis, and unfortunately, we are not receiving any credit card information in their system either.

Best regards, 

Robin

 


Same happended for us, also working with Cubilis but it seems fixed now and as @barb00sa said, the problem apparently came from Booking…

 

Have a nice day

 

Stephane


Hello all, 

thank you for this topic! 

@barb00sa @PHman88 - can you let me know if the problem was fixed for you as well? 

If not, I´ll start digging! 

Thank you!


Sorry @MarketaOupi 

 

Just had a reservation and the issue is still not fixed but the virtual credit card is available on the booking extranet

 

Regards

 

Stephane


Hello @smehia, thank you for the message! checking it with the CHM experts! 💡


good morning.

update from my side: 
the integration (in which the VCC is automatically loaded as payment method) works.

the scheduled payments, determined via the rate groups, are not implemented correctly (yet):
eg. non-refundable should be 100% at confirmation, but the payment was not time-scheduled correctly
eg. refundable rate (in our case 100% chargeable 3 days prior to arrival), but the payment was not time-scheduled correctly

thank you for taking a look


We’ve had issues with the scheduled payments as well - sometimes it just takes random amounts like 10 %of the reservation, or the validation date of the card sent by booking.com is wrong.


Hello all, 

thank you for this topic! 

@barb00sa @PHman88 - can you let me know if the problem was fixed for you as well? 

If not, I´ll start digging! 

Thank you!

Problem shuld be fixed. I have got this message from Stardekk:

Goedemiddag,

 

Sinds vrijdag 20 september werden reserveringen via Booking.com zonder creditcardgegevens naar de Channel Manager verstuurd.

 

Dit probleem is intussen opgelost in overleg met connectivity van Booking.com, alle gegevens worden opnieuw doorgestuurd sinds 24 september. Helaas is het niet mogelijk om deze creditkaarten terug te pushen vanuit Booking.com naar de Channel Manager. De ontbrekende creditcard gegevens kan je tot 10 dagen na boekdatum opvragen op het extranet van Booking.com.

 

Voor andere vragen kunt u altijd contact opnemen met ons support team via [email protected].

Nog een fijne dag gewenst.

 

Met vriendelijke groeten - Kind regards - Bien cordialement

 

Joshua Jacxsens
​Product Support Specialist

Customer Care & Operations


Hello all,

so after talking to the CHM and Payment experts, this is the conclusion:

Sometimes, B.com may not send the virtual credit card (VCC) details, and occasional issues can happen.

However, we haven't seen a big increase in reports about this, so we do not see this as a trend/bug.

Since B.com decides when to send the VCCs, the best way we can help is if you open a case with us and provide some specific examples, so we can investigate in detail.

Hope this helps! 


The issue seems to be two-fold: 

1) B.com VCC not loading into Mews → this seems to be fixed.

2) Scheduled payments - I will keep an eye out if this is fixed and will let you know.
Just to give a few examples: standard rate is scheduled to be paid at the end of the stay (instead of 3 days prior); non-refundable rate is scheduled to be paid 1 day prior to arrival (instead of immediately)

Doesn’t seem to be an issue with my settings as for all other reservations the offset (= date of scheduled payment) is correct.

Will keep an eye out and report as soon as it looks fixed.


the latter issue (incorrect scheduled payments) have unfortunately not only affected the newest reservations, but also existing reservations.

eg.

  • reservation date 28/07;
  • arrival date 16/12
  • 100% payment as per policy: 13/12.
  • (incorrect) Mews scheduled payment: 17/12

On our side, we got the same message as @barb00sa from our channel manager (also Cubilis from Lighthouse)

 

So it should be fixed 😉

 

Regarding the other part of the problem, no issue on our side

 

Stephane


I’ve done random checks these last two days and the dates of the scheduled payments seem to be back to normal 😀


Reply