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

Was this helpful?

  1. Booking Engine API
  2. Use cases

Supporting payment cards

PreviousPayment card authorizationNextAPI Operations

Last updated 1 year ago

Was this helpful?

When creating a reservation, it is possible to attach a payment card to the reservation. As part of creating your own custom booking engine, you may want to have a form within your application where customers can enter their payment card data and send this data to the Booking Engine API for further use. Payment card data can then be used by Mews for charging the customer. To do that, some Booking Engine API operations support or require in the request.

Where to get CreditCardData values

  • Confirm that the hotel or property supports PCI Proxy by checking the field in the configuration data returned from . Also refer to the documentation to see what other API data you could potentially use for your implementation.

  • Follow the guide to handle the sensitive card data and obtain PaymentGatewayData. Use as the merchantId while implementing PCI Proxy fields.

  • The PCI Proxy service will return a transactionId in the response which you use as PaymentGatewayData inside the object.

  • Once you have the PaymentGatewayData, you can create a payment card by providing in the request body.

Production environment: Note PCI Proxy documentation only highlights the sandbox endpoints, used for the staging environment. For the production environment, omit the sandbox. part from the address. For example, https://pay.sandbox.datatrans.com/upp/payment/js/secure-fields-2.0.0.min.js becomes https://pay.datatrans.com/upp/payment/js/secure-fields-2.0.0.min.js.

PCI Proxy Secure Fields
Credit card data
Credit card data
Credit card data
Payment card storage type
Get hotels
Payment gateway
PublicKey