Mews Payments is the embedded payment infrastructure of the Mews operating system. It covers the full payment lifecycle: secure card collection and tokenization, automated online and in-person payments, payment requests by link, terminals, chargeback handling, settlements and reporting. The property contracts with, and is supported by Mews as the single commercial contact; the underlying card processing is performed by certified payment processors, currently Adyen and Stripe, depending on region and configuration. Besides cards, Mews also supports alternate payment methods such as iDeal, SEPA and ApplePay, GooglePay wallets. In European markets that operate with Euro currency, Mews is able to support Bank Transfer payments leveraging AirWallex. We are in the process of finalizing a contract with PayPal, which could be offered to our customers in Europe, starting with Germany as the launch market.
In this article you can learn about how to:
- 01 Get started
- 2.0 Product Capabilities
- 03 User Interface
- 04 Deployment & Updates
- 05 Release Notes
- 06 API & Integrations
- 07 Related Documents
- 08 Sub-processors
01 Get Started
1.1 Prerequisites
Mews Operations must be live or onboarding in parallel.
Activation requires completed merchant onboarding: know-your-business (KYB) and know-your-customer (KYC) verification, bank account verification and acceptance of the applicable payment terms.
1.2 How onboarding works
-
Merchant application: The property completes the Mews Payments application, including business, ownership and bank details.
-
KYB / KYC verification: Identity and business checks are completed with the payment processor; Mews coordinates this step.
-
Configuration: Payment policies including prepayment, preauthorization, settlement timing, payment methods and payout descriptors are configured in Mews Operations.
-
Terminals: If ordered, terminals are shipped, paired to the property, and tested.
-
Go-live and monitoring: First, transactions and payouts are monitored to confirm settlement to the property's bank account.
1.3 Indicative activation timeline
The Mews team aims to complete merchant verification typically within days of a complete application; total activation commonly takes 1 to 3 weeks, including terminal shipping where applicable.
Timelines may vary with KYB/ KYC complexity and market.
1.4 What the Partner needs to provide
-
Complete and accurate business, ownership and bank account information for KYB / KYC verification
-
Decisions on payment policies, when cards are charged or preauthorized, per rate group
-
Responses to chargeback evidence requests within 48 hours of notification; evidence must be submitted in English, in clear and legible PDF or image format, and can only be submitted once
1.5 Onboarding contact
|
Team responsible |
Mews Fintech onboarding team |
|
Support during onboarding |
Mews Help Center: help.mews.com (Mews Payments section) |
2.0 Product Capabilities
2.1 What's included in the license
|
Capability / Feature |
What it does for the Partner |
Status |
|
Card tokenization |
Card details entered online by guests are replaced by a secure PCI-compliant token via PCI Proxy hosted in Switzerland; raw card numbers are not stored in Mews.
PCI Proxy tokens are universal across processors. Tokens can be reused for charges during the stay within the configured retention period of a maximum of 90 days. |
Generally Available (GA) |
|
Automated payments |
Payment policies charge or preauthorize stored cards automatically: booking prepayment, no-show charges, in-stay charges and check-out settlement. |
GA |
|
Payment requests |
Secure payment links sent to guests by email, supporting partial payments and instalments, without requiring a guest account. |
GA |
|
Payment terminals |
Certified Mews terminals for in-person payments. Current lineup:
Terminal payments are automatically posted to the folio. |
GA |
|
Payment methods |
|
GA |
|
Multicurrency |
Guests can be charged in their home currency while the property settles in its local currency; the property carries no exchange-rate risk and may earn a share of the conversion markup.
Stripe:
Adyen:
|
See the adjacent column |
|
3D Secure and PSD2 compliance |
Strong Customer Authentication is triggered automatically for online payments; successful authentication can shift fraud liability to the card issuer. |
GA |
|
Chargeback management |
Mews notifies the property of disputes by email to the configured chargeback notification address. The property has 48 hours to respond with compelling evidence via [email protected].
Mews submits evidence on the property's behalf; the card issuer makes the final decision, typically 60–75 days.
Fee: €15 per dispute regardless of outcome. |
GA |
|
Payouts and reconciliation |
Regular settlements to the property's bank account. Payouts are aligned to the business day customer configured in Mews.
Payment, Payout and Chargeback reports available in Mews Operations. |
GA |
|
Flexible Financing |
Eligible properties may apply for a capital advance through the Mews partnership with YouLend, repaid as a fixed percentage of daily card sales.
Available in Belgium, Germany, Spain, France, Ireland, the Netherlands, Poland, the UK and the US. Subject to eligibility, minimum 3 months processing history, minimum €2,500 monthly card turnover. |
GA |
|
Wire Transfers by Mews |
Mews enables customers to collect bank transfer payments in Europe for the invoices they issue. Bank transfer collection managed within Mews for EUR markets. Pilot from April 2026. |
Soon – GA July 2026 |
|
In-person multicurrency on Adyen terminal lineup |
Multicurrency for in-person payments on the newest Adyen terminal models. |
Soon |
|
Payment Plans |
Customers can set up payment plans in Mews to collect recurring payments for long stays or other kinds of subscriptions they offer in their property, such as parking. These recurring charges are billed monthly to the payment method shared by the guest, by card, Bank Account in Europe (SEPA). |
GA |
|
PayPal |
Enable customers to offer PayPal as a payment method to their guests for online payments. Initial launch market is Germany and to be followed later by the US and UK. |
Soon |
2.2 Available as add-ons
Payment terminals are purchased separately, minimum 12-month term; models and country availability at https://www.mews.com/products/terminals/comparison.
Flexible Financing is an optional service subject to separate terms and eligibility. How to purchase: contact your account manager.
2.3 Marketplace integrations
Mews Payments is embedded in Mews products, including Booking Engine, Guest Portal, Kiosk, POS and Operations. Integration partners can process payments through Mews Payments using the Mews Checkout component.
Full catalogue: https://www.mews.com/en/hospitality-software-marketplace.
03 User Interface
3.1 Interface overview
Mews Payments is operated from within Mews Operations: payment policies, payment requests, refunds, disputes and reports all live in the PMS. Guests interact with Mews Payments through the Booking Engine, Guest Portal, Kiosk, payment links and terminals.
3.2 Key Partner workflows
-
Configure payment policies per rate group and let bookings charge or preauthorize automatically
-
Send payment request links for deposits, instalments and outstanding balances
-
Take in-person payments on Mews terminals, including at the Kiosk and POS
-
Respond to chargeback notifications within 48 hours by forwarding evidence to [email protected]
-
Reconcile settlements using the Payment, Payout and Chargeback reports
3.3 Access methods
|
Web app |
Yes. Managed within Mews Operations |
|
Mobile |
Guest-facing flows are mobile-web; terminals are dedicated devices |
|
Embedded in Mews OS |
Yes. Mews Payments is embedded across the Mews product suite |
|
API access |
Yes. Mews Checkout for integration partners. See Section 06 |
3.4 Accessibility
WCAG 2.1 AA is the Mews default standard for guest-facing payment surfaces.
04 Deployment & Updates
4.1 Deployment model
|
Deployment type |
Mews-managed cloud. Card data is handled by PCI Proxy through tokenization and via certified payment processors; Adyen, Stripe. Raw card data is not stored in Mews systems, which reduces the property's PCI scope. |
|
Environment types |
Production and Demo/ sandbox (test transactions) |
4.2 How updates are delivered
Continuous deployment for cloud services. Terminal software and firmware are updated remotely by Mews and the processor.
Where Mews migrates a property between processors, the migration is scheduled with the property, includes pre-flight checks and is followed by a post-cutover monitoring period.
4.3 Update cadence
Feature releases: Continuous.
Security and compliance updates: As required, applied by Mews without advance notice.
Processor migrations: Scheduled individually with affected properties.
4.4 Does the Partner need to do anything after an update?
No Partner action is required for standard updates. During a processor migration, the property may need to complete renewed verification steps and should expect a transition period for items tied to the previous processor, such as held dispute reserves.
05 Release Notes
5.1 Current version
|
Current version |
Continuous delivery. Mews Payments does not carry Partner-facing version numbers |
|
Release date |
Rolling; latest release notes at releases.mews.com (Release notes) |
|
Type |
Continuous. Feature, minor improvements and security releases |
5.2 Release history
|
Version |
Date |
Type |
What changed |
Partner action? |
|
– |
May 26 |
Minor |
New Adyen terminal lineup: A1 Starter, A2 Flex, A3 Engage, A4 Engage Countertop made available; Interac live in Canada on Adyen terminals. |
No. Existing hardware unaffected |
|
– |
Apr 26 |
Minor |
iDEAL made available on Adyen processing configuration; activation via the Marketplace. Wire Transfers by Mews entered pilot for EUR markets. |
No. Optional activation |
|
– |
Mar 26 |
Minor |
Multicurrency extended to POS payments in eligible markets. |
No |
|
– |
2025–26 |
Minor |
Daily business-day-aligned Sales Day Payouts with customizable bank descriptors rolled out on Adyen configurations. |
No |
06 API & Integrations
6.1 Mews Open API
|
API available? |
Yes. For integration partners |
|
API type |
Mews Checkout, an embedded, hosted payment component for partner booking flows, covering cards, wallets and local methods with PCI, PSD2 and 3DS handled by Mews. Some of the payment methods Mews offers are marked as ‘deprecated’ in our documentation; a proper deprecation has not yet been put in place. |
|
Documentation | |
|
Authentication |
Partner credentials issued by Mews |
|
Rate limits |
Applied per environment. |
6.2 Standard integrations
Mews Payments is required for Mews POS and powers payment steps in the Booking Engine, Guest Portal and Kiosk. Third-party terminals and external payment providers can have their transactions recorded in Mews as External Payments without automation.
Full catalogue: https://www.mews.com/en/hospitality-software-marketplace.
6.3 Third-party integrations
Integrations with third-party products and services are provided and operated by the relevant third party. Mews does not warrant the availability, performance or continuity of any third-party integration, and third-party integrations are not covered by the Mews SLA.
07 Related Documents
7.1 Training, specific guidance & additional resources
Mews University learning paths and the Mews Help Center at help.mews.com (Mews Payments section).
7.2 Living documents incorporated by reference
|
Document |
Where to find it |
|
Terminal comparison and availability |
08 Sub-processors
As contained at: https://www.mews.com/en/legal/mews-sub-processors