Accept Crypto Payments at Your Hotel — Deposits That Stick, Check-outs Without Chargebacks

The payments problem checked into every hotel

Lodging runs on the most fragile kind of card payment there is: card-not-present, taken weeks in advance, from a guest in another country. A direct booking arrives by email or through your website, the front desk keys in a card to hold the room, and that transaction is already the expensive kind — a higher card-not-present rate, and the fraud liability sitting on the property rather than the bank. On a $600 three-night stay, ~2.5–3% is $15–18 gone per booking; across a 20-room property running most of the year, the card stack quietly takes what a full-time housekeeper earns.

Then there's the money you never manage to hold at all. A "guaranteed" booking with a card number is only as good as the authorization behind it: cards expire between booking and arrival, holds drop, foreign cards decline at the worst moment, and a no-show becomes a debate with an issuer about whether your cancellation policy was "clearly disclosed." Many small properties simply don't charge deposits because the card machinery makes it painful — and eat the empty room instead.

And the dispute window outlasts the stay itself. A guest checks out happy, and six weeks later a chargeback lands: "services not as described," or a family member "didn't recognize the charge." The network gives cardholders roughly 120 days. You respond with a signed registration card and a folio; the dispute fee arrives either way; and if you lose, the room-night, the breakfast, and the late check-out fee are all clawed back — from a night you can never resell.

What it costs to leave this unsolved

Price out one bad month. Two no-shows on peak-season rooms you turned other guests away for, one lost chargeback on a $600 stay plus its $15–25 dispute fee, and the ordinary 2.5–3% skim across everything else. For a small property, that's a four-figure hole — and unlike a restaurant, you can't make it up on volume tomorrow, because last Tuesday's empty room is perishable inventory that already expired.

Cash flow compounds it. Card settlements take 1–3 business days; in high season you're fronting linen services, staff overtime, and supplier orders against money that's still "in transit." Properties that lean on online travel agencies to avoid card handling trade one problem for a bigger one: 15–25% commission per booking and payout cycles that can stretch past the guest's departure — you host in July and get paid for it well after the sheets are washed.

There's also the revenue that never reaches you: the international guest whose card declines three times at 11pm, the digital nomad who asks if they can just pay in USDC — an answer any hostel on a remote-work route has needed since crypto-native travelers became a segment — and the group organizer abroad who'd rather not push a five-figure event booking through correspondent banks and FX spreads. Every "we only take cards" is a booking that goes to the property that doesn't.

Why card rails fail hotels, hostels and B&Bs

None of this is bad luck — it's the design. Card payments are reversible by contract: the network promises the cardholder that a charge can be undone, which is the worst possible property for a business selling perishable room-nights that can't be repossessed or resold after the fact. Between you and your money sits an acquirer that prices every advance booking as high-risk card-not-present volume, holds funds in transit for days, and treats a spike in disputes — routine in travel — as a reason for reserves on your account. Layer the OTA on top and you've added a second intermediary that holds the guest relationship and the money. The rails were built for a cardholder standing at a register — not for a room sold three weeks and two borders away from the front desk.

How Payzum lets you accept crypto payments at your hotel

Payzum is a non-custodial, crypto-only payment processor. Non-custodial means the settlement is the payment: when a guest pays, the funds route directly to a wallet your property controls. Payzum never pools, holds, or touches the money — so there is no processor balance to freeze, no rolling reserve because travel "looks risky," and no OTA-style payout cycle between tonight's guests and tomorrow's payroll.

For bookings, payment links replace the keyed-in card number. The moment a guest confirms dates by email or WhatsApp, you send a link for the deposit; when it confirms on-chain — roughly 0.4 s on Solana, about 2 s on Base or Polygon across the supported networks — the room is genuinely secured, because the payment is final. No expired card at arrival, no authorization that quietly dropped, no no-show debate: a paid deposit is money in your wallet, on your cancellation terms. For groups, retreats and events, expiring invoices with overpayment detection put a real deadline on the block: paid or void, never "the organizer swears the transfer is coming."

At the property, the POS turns any phone or tablet at reception into the terminal. At check-out, the balance plus extras — minibar, tours, late check-out — becomes a fresh QR generated for that exact folio. The guest scans and pays from any wallet, in whatever supported crypto they hold; with auto-convert, everything settles as USDC or USDT, so the nightly rate you quoted is the value that lands. A stablecoin like USDC is issued fully reserved against dollar assets, which is what makes "quote in dollars, keep dollars" work. Each receptionist runs under their own PIN cashier login with per-cashier, per-terminal analytics — so the night shift's close is a report, not a recount.

How it works, step by step

1. Sign up. Create a Payzum account for the property — no acquirer application, no terminal lease, no underwriting questionnaire about your dispute history or "travel merchant" risk category.
2. Connect your wallet. Point Payzum at a wallet the property controls. Every deposit and check-out settles there directly; turn on auto-convert so everything lands as USDC or USDT regardless of what the guest paid with.
3. Set up bookings and the desk. Save payment-link and invoice templates for deposits, balances and group blocks; open the POS on the phone or tablet already sitting at reception and create a PIN cashier for each receptionist and shift.
4. Run the stay. Deposit by link at booking, QR at check-out for the balance and extras, invoice for the wedding block — each payment final, non-reversible, and already in your own wallet before the guest reaches the parking lot.

Use cases in a hotel, hostel or B&B

The same building blocks cover every way a property actually collects:

• Direct-booking deposits that stick: a guest emails asking for three nights in August. Instead of keying their card into the PMS, you reply with a payment link for the deposit. It confirms in seconds and it's final — the no-show risk on that room just went to zero, and the OTA never touched the booking.
• Check-out at the front desk: the folio — room balance, minibar, the tour you arranged — becomes a fresh QR on the reception phone. The guest pays from their wallet and the confirmation lands before the receipt prints. No imprint, no signature, no dispute window trailing the stay.
• Hostels on the nomad route: digital nomads and crypto-native backpackers are the guests who already hold USDC and actively pick properties that take it. A QR at the desk and a "we accept USDC/USDT" line on your site is a differentiator that costs nothing to run.
• International guests without card roulette: the foreign card that declines at 11pm stops being your problem. The guest pays from a wallet; there's no issuing bank, no FX surcharge dispute, no "call your bank" at the desk.
• Groups, retreats and events: send the organizer an expiring USDC invoice for the room block or the wedding weekend. If it isn't paid by the deadline, the invoice expires and the rooms release automatically to be sold again; if it is, the money is final and overpayment detection keeps the folio clean.
• B&Bs and small properties with no front desk at all: the owner's phone is the terminal. Confirm the booking with a link from the kitchen table, take the balance with a QR at breakfast — no PMS integration, no card machine rental for a six-room house.
• Multi-shift receptions: PIN cashiers give the morning, evening and night staff their own logins, and per-cashier, per-terminal analytics show who collected what — clean handovers and less end-of-shift ambiguity.

And one more that's arriving fast: guests whose AI agents do the booking. Agentic travel — where an assistant searches, books and pays for rooms in USDC over the x402 protocol — already went live at scale this year. Properties that settle in stablecoins today are the ones positioned for reservations that arrive with the payment already made.

Payzum vs cards and OTAs — side by side

Common objections, answered

My guests don't hold crypto — is this worth setting up?

Run it alongside the card terminal and the OTA channel, not instead of them. The links and QR become the option for the cases where they pay off most: deposits you currently can't make stick, international guests whose cards fail, group invoices, and the growing slice of travelers — nomads, crypto-native tourists, agent-assisted bookers — who actively prefer paying in USDC. Everyone else books as they always have. It's an added rail with near-zero setup cost, not a switch.

What about cancellations and refunds if payments can't be reversed?

A cancellation is a policy question, not a payments question — and it becomes your policy decision instead of an issuer's ruling. You still honor whatever terms you publish: free cancellation to a date, partial refunds, credit toward another stay. The difference is that you refund from your own wallet, on the schedule printed on your confirmation email, rather than a card network deciding months later with the money already pulled back.

Is the money safe if Payzum never holds it?

That's precisely what makes it safe. Because Payzum is non-custodial, there is no pooled processor balance to freeze and no reserve to withhold — payments settle straight to the property's own wallet. The account is protected with 2FA, signed webhooks, and a full audit log.

Won't the price move between booking and arrival?

No — quote in dollars, settle in dollars. Rates are denominated in stablecoins, and auto-convert turns any other supported crypto into USDC or USDT on arrival. A $600 booking settles as $600 of stablecoins whether the guest paid last month or at the desk, not as a coin that might move overnight.