Apple Pay and Google Pay are digital wallets where iOS and Android users can store their payment card details and then make payments via the latest authentication technologies like Touch and Face ID.

Apple Pay and Google Pay are available for all Mews properties using Mews Payments via Stripe, so guests can choose to pay using these methods in Mews Booking Engine, during online check-out, and for payment requests sent by your property.

A faster and more seamless payment experience through digital wallets helps boost your online bookings and conversions for payment requests and online check-outs. Apple Pay and Google Pay digital wallets use the latest authentication methods for card verification, resulting in fewer disputes, saving properties revenue.

Note: Apple Pay and Google Pay for online transactions are available only via Stripe.


How to enable Apple Pay and Google Pay?

For properties: Apple Pay and Google Pay are automatically enabled for all Mews properties, except for those using surcharge services in Australia and New Zealand, which are not supported by Apple Pay and Google Pay.

Note: Properties located in Australia and New Zealand can manually enable digital wallets in their Stripe integration, in the digital wallets section.

For guests: The speed of checkout with Apple Pay & Google Pay is usually three times faster, as guests don’t need to insert payment card details. To provide an express checkout experience to your guests in the Mews booking engine with Apple Pay & Google Pay, we recommend you revise your booking engine configuration to reflect your preference about payment card collection, as follows:

Navigate to Service > Bookable Services > Booking engines > Payment card input. Choose one of these options to meet your preferences:

  • Always required: To collect payment card details for every booking.

  • Not required: If you don’t want guest’s payment card details on reservation.

  • Not required for fully paid bookings: If you don’t want payment card details for bookings where guests pay in full on reservation creation. Choose this option to accept payment with Apple Pay and Google Pay, or

  • Not required for fully or partially paid bookings: If you don’t want to collect payment card details for bookings where guests pay in full or partially on reservation. Choose this option to accept payment with Apple Pay and Google Pay.

You can learn more about how to set up your Mews Booking Engine here.

Note: Guests can view and avail the Apple Pay and Google Pay payment options in the Mews Booking Engine only when the payment settlement option for your rate group is set to "Confirmation" in the "Settlement trigger" field and without any settlement offset.

You can learn more about how to set up automatic payment settlements in Mews here.


What are the costs involved?

  • Apple Pay and Google Pay are automatically enabled and free of charge for all Mews properties using Mews payments via Stripe.

  • There are no additional processing fees and pricing is the same as for any other payment card. Fees as stated in the respective Merchant agreement are applicable (includes interchange, scheme and Mews commission fee).

  • Guests pay through their digital wallets, so card details cannot be reused for future charges, but that also means you don't have to pay the tokenization fee.

Note:

  • Since Apple Pay and Google Pay are digital wallets, commission adjustments are done the same way as with payment cards via Stripe.

  • No need to worry about refunds, these are processed the same way as with physical cards.


Where can I find Apple Pay and Google Pay transactions in Mews?

  • In the Guest profile: You can view Apple Pay and Google Pay transactions under Customer Profile. The payment card section displays payments charged via Apple Pay and Google Pay.

  • In the Payment report: Use the "Apple Pay" and “Google Pay” filters to display Apple Pay and Google Pay transactions.


You can read the guide below to learn about your guest's journey with Apple Pay and Google Pay digital wallets in the Mews Booking Engine, while fulfilling payment requests and during online check-out.


Did this answer your question?