TL;DR
Mews earned €219 million of its €291 million 2025 revenue from transactions, but still posted a 25% gross margin and a €111 million operating loss.
Payfac-as-a-service, used by Cloudbeds on Stripe and RMS Cloud on Adyen, is the practical default for most hotel software vendors.
Building your own stack keeps the full margin but puts chargebacks, fraud losses and compliance on your books.
Referral models carry no risk but earn little and leave hotels juggling several gateways.
Adoption decides the outcome: median payments adoption was 40% in 2025, while top platforms reach 80% or higher.
Every PMS, booking engine and guest app founder eventually gets the same question from the board: why are we letting someone else earn on the money that flows through our product? Hotels take deposits, pre-authorise cards, charge no-shows and settle folios every day. If that money moves inside your software, you can earn on it. The real question is not whether to offer embedded payments, but how much of the payments stack you should own.
This post lays out the three realistic options as pros and cons tables, using what hotel tech vendors and payment providers have actually published. It is a commercial decision as much as a technical one, so it sits inside your wider hotel tech go-to-market strategy, not just the engineering roadmap.
What embedded payments means for a hotel software vendor
Embedded payments means a hotel takes guest payments inside your software, under your brand and your commercial terms, and you earn a share of every transaction instead of handing that margin to a separate gateway.
There are three ways to get there. You can build your own stack and register as a payment facilitator or licensed institution. You can use payfac-as-a-service from a provider such as Stripe Connect or Adyen for Platforms, which handles acquiring and compliance while you own the experience and earn a revenue share. Or you can stay with a referral model: integrate third-party gateways, let the hotel hold the merchant relationship, and take a referral fee where one is on offer.
What the published numbers say
The strongest public case in hospitality is Mews. Skift's review of Mews' statutory filings (Skift, October 2026) found revenue grew 39% to €291 million in 2025, with roughly three quarters coming from transactions rather than subscriptions, and €17 billion in transaction volume on the platform. A summary of the same filings (Travel Trade Desk, via Skift) puts transaction revenue at €219 million against roughly €62 million of core SaaS revenue.
The same filings show the other side. Mews paid roughly €172 million in gateway commissions, interchange and bank fees in 2025, leaving €72 million of gross profit, a 25% gross margin, and a €111 million operating loss. In August 2026 De Nederlandsche Bank granted Mews Financial Services an Electronic Money Institution licence. Payments made Mews big; they did not, on their own, make it profitable.
Across vertical software more broadly, Stripe reported after Sessions 2026 (Stripe, May 2026) that median payments adoption rose from 27% in 2024 to 40% in 2025, while top platforms reach 80% or higher. Tidemark estimates each customer who adopts embedded payments generates an average of $4,200 in incremental ARR, and 2026 Stripe data shows platforms with embedded financial products see 11% lower annual churn.
Model | Who owns the merchant | Who carries fraud and chargeback risk | Hotel tech example |
|---|---|---|---|
Build your own | You | You | Mews, now with its own EMI licence |
Payfac-as-a-service | You, on a provider's rails | Mostly the provider, shared with you | Cloudbeds on Stripe Connect, RMS Cloud on Adyen for Platforms |
Referral | The gateway | The gateway and the hotel | PMS vendors that list several gateway integrations |
Option 1: Build your own payments stack
Building means registering with an acquiring bank as a payment facilitator, or going further and holding a licence, as Mews has done in the Netherlands. Stripe's own guide to revenue models for embedded payments is blunt about the trade: a registered payfac collects the entire margin spread but is responsible for submerchant chargebacks, fraud losses and compliance, and needs underwriting and reserve infrastructure before it processes a single dollar.
Pros | Cons |
|---|---|
You keep the full margin spread on every transaction | You carry chargebacks, fraud losses and reserves on your own books |
You control pricing, payout timing and the data end to end | Heavy upfront spend on underwriting, compliance and payments operations staff |
A licence lets you hold funds and launch financial products directly | Licensing is slow and country by country, so it can stall expansion |
Payments revenue can outgrow software revenue, as Mews' 2025 mix shows | Gross margin can still be thin: Mews reported 25% after €172 million of processing costs |
Fits when: you already process billions in volume, you have capital to fund a long build, and you see payments as the core business rather than an add-on. For most hotel tech vendors under a few thousand properties, this is a later stage, not a starting point.
Option 2: Payfac-as-a-service (Stripe, Adyen and similar)
This is where most hotel software vendors who embed payments actually sit. The Stripe case study on Cloudbeds explains that Cloudbeds first partnered with another payment provider, moved to Stripe in 2019, and built Cloudbeds Payments on Stripe Connect. Stripe reports hotels are now onboarded in hours rather than weeks, properties that added methods such as Apple Pay, Google Pay, Affirm or OXXO saw revenue rise 14.8% on average, and Cloudbeds added Instant Payouts and Stripe Capital as new revenue streams.
RMS Cloud took the same route with Adyen. RMS has used Adyen for Platforms since 2022 and launched RMS Pay in 2023. Adyen's 2024 announcement says properties report savings of between $50,000 and $200,000 annually, 6X faster payment processing and a 93% decrease in disputes, and Adyen's RMS case study cites 60 minutes a day saved in reconciliation.
Pros | Cons |
|---|---|
Launch in weeks or months, not years | Lower unit economics than a registered payfac, as Stripe itself notes |
The provider handles acquiring, KYC and most compliance | Your margin depends on the provider's pricing and your volume tier |
Prebuilt onboarding and dispute tools cut engineering time | Switching providers later means re-onboarding every hotel |
Add-ons such as instant payouts and capital come ready to switch on | You still own merchant support, payout questions and adoption |
Fits when: you want payments revenue and stickiness now, you have the sales and support capacity to drive adoption, and you would rather spend engineering on hotel workflows than on acquiring infrastructure. Treat it like any build or partner integration decision: the partner saves time, you keep the customer.
Option 3: Referral and third-party gateways
The lightest option is to integrate a list of gateways, let each hotel choose its own merchant account, and earn a referral fee if the gateway offers one. Plenty of PMS and booking engine vendors still work this way, especially those selling to hotel groups that already have negotiated acquiring contracts.
Pros | Cons |
|---|---|
No compliance, fraud or chargeback exposure | You earn little or nothing on transaction volume |
Easy to sell to groups that already have acquiring contracts | Hotels juggle several systems; RMS users ran up to three gateways before RMS Pay |
Engineering effort is limited to integrations | No payments data to build add-ons such as financing |
Fast to launch in any market the gateway covers | Competitors with embedded payments can price software lower and earn on volume |
Fits when: your buyers are larger groups that control their own payments, or you sell a point solution where money rarely moves through your product. If you do go this way, structure the commercial terms properly; our comparison of referral fees and reseller margins covers the trade offs.
A quick scorecard to choose
Signal in your business | Points towards |
|---|---|
Most customers are independents and small groups | Payfac-as-a-service |
Most customers are chains with their own acquiring | Referral |
You already process very large volume across several countries and can fund a licence | Build your own |
Your engineering team is small and stretched | Payfac-as-a-service or referral |
Payments revenue would reshape your pricing | Payfac-as-a-service, then review build later |
The go-to-market work nobody budgets for
Turning payments on is the easy part. Adoption is where the revenue is won or lost, and it is a sales and customer success job. At Stripe Sessions, Fullbay's VP of payments described paying software AEs, onboarders and CSMs to raise payments in every customer conversation. That is a compensation plan decision, not a product one.
Put payments in the first demo, not in a later upsell call
Add payments adoption to AE, onboarding and CSM targets
Decide your pricing before launch; Stripe warns that platforms which underprice find it hard to reprice later
Report payments revenue next to ARR so the board sees the full picture
Track adoption rate, take rate and churn of payments users against non-users
Payments also changes how you price software. Some vendors lower the subscription and earn on volume, which links closely to the questions in whether hotel software should use revenue-share pricing. And because payments users churn less, it belongs in your net revenue retention plan, not just your product roadmap. If you are adding payments to existing accounts, our guide to pricing a second product into a hotel account applies directly.
Not sure whether payments adoption, pricing or the sales motion is where your revenue is slipping? Start with a free GTM leak audit and see where the gaps are before you commit engineering to a payments build.
Frequently Asked Questions
What are embedded payments in hotel software?
Should a hotel tech startup become a payment facilitator?
How much revenue can embedded payments add for a software vendor?
Which hotel software vendors use Stripe or Adyen for payments?
Do embedded payments reduce churn for hotel software?
FREE RESOURCES
Free GTM resources for hotel tech vendors
The Hotel Deal Kit, the Hotel Software Pricing Index, the 12-point leak audit and the complete GTM guide, all in one place.
See the resources
Get the latest strategies, trends, and expert advice to help your hotel tech business stay competitive and grow.
Where is your revenue actually leaking?
Twelve questions, about twenty minutes, on your own funnel. The same audit I run on day one of an engagement. No call required.
Get the free leak audit
