Mews Payments is the right move for most small lodging operators already running Mews, with one condition you cannot check before you sign: Mews publishes no processing rate anywhere public. Price it against your own Stripe account at 2.9% plus 30 cents on a domestic card. If your own account already works, stay put until you can see that number.
Should you move payments into Mews, or keep your own Stripe account?
Mews Payments is the card processing built into Mews, so the charge, the bill, the payout and the refund all happen inside the property system. Mews holds the merchant account itself, and your property's payments are processed through that account. Its own payments product page puts it as one system doing both jobs: "The operating system is the payment system, so reconciliation, reporting and refunds happen in one place", and its embedded versus integrated payments page describes Mews Payments as built directly into Mews itself, so the same support team that handles your front desk also handles your payments.
Most Mews operators are not building a Stripe checkout from scratch. They already have a Stripe account wired into a booking engine, so the choice is keeping cards there at Stripe's published 2.9% plus 30 cents on a domestic card, or moving the charge into Mews at whatever rate your merchant contract turns out to say.
What does Mews Payments cost per booking?
Mews does not publish that figure. None of Mews's public pages, including its legal fees page and its help centre, show a percentage or a per transaction figure to anyone without a Mews login. The only fee the payments page names is a one time charge for storing a guest's card securely so it can be billed again later, and the page lists no amount for it. Your rate is whatever your merchant contract says, so ask for it, the chargeback fee and the payout delay in one email before you switch. Compare that quote against Stripe's own price list, the only number in this whole comparison you can actually read.
| Your own Stripe account | Mews Payments | |
|---|---|---|
| Per transaction cost | 2.9% plus 30 cents, domestic card | Not published |
| Where the rate is set | A public price list | Your merchant contract |
| Chargeback cost | $15.00 per dispute received | Not published |
| Who chases the dispute | You | Mews notifies you and helps you submit evidence |
| Stored cards sit | On your account | Stored securely inside Mews as a stand-in for the real card number |
Fees read from mews.com/en/products/payments and stripe.com/pricing, checked on September 2026.
Price a real month of your own bookings at the rate Mews quotes you, against the same month at 2.9% plus 30 cents. Contract pricing is normal in this trade: Booking.com does not name a single commission figure either, and its own partner help page says "The exact percentage depends on your country, property type, and the accommodation agreement you signed when you joined us."
Keeping your own processor, and the weekly job that comes with it
Most operators reading this already keep their own processor, which means registering outside payments in Mews by hand every week. An operator running an outside booking engine and their own card processor wrote in Mews's own community forum in May 2025 that "any advance payments need to be manually registered in Mews as external payments. This manual step has proven to be one of the biggest pain points for our hotels. Payments are often misallocated, or bookings end up being charged twice by mistake."
Move the charge inside Mews instead, and the weekly registration step disappears, along with the double charges the forum post describes. Mews has a built-in safeguard against double charges: if a connection drops and your booking system sends the same payment instruction twice, Mews recognizes the repeat and still charges the guest only once. Mews documents this protection as a setting someone has to turn on, so check your booking engine's integration settings and turn it on if it is not already.
Mews's own payout reports break a payout into transactions where "Each transaction states its type, the related payment where there is one, and any invoice references." A city tax line arrives already labelled as a tax line. Tracking down what an unlabeled line actually was can still eat real time at month end close. Charges post to the guest profile instead of the reservation, so tracing one back to a specific booking takes an extra step. The same trade on another system is in the Cloudbeds Payments comparison we ran first.
What do you give up when Mews holds the merchant account?
Moving your merchant account to Mews changes four things you will only notice after you have already switched. Mews reveals your rate only inside the contract it sends you when you sign up, so you cannot price it in advance. You give up the merchant relationship too, so when money is late or a payout does not match what you expected, you ask Mews to chase the processor for you. You can also lose the processing fee on a refund: Stripe's own documentation says plainly that "Application fees aren't automatically refunded when issuing a refund", per its guide to direct charges. Ask Mews whether its share follows the same rule when you refund a guest. And answering a question about one charge gets slower. On your own processor account you can usually work out what an undescribed payment was in five minutes, but hand that same question to somebody else and it can eat most of a morning before they get back to you.
What we do at our own apartments
We faced this exact tradeoff ourselves. Maxine and I own MINT @Naschmarkt, serviced apartments in Vienna, and since we already had a development team on hand, we built the booking and payment setup ourselves instead of routing it through a managed system. We charge the guest on our own Stripe account and write the transaction back into the property system by hand, which keeps us clear of the 1% platform fee the managed setup would have taken. The rate plan is 50% at booking, balance charged five days before arrival on the stored card.
The right payments setup for your property size
If you run 8 to 15 units, have no developer, and nearly every booking arrives through the platforms, moving to Mews Payments is the right call. Registering outside payments by hand is a real weekly cost, and there is nobody free to keep a second account running smoothly. If you run 15 to 25 units and already charge cards on your own domain, stay put: you hold the merchant relationship, already know what Stripe charges, 2.9% plus 30 cents, before signing anything, and can query a disputed charge yourself. The same logic holds if Mews Payments is already working for you: leave it alone. Changing processor mid season means running two of them for a quarter while the bookings already taken run down on the old one.
If nobody on your team is technical, moving to Mews Payments closes the double-charge risk on a retry and hands you a payout already broken into labelled lines you can check one by one. Ask about the unpublished rate before you sign anything. Read the MINT case to see how we run the other route at our own property.
Bring the setup you are weighing up to the call and we will tell you what it does not cover. Twenty minutes, prepared for your property. Or count what the platforms take first, on the commission savings calculator. If you want a second opinion on your own numbers, book the call.
Sources
- Hotel Payment Processing, Mews
- Embedded versus integrated payments, Mews
- Create a payment, Mews POS API reference
- Accounting, Mews Connector API
- External Payments, Mews Community
- Pricing and fees, Stripe
- Direct charges, Stripe documentation
- How invoices and commission work, Booking.com for Partners
Vendor pages checked on September 2026.
