Booking Engine Guide
  • Mews Booking Engine Guide
  • Booking Engine Standalone
    • Getting started
    • Deeplinks
  • Booking Engine Widget
    • Getting started
    • Use cases
      • Prerequisites
      • Testing in the Demo environment
      • Using your own Date inputs
      • Multiple enterprises and pre-selected locations
      • Disabling widget caching
    • Advanced guide
    • Reference
    • Troubleshooting
  • Booking Engine API
    • Usage guidelines
      • Authentication
      • Requests
      • Responses
      • Environments
      • Images
      • Supported currency codes
      • Supported language codes
    • Use cases
      • Availability blocks
      • On session payments
      • Payment card authorization
      • Supporting payment cards
    • API Operations
      • Availability blocks
      • Configuration
      • Hotels
      • Payment cards
      • Reservations
      • Reservation groups
      • Services
      • Vouchers
    • Deprecations
  • Integrations
    • Google Tag Manager
    • Google Triggers Reference
    • Google Tag Manager Configuration
    • Google Analytics cross-domain tracking
  • FAQ
    • Ways to integrate
    • Migration off the mews.li domain
  • Changelog
    • Changelog 2024
    • Changelog 2023
    • Changelog 2022
    • Changelog 2021
    • Changelog 2020
Powered by GitBook
On this page
  • Full example
  • Payment card storage
  • Payment gateways

Was this helpful?

  1. Booking Engine Widget

Advanced guide

PreviousDisabling widget cachingNextReference

Last updated 1 year ago

Was this helpful?

Full example

Here you can see a full example with all possible options used, with their default values. To get further information about the options and Javascript API calls, see the .

Note: Direct configuration of the booking engine through the options has been deprecated and will be disabled in future. Instead use Booking Engine Configuration in Mews Operations. The only supported options now are configurationIds and openElements.

Important: This is just an example, do not copy this directly to your website!

<script>
Mews.Distributor({
    // required
    configurationIds: [
        'aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee'
    ],
    // optionals
    openElements: '',
},
function(distributor) {
    // Always available api calls
    // distributor.open();
    // distributor.setLanguageCode(languageCode);
    // distributor.setCurrencyCode(currencyCode);
    // distributor.setStartDate(date);
    // distributor.setEndDate(date);
    // distributor.setVoucherCode(code);
    // Singlehotel mode api calls
    // distributor.showRooms();
    // distributor.showRates(roomId);
    // Multihotel mode api calls
    // distributor.showHotels();
    // distributor.showRooms(hotelId);
    // distributor.setCity(cityId);
});
</script>

Note: Make sure you have just one <script> tag containing the call to Mews.Distributor on your page.

Payment card storage

Payment card storage is used to safely collect and store information about a customer's payment card. Currently the Mews Booking Engine supports these payment card storage options:

Payment gateways

Payment gateways are used to securely handle customer payments. Configuration is done once, when the property is set up, and with the Mews Booking Engine this can be done with minimal setup. Mews Booking Engine currently supports these payment gateways:

Using a payment gateway is not mandatory, because reservations can be created without providing payment card information.

Important: The PCI Security Standard requires you to use an SSL Certificate on your website to be allowed to collect any payment information. For information on Mews PCI compliance, including current certification, please follow the links below.

Reference
PCI Proxy
Mews Payments
Mews PCI compliance
Mews PCI certificate