Settings and activity
1 result found
-
69 votes
Hi all,
Thanks to the current feedback, we decided to move back this idea to be upvoted.
We did release Mews Terminals, however, due to security reasons, we will not store that card for future use.
Most of the upvotes mentioned that they’d like that functionality – even though the current Mews terminal is a huge step towards automation – providing the possibility to charge or pre-authorize a card without the need to ask a guest to give you card details & where you’d need to type in manually back information to Mews…
Looking forward to hearing more about this!
An error occurred while saving the comment
At my hotel property, this feature change is a hindrance. We need credit cards that are taken from the terminal to be saved because our guests do not stop by the front desk to settle their bills. We have a mini bar that needs to be reviewed for any items missing after the guests leave. Once the mini bar charges have been added to the folio, the front desk can then charge the final bill. At this point the guest has already left the property and the credit card is no longer physically present.
It's convenient for our guests to not have to physically check out and to have all their charges be settled onto to the credit card they gave at check in. But if the credit card given at check in was processed through the terminal only, Mews doesn't save the card for any future charges. It would be beneficial to have the credit card to be saved when processed through the terminal because 1. it prevents the front desk of having to do a 2 step system of hand keying the credit card at check in as the payment card then process the card through the terminal, 2. it saves time, 3. it's more secure to insert the card instead of hand keying the credit cards that are presented at check in by the guest.