Accept crypto payments for your vacation rental
Key takeaways
- Every host who builds a direct-booking channel to escape the platform's commission inherits the platform's hardest job: collecting advance payment for travel, card-not-present, from a guest who is foreign by definition — the exact profile card acquirers price as high risk.
- The card rail fails this business at both ends: the booking (foreign cards tripping 3-D Secure at your checkout while the guest gives up and books through the platform anyway) and the deposit (pre-auth holds that decline foreign debit cards, linger for a week after checkout, and earn the one-star review).
- A chargeback on a completed stay is the worst dispute in commerce: the night was sold, the apartment was cleaned and worn, and months later the revenue is pulled back by someone reading photos of a flat they never saw. Card dispute windows are measured in months, not nights.
- Payzum is a non-custodial, crypto-only processor: hosted checkout behind your own “Book direct” button, no-code payment links that close a WhatsApp inquiry, invoices with expiry and a unit+dates reference for balances and monthly stays, recurring subscriptions for mid-term nomad rentals, and CSV mass payouts for cleaners, co-hosts, laundry and monthly owner remittances — settled straight to wallets you control.
- Honest scope: there is no pre-authorization on-chain — a security deposit on this rail is real money in your wallet, refunded by you, net of deductions, under the rental agreement the guest signed. And no payment rail touches your licence number, tourist tax, guest registration or building rules. Those stay yours.
Why direct bookings are the hardest money a vacation rental collects
A vacation rental looks like a hospitality business, but it settles like an import/export firm run from a phone. The product is a prepaid, perishable night in one country, sold months ahead to a payer in another, with a damage risk attached and a cleaning crew booked against the calendar.
Four structural facts shape every payment the operator ever receives.
First, the platform toll — and the platform payout calendar. Listing platforms take a commission on every booking, and hosts feel every point of it, which is why the direct-booking movement exists: a website, a booking engine, repeat guests invited to book direct next time. But the platform was never only marketing — it was also the payments department. It vetted the card, absorbed the fraud, held the money and paid out on its own schedule, typically after check-in. Leave it, and the payments department is now you.
Second, the guest is structurally foreign. Tourism is the business of other people's countries — the World Bank counts international tourist arrivals in the billions per year. For a vacation rental in any destination market, the direct payment is cross-border by default: foreign cards, cross-border interchange, FX spread, an issuer's fraud model that has never seen your booking engine before, and a 3-D Secure challenge sent to a phone that may be roaming.
Third, the stay is prepaid and perishable. The balance is due before arrival; a night unsold tonight is not sold tomorrow. So the money must arrive — whole, confirmed, on time — before a stranger receives a door code. Every rail that settles in “1–3 business days”, or that can un-settle for months afterwards, is structurally wrong for this trade.
Fourth, the revenue runs through a payout stack. Behind every check-out there is a cleaner paid per turnover, laundry, a maintenance call, sometimes a co-host on a percentage — and if you manage units for owners, a monthly remittance per owner, quite often to an owner who lives abroad. The collection problem and the payout problem are the same problem, run in opposite directions.
Five revenue lines that behave nothing alike
Direct bookings. The business you are trying to build: deposit at reservation, balance before arrival, sold from your own website or closed in a WhatsApp or Instagram conversation with a past guest.
Security deposits. A refundable amount held against damage — the payment that card rails handle worst, because a pre-auth declines the foreign debit card, expires if the stay is long, and lingers on the guest's statement after checkout.
Extras. Early check-in, late check-out, airport pickup, mid-stay cleaning, the crib, the parking spot — small amounts sold at odd hours, usually over chat.
Monthly and mid-term stays. The digital-nomad month, the winter-escape season, the relocated worker waiting for a lease — rent-sized amounts, recurring, paid by people who by definition do not have a local bank account yet.
Owner-side money. For managers: management fees collected, and net rent remitted owner by owner, month by month — each one a transfer with its own fee and its own reconciliation line.
What the current rails actually cost you
The direct booking that dies at your checkout. A past guest found your site, picked dates, and is holding a foreign card at your payment page. The issuer challenges the charge — unfamiliar merchant, another country, travel-sized ticket — the 3-D Secure code goes to a number that doesn't answer, and the guest does what humans do: gives up and books the same dates on the platform. You just paid the commission you built the website to avoid, plus the marketing that brought them to you.
The chargeback after checkout. The stay happened. The apartment was cleaned twice, the towels aged a little, the keys were handed back. Months later a “not as described” or “unrecognised transaction” dispute arrives — filed from another country, judged by someone comparing your listing photos to a claim, inside dispute windows the Visa Core Rules measure in months. Your evidence is a message thread and a check-in photo. The night, meanwhile, was never re-sellable.
The processor that freezes the season. Advance payment for travel, card-not-present, seasonal spikes, cross-border cards: to an acquirer's risk model, a direct-booking host looks like a textbook high-risk merchant. The polite versions are a rolling reserve and conservative terms; the impolite one is a frozen balance in the week your peak-season payouts were due.
The deposit dilemma. Hold a real pre-auth and you lose bookings — many foreign debit cards cannot carry it, and the ones that can show a blocked amount for days after checkout, which reads as “they kept my money” in a review. Skip the deposit and you absorb the broken glass shelf yourself. Most hosts quietly do the second and call it a cost of doing business.
The monthly stay paid by wire. The nomad booking a month in your one-bedroom pays by international transfer: it leaves on Monday, lands on Thursday — or the next Monday — arrives short after intermediary deductions, and reconciles as an unlabelled amount you match to a booking by hand. Meanwhile the calendar is blocked and three other inquiries were declined.
The payout stack, transfer by transfer. Month-end: six cleaners paid per turnover, the laundry service, the handyman, a co-host's percentage, and nine owners' net rent — two of whom live in another country. Each is a separate transfer with its own fee, cut-off and typing exercise; the international ones cost real money and arrive whenever they arrive.
Why cards, wires and the platforms each break on short-term rentals
None of these rails is badly built. Each one assumes something a vacation rental violates.
The platforms assume you rent their payments with their marketing. The commission buys distribution and a payments department, bundled — there is no “distribution only” tier. The moment a guest books direct, the bundle is gone and nothing replaces the payments half.
Cards assume a local payer and a disputable deliverable. The dispute framework was designed around goods with tracking numbers and payers in the same country as the merchant. A cross-border, card-not-present advance payment for a stay that is consumed and gone is the opposite of that design — which is why it is expensive where it is possible, and classified as high-risk where it is not.
Pre-auths assume short holds on deep cards. A security hold works for a hotel chain batching against corporate credit cards. It fails on a foreign debit card, on a 28-night stay that outlives the hold, and on a checkout Friday night when nobody releases it until Monday.
Wires assume the deadline is administrative. A wire has a value date and a correspondent chain; your deadline is a calendar night that dies at midnight. We wrote the general version in getting paid from abroad without a bank account — a vacation rental is that article with a check-in time attached.
All of them assume the guest's money can leave home easily. A real share of long-stay guests — and of the owners you remit to — bank in countries with capital controls and unusable official exchange rates. Many already hold dollar stablecoins for exactly that reason. Today your booking engine gives them nothing to point that balance at.
How Payzum lets a vacation rental accept crypto payments — booking, deposit and payout
Payzum is a non-custodial, crypto-only payment processor. Both halves matter here.
Non-custodial means the money never sits in a Payzum balance. A booking goes from the guest's wallet straight to wallets you control. There is no platform payout calendar, no processor float, no rolling reserve priced against a “travel advance payment” risk profile, and no balance a risk desk can freeze in August. The settlement is the payment.
Crypto-only means the rail is on-chain and the payment is final once confirmed — roughly 0.4 seconds on Solana, around two seconds on Base and Polygon. A guest can pay a balance from nine time zones away at their midnight, and the door code goes out before they close the laptop. Auto-convert everything to USDC or USDT and “crypto” never means price movement — see USDT vs USDC for payments for how the two differ.
The instruments, mapped to how a rental actually bills
- Hosted checkout — the “Book direct” button. The flagship for this vertical. Behind your booking engine's pay step, a checkout the guest completes in any of the supported chains, confirmed in seconds, with no foreign-card decline tree. The direct channel finally has a payment rail that doesn't leak bookings back to the platform.
- No-code payment links — the WhatsApp closer. Half of direct business is closed in chat: the past guest asking for March, the referral from a neighbour, the influencer's follower. Send a link for the reservation deposit in the same thread, another for the balance six weeks out. No website required at all.
- Invoices with expiry, reference and overpayment detection. For balances and monthly stays: unit + dates as the reference, expiry aligned to your cancellation policy or the calendar-release date, and detection of the guest who rounds up or pays two months at once. The payment arrives whole — no intermediary deductions — and reconciles itself.
- Real security deposits instead of fragile holds. Honest scope: there is no pre-authorization on-chain. A deposit here is actual money in your wallet — which means it never declines, never expires mid-stay and never lingers on a statement. The flip side is real responsibility: you refund it yourself, net of documented deductions, under the rental agreement the guest signed. It is the same honesty note we made for car rentals: the deposit is the recourse instrument — size it, and paper it, accordingly.
- Recurring subscriptions — rent that doesn't die on a reissued card. Mid-term and monthly stays billed as a subscription that ends when someone cancels it, not when a bank reissues plastic to an address the nomad left. The failure mode is the one we covered in crypto subscriptions without chargebacks.
- POS with a fresh QR per sale and PIN cashiers. For operations with a human touchpoint — greeters, a small reception, a tour desk in the lobby of an aparthotel: extras, late checkouts and bike rentals settle on a QR on any phone, one PIN per staff member, per-cashier analytics. Mechanics in turning a phone into a crypto POS.
- CSV mass payouts and EVM stablecoin payouts. One file at month-end — cleaners per turnover, laundry, maintenance, co-host percentages and the net rent for every owner, including the two who live abroad — on Polygon, Arbitrum, Optimism, Base, BNB Chain or Avalanche, plus BTC/LTC/DOGE batches. The format is walked through in bulk crypto payments by CSV.
- REST API with signed webhooks. Your property-management system learns the instant a balance confirms: the smart-lock code is generated, the check-in instructions go out, the calendar closes — at 23:40 on a Saturday, with nobody awake on your side.
What actually happens when the balance clears
The invoice for the balance carries the unit and the dates; the guest pays it from wherever they are; it confirms in seconds. The signed webhook tells your PMS, which issues the door code and sends the arrival guide. The money is in your wallet — not in a platform's payout queue, not in an acquirer's settlement batch, not in transit between correspondent banks. The night was sold, and it stays sold: on-chain finality means there is no dispute window trailing the stay.
The change is not primarily about speed. It is that the direct channel stops being the risky channel. Today, direct is where the commission savings live and also where the declines, the disputes and the deposit friction live. This rail removes the second list.
Honest scope: finality cuts both ways
No chargebacks also means no reversals. Refunds under your cancellation policy become payments you initiate, from your wallet, per the terms the guest agreed to at booking. That is more control than a card rail gives you — and more responsibility, because the rental agreement is now the whole agreement. Write the cancellation ladder, the deposit deductions and the no-show rule down, and have the guest accept them before paying. Where local consumer rules regulate deposits or cancellation refunds, they bind you exactly as before.
What this rail does not do
Payzum is a payment rail. It is not your short-term rental licence or registration number, your tourist-tax collection and remittance, your guest-registration duty with local authorities, your building's rules, your insurance or your tax return. Nothing about how a guest pays changes a single one of those obligations — and no payment rail fills an empty calendar. What it removes is the narrower, expensive category: direct bookings that were fully intended and were declined, reversed, frozen or delayed by the instrument.
Volatility is a setting, not a risk
The objection every host raises first: “my mortgage and my cleaners are in dollars or euros — I can't hold something that moves.” You don't have to. Accept whatever the guest holds and auto-convert to a dollar stablecoin — USDC or USDT — so what lands in your wallet is a dollar amount against a dollar-priced calendar. The chain is the transport; the stablecoin is the unit of account.
How it works, step by step
- Connect your wallets. Create the Payzum account and point it at wallets you already control — managers often use one per owner or per building so statements stay clean. Turn on auto-convert to USDC or USDT and enable 2FA. Nothing ever sits with Payzum.
- Put hosted checkout behind “Book direct”. Your booking engine's pay step redirects to (or embeds) the checkout; the guest pays in seconds from any supported chain.
- Template your links and invoices. A deposit link and a balance invoice per booking — unit + dates as reference, expiry aligned to your cancellation policy, overpayment detection on. Send them in the same WhatsApp thread where the inquiry arrived.
- Decide your deposit policy. A real stablecoin deposit per stay, sized to the unit, refunded on inspection per the signed agreement — or no deposit for trusted repeat guests. Either way, write it down.
- Put subscriptions behind monthly stays. Mid-term guests are billed monthly with nothing behind the charge that can expire or be reissued.
- Connect your PMS. REST API and signed webhooks: confirmed payment → door code, arrival guide, calendar block — automatically.
- Run the month-end from one file. Cleaners, laundry, maintenance, co-hosts and owner remittances in a single CSV — verifying any changed payee details out of band before sending. Same rail, opposite direction.
Use cases at a vacation rental operation
Five situations that happen in every direct-booking operation, and what each looks like on this rail.
- The repeat guest who books direct at midnight. Last summer's guest writes on WhatsApp asking for the same two weeks. You send a deposit link in the thread; she pays it from her phone; the balance invoice, expiring six weeks before arrival, follows automatically. No platform in the middle, no foreign-card decline, and the commission you saved is real margin, not a churn risk.
- The deposit that stopped being a fight. A €500 hold used to decline half the foreign debit cards you saw. Now it is a real stablecoin deposit, paid with the balance, held in your wallet, and refunded two hours after the checkout inspection — an outbound payment the guest watches arrive, instead of a blocked amount they watch linger.
- The nomad month from a capital-controlled country. A remote worker from Buenos Aires books your one-bedroom for October. His pesos cannot legally buy a wire at any sane rate — but he is paid in USDC and has been for two years. Your monthly invoice is the first rent he can pay without a currency workaround; it arrives whole, referenced, in seconds.
- The chargeback that never came. The guest who broke the lamp and left a bad review used to dispute the whole stay on top — and win, months later, against your photos. On this rail the stay was final at confirmation; the lamp came out of the deposit with an itemised note; the review is just a review.
- Month-end for nine owners and six cleaners. One CSV: every cleaner's turnovers, the laundry invoice, the handyman, the co-host's percentage, and each owner's net rent — including the owner in Madrid and the one in Miami — settled the same afternoon, each line referenced, with no per-wire fees eating the smaller payouts.
Payzum vs platforms, cards and wires for a vacation rental
| What matters at check-in | Platforms, cards and wires | Payzum |
|---|---|---|
| Commission on a direct booking | Platform commission avoided, replaced by card fees + cross-border + FX on the direct sale | Network fees measured in cents, whatever the guest's country |
| Where the money lands | Platform payout after check-in; card money via the acquirer 1–3 days later | Directly in a wallet you control — non-custodial, nothing held back |
| Foreign guest at your checkout | 3-D Secure challenges, issuer declines, the booking leaks back to the platform | Pays from any supported chain; confirms in seconds — ~0.4s on Solana, ~2s on Base and Polygon |
| Dispute after a completed stay | Card chargeback windows measured in months; photos vs claims | Final on confirmation — no chargebacks; refunds are payments you initiate per your policy |
| Security deposit | Pre-auth declines foreign debit, expires on long stays, lingers after checkout | A real stablecoin deposit in your wallet, refunded on inspection per the signed agreement |
| Monthly / mid-term stay | International wire: days late, arrives short, matched by hand | Invoice or subscription with unit+month reference — whole, in seconds, self-reconciling |
| Seasonal risk review | Rolling reserves and frozen balances at peak season | No custodial balance exists to freeze |
| Paying cleaners, co-hosts and owners | A stack of individual transfers, fees and cut-offs — worse when the owner lives abroad | One CSV batch, EVM stablecoin payouts, same day |
Common objections, answered
“My guests don't hold crypto.”
Most don't, and this is not for them — run it alongside the rails you already accept. It is for the slice that is already painful: the foreign guest whose card your checkout keeps declining, the nomad from a capital-controlled economy who is paid in USDC, the long-stay guest whose wire always arrives short, and the owner abroad waiting on a remittance. That slice is small in guests and large in revenue.
“The platform handles all this for me. Why bother?”
If all your business comes from the platform and the commission doesn't bother you, keep it — this rail is for the direct channel you are building precisely because the commission does bother you. Direct bookings without a payments rail built for foreign payers is a website that leaks its conversions back to the platform at the last click.
“Is a real deposit better than a hold? It feels heavier.”
It is different, and honestly so. A hold is lighter for the guest until it declines their debit card or sits on their statement for a week; a real deposit is money that moved, visibly, both ways. Operators who switch tend to size deposits more carefully, document the unit's condition better, and refund fast — because the refund is now a visible payment that guests screenshot next to their five-star review.
“What does my accountant do with rent in USDC?”
A booking collected in USDC is rental revenue, recorded on the day it is received at that day's value, against the unit and the dates — the same as any receipt, and easier to reconcile because the reference travels with the payment. Your licence, tourist tax, guest registration and income tax are unchanged. Confirm the details for your jurisdiction with your own advisers; we are a payment rail, not your compliance department.
Frequently asked questions
How does a vacation rental accept crypto payments for direct bookings?
Through Payzum, the host puts a hosted checkout behind the “Book direct” button and sends payment links or invoices for deposits and balances, referenced to the unit and dates. The guest pays in stablecoins from anywhere; the payment confirms on-chain in seconds and lands directly in a wallet the host controls — Payzum never holds the funds.
Can a guest charge back a stay after checkout?
No. On-chain payments are final once confirmed, so there are no chargebacks against a completed stay — no “not as described” dispute months later, no deposit clawed back after a cancellation. The flip side: refunds under your cancellation policy are payments you initiate from your own wallet, under the terms the guest accepted at booking.
How do security deposits work without a card pre-authorization?
There is no pre-auth on-chain, and Payzum is honest about that: a deposit is real money paid into your wallet with the balance. It never declines a foreign debit card and never lingers on a statement; after the checkout inspection you refund it, net of documented deductions, as a payment the guest sees arrive in minutes.
Can a digital nomad pay a monthly stay in stablecoins?
Yes, and it is one of the strongest cases for this rail. Mid-term guests are often paid in USDC already, or hold dollar stablecoins because their home banking system is capital-controlled. A monthly invoice or recurring subscription with the unit and month as reference arrives whole, in seconds — instead of an international wire that lands late and short.
What about crypto volatility on a season's worth of bookings?
Turn on auto-convert to USDC or USDT. You accept whatever the guest holds, and what lands in your wallet is a dollar-denominated stablecoin amount matching your dollar- or euro-priced calendar. The blockchain is the transport; the stablecoin is the unit of account.
Can I pay cleaners, co-hosts and property owners on the same rail?
Yes. Payzum does mass payouts from one CSV file — cleaners per turnover, laundry, maintenance, co-host percentages and monthly owner remittances, including owners who live abroad — in stablecoins on Polygon, Arbitrum, Optimism, Base, BNB Chain or Avalanche, plus BTC/LTC/DOGE batches, settled the same day.
Book 20 minutes and we'll design it for your rentals
Every short-term rental operation runs payments differently: a single flat closed over WhatsApp or a portfolio with a booking engine, real deposits or repeat-guest trust, nightly tourists or monthly nomads, your own units or nine owners expecting statements. Book a short call with our payments team and we'll map exactly how you would collect each of those — and how the month-end payout run would go out — in stablecoins, non-custodial, to wallets you control.
If the calendar does not load, book directly here · [email protected]
This article is general information about payments, not legal, financial or tax advice. Short-term rental licensing and registration, tourist and occupancy taxes, guest-registration duties, security-deposit and cancellation consumer rules, building and zoning restrictions, insurance and tax are regulated differently in every jurisdiction and remain entirely your responsibility. Confirm the rules that apply where you operate with your own advisers.