Mews has become the first hospitality operating system to obtain an e-money license in the European Economic Area, according to a hospitalitynet.org report.

The license authorizes Mews to issue electronic money, execute payment transactions, and provide merchant acquiring services across all 30 EEA member states under a single regulatory passport.

What does the license cover?

An EEA e-money license, issued under the EU's revised Payment Services Directive framework, allows the holder to:

• Issue electronic money against funds received
• Execute payment transactions on a payment account
• Operate money remittance services
• Provide merchant acquiring
• Hold and safeguard customer funds

For a hospitality operating system, the scope is broad enough to capture guest deposits, booking engine transactions, point-of-sale receipts, group bill settlements, and refund disbursement under one authorized arrangement. Chargeback liability and AML/KYC responsibility shift from the hotel to the platform.

Why is this a first in hospitality?

Software vendors serving hotels have historically routed payments through partner acquirers or licensed payment service providers rather than holding the license themselves.

The capital requirements, typically €350,000 in initial regulatory capital for a small e-money institution under PSD2, combined with safeguarding obligations and ongoing AML/KYC compliance burden have discouraged most PMS, RMS, CRS, and booking platform vendors from applying directly.

By securing the authorization, Mews becomes the only hospitality operating system in the EEA holding the license in its own name, according to the source. The home regulator, licensing date, and capital threshold category are not specified in the report.

What changes for European hotel operators?

Operators using the Mews stack in any of the 30 EEA markets will see structural changes in how payments flow. Instead of contracting directly with an acquirer for card processing and settling each transaction, Mews can sit as the licensed entity executing the transfer.

Chargeback handling, transaction data retention under GDPR, and PCI-DSS scope all shift to Mews. Hotels continue to bear PSD2-mandated Strong Customer Authentication procedures for card transactions above €30, with exemptions available only for low-risk, low-value recurring payments.

For multi-property groups, standardization across markets reduces the integration burden of managing separate acquirer relationships in Germany, France, Italy, Spain, the Netherlands, and the Nordics. Independent operators and small chains stand to benefit from interchange and scheme fee rates negotiated at platform scale rather than individually.

What is the regulatory framework?

The license sits within PSD2, which the EEA formally adopted through EFTA surveillance in 2019. Authorizations are granted by a national competent authority, typically the central bank or financial markets supervisor in the member state where the applicant is incorporated, and passported to the rest of the EEA through the single market mechanism.

Supervisory obligations include capital adequacy reporting, safeguarding audits, and transaction monitoring filings. The regime post-dates the original Electronic Money Directive (2000/46/EC), which PSD2 superseded effective January 2018 for EU member states.

What does this signal for the wider hospitality tech sector?

The development signals that the operational overhead of holding a payment license has become manageable for the largest hospitality software vendors.

Other major PMS and RMS providers processing significant card volumes in Europe will now need to evaluate whether to pursue their own licenses or remain tied to payment facilitator or partner-acquirer models. The decision affects the merchant-of-record structure, which determines who carries chargeback liability and operates the refund workflow.

If a competitor secures a similar license in the next 12 months, Mews's first-mover position inside hospitality would narrow to a brief window. Consolidation in payment and finance modules at hotel software vendors has been accelerating, and in-house licensing is the next logical step for the largest players.

What happens next?

Operators on Mews should expect formal communication from the company within the next two quarters detailing the migration timeline, updated merchant terms, and the activation date for in-house payment services. The license number will appear on the home regulator's public register, and Mews will need to onboard the authorization with acquirer partners before activating new payment flows. Partner hotels will need to update PCI-DSS attestations of scope and reconfirm Strong Customer Authentication configurations.