Take the booking the OTA wanted
Take room payments in stablecoins to your own wallet, with no acquirer reserve holding your cash through peak season — once the guest has checked out, the payment can never be reversed.
Where direct-booking economics break under OTA dominance
Why does the booking you won direct still leak revenue at the till?
Four ways OTAs and card rails put room revenue at risk — the channel commission, the fee on direct, the dispute after the stay, and the spread on foreign guests.
The OTA channel takes a double-digit slice of every room
Booking.com's baseline commission starts around 15% and climbs past 20% on its preferred-partner program; Expedia Group brands run tiered dynamic commissions across the same band. A mid-size independent at healthy occupancy routinely hands the OTAs a six-figure sum a year — money that could have funded a direct-booking pipeline instead. Chains negotiate the rate down; independents are the segment hit hardest.
And the card fee stacks on the rooms you DO win direct
For every guest you pull off the OTA to your own site you save the commission, then immediately pay the card processor. On a standard 2.9% + $0.30, a $150 single-night booking costs about $4.65 to accept — roughly 3% before anything else. Better than 15%, but still a real bite on slim hospitality margins, and it scales with every direct room you fought to win.
A no-show can still be charged back months later
Lodging sits among the card networks' elevated-dispute categories — no-show disputes, "I cancelled within policy" claims that contradict your records, fraud-flag false positives on international guests. The dispute window runs up to 120 days from booking, so a no-show in March can still be disputed in July. Your no-show policy is your contractual right; getting it past the chargeback panel is a different fight.
Cross-currency margin eats every foreign guest
A boutique hotel in Lisbon taking direct bookings from US and Brazilian guests pays a processor 1–2% in cross-currency conversion on each foreign card, at a rate it sets, not you. On a book full of international guests, that spread is margin leaving your treasury on every stay — on top of the acquiring contract you negotiate per jurisdiction. (Side-by-side in Pricing.)
How direct bookings work in stablecoins
What changes when the room settles in stablecoins?
Settle the room on a wallet instead of a card, and four costs fall away.
A no-show charge holds — the dispute window never opens
A stablecoin payment has no chargeback mechanism. Once the guest signs the transfer for the deposit or full payment, there is no panel to convince — no-show fees, cancellation-window penalties, and deposit-keep decisions are all governed by your written policy, not the issuer's dispute team. The card-network default of siding with the cardholder, which is the real cost driver on lodging, isn't in the loop.
Room revenue in your wallet the night it's booked — no reserve
The guest pays and the room revenue credits your Paymos balance within seconds — no 2–7 day payout cycle and nothing held back in a peak-season reserve you have to negotiate or wait out. For an independent paying cleaners, suppliers, and seasonal staff on tight cycles, the cash arrives exactly when working capital is tightest.
Deposit now, balance at check-in — two clean payments
For multi-night stays where you want a deposit at booking and the balance on arrival, send two payment links — one immediate, one for check-in day. The guest signs the deposit today and the balance when it's due, each a real transfer. No mid-stay card hold to dispute and no balance-charge surprise at departure.
Roughly $1.50 to accept a $150 room, not $4.65
That same $150 single-night booking costs about $1.50 to accept on Paymos instead of roughly $4.65 on a card processor — and a foreign guest pays the same stablecoin you price in, so there's no cross-currency cut and no processor-set rate. You keep the difference on every room, with no per-transaction minimum and no separate currency-conversion fee. Full rate card in Pricing below.
How independent hoteliers wire Paymos in
Which integration fits your direct-booking stack?
Three integration paths — from a no-code direct-booking page to a PMS-driven flow.
Hosted Checkout — a direct booking page with no code
The guest picks the room and dates on your site, you create a Paymos invoice with the total, and redirect them to a hosted page where they pay from their wallet and return with a paid booking. Best for independents on WordPress or a basic CMS-driven site without a dev team.
See details
Embedded checkout — Paymos inside your booking widget
Running a custom direct-booking site? The embedded flow keeps the wallet payment inside your domain, so the guest never leaves your funnel. Works with React, Vue, and server-rendered HTML; invoice creation and confirmation events come through your existing API integration.
See details
Server-side API — PMS-integrated booking flow
On Cloudbeds, Oracle Opera, Mews, or a custom PMS, the server-side API lets the PMS create invoices on reservation, listen for confirmation over signed (HMAC-SHA256) webhooks, and update reservation state automatically. The PMS stays the source of truth for inventory; Paymos handles the payment leg.
See detailsDirect-booking flows on stablecoins today
What booking patterns run cleanly on a wallet?
Four flows from working independent hoteliers — single night, multi-night, loyalty, and corporate block.
Single-night direct booking — Hosted Checkout
For a direct one-night booking, issue the room invoice from the reservation system. The guest pays from their wallet, and the confirmation webhook secures the booking before arrival. No OTA commission or acquirer reserve is deducted.
Multi-night stay — deposit plus balance via two links
A week-long stay where you want a deposit now and the balance at check-in. The guest signs the deposit today and the balance on arrival day, each a clean wallet payment. There's no held card to dispute mid-stay and no surprise charge on departure — the deposit-plus-balance rhythm just works.
Loyalty membership — monthly renewal invoice
A boutique chain running a paid loyalty tier for guaranteed rates and late checkout. Each cycle your system issues a renewal invoice the member pays from their wallet — no card on file to expire and no involuntary churn when a card silently rotates. The membership just renews.
Corporate group block — server-side API
A room block for a company offsite. Procurement gets an invoice through your CRM and pays from a corporate wallet; your PMS confirms the block on the webhook. The receivable closes on confirmation, with a real invoice attached and no card-statement reconciliation on either side.
Direct hotel booking on stablecoins
Frequently asked questions
How does Paymos integrate with my PMS (Cloudbeds, Mews, Opera)?
Can I do "deposit at booking, balance at check-in" with Paymos?
How do refunds work when the guest cancels, driven from the PMS policy?
What about no-show charges — can I still keep the deposit?
Which networks do hotel guests actually use for $100–500 bookings?
Can I keep the OTA for visibility and use Paymos for repeat direct guests?
Honest disqualifier
When NOT to use Paymos for hotel booking
Four hotel setups where the OTA or the card machine keeps its place.
The OTAs are your demand engine, not just a fee line
If Booking.com fills most of your calendar, the commission is paying for distribution you don't otherwise have — and no payment rail can generate a room night. Paymos makes the direct bookings you already win cheaper to keep; it doesn't create new ones. Build the direct funnel first, then move its payments off cards.
Your front desk runs on card holds, not payments
Pay-at-property rates, incidentals cover, and no-show guarantees all lean on the pre-authorisation — a hold that may never be captured. A stablecoin transaction is always a real transfer: you can take a deposit and refund it, but you cannot place a hold on a guest's wallet. If the auth is the backbone of your desk workflow, keep a card rail under it.
Your room nights come from AP systems that only pay by ACH or card
Some enterprise procurement teams can settle from a corporate wallet — many can't and won't soon. If your block business runs through AP software that automates only ACH and virtual cards, the wallet rail waits on a buyer-side change you don't control. Offer it where procurement is willing, and bill the rest on the rails their systems already speak.
Sub-$30 hostel beds sold to backpackers on the move
A dorm bed gets booked from a phone in a bus queue, and the one-tap card flow wins that moment. On a $25 bed the fee you save is cents, while an unfamiliar wallet step risks the whole booking. Show the wallet to long-stay and crypto-native guests, and let the card take the impulse bed.
Related flows
Other Travel & Hospitality sub-niches on Paymos
Pricing
1.0% per direct booking. No OTA commission, no peak-season reserve
Same rate for the $30 hostel bed and the $5,000 suite block — about $1.50 on a $150 room versus roughly $4.65 on a 2.9% + $0.30 card processor, before any currency conversion. High-volume tier at 0.3% on request.
See pricing