How to Set Up Stripe for Vacation Rental Direct Bookings

A guest lands on your booking page, picks their dates, enters a card, and gets a confirmation email before they've closed the tab. That's the whole point of a Stripe setup for a vacation rental. No PayPal invoices chased over email. No bank transfer that clears in three days while the guest gets cold feet. Money in your account, booking locked, done.

Below is the setup I'd walk a friend through if they'd just built a direct site and wanted to take a card by the weekend.

How do I set up Stripe for vacation rental direct bookings?

Create a Stripe account, verify your business and identity, connect your payout bank account, then link Stripe to your booking platform (most connect in minutes with an API key or a one-click button). Set your currency, configure a deposit or full-payment charge, and run one live test booking before you go public.

1. Create the account and pick the right entity type. Go to stripe.com and sign up. When it asks whether you're an individual or a company, answer honestly. If you run rentals under your own name, individual is fine. If you've got an LLC or Ltd, use that, because the payout name has to match the bank account name or Stripe holds your money. What goes wrong here: people pick "company" because it sounds more professional, then their sole-trader bank account name doesn't match and payouts freeze on the first transaction.
2. Verify your identity. Stripe will ask for a photo ID and sometimes a selfie. Do this on day one. Verification can be instant or it can take two days if a document is blurry. You do not want a guest trying to pay a €1,400 booking while your account is still "pending review."
3. Add your payout bank account. Enter the account that receives your money. Double-check the sort code / routing number. A single wrong digit means the first payout bounces and sits in limbo for a week.
4. Set your payout schedule. Default is usually a rolling 2-7 day delay, then daily automatic payouts. I leave mine on automatic daily. Some hosts switch to weekly to make bookkeeping cleaner. Your call. The first payout always takes longer (7-14 days) because Stripe is checking you're legit. Expect that, don't panic.
5. Connect Stripe to your booking system. This is where the magic happens. Most direct-booking tools have a Stripe button in settings. Click it, log into Stripe, approve, and you're linked. If you built a custom site, you'll paste a publishable key and a secret key. Keep the secret key secret. Never put it in front-end code.
6. Configure the charge. Decide: full payment at booking, or a deposit now with the balance auto-charged 30 days before check-in? For stays over €500 I take a 30% deposit and schedule the balance. Higher conversion, and the guest isn't hit with one scary number.
7. Run a live test. Book your own place with a real card for the smallest amount you can. Watch the confirmation fire, check the money appears in Stripe, then refund yourself. Yes, you'll pay a few cents in fees. Worth it to know the whole chain works.

What does Stripe actually cost a host?

Standard Stripe pricing in most regions is around 2.9% plus €0.30 (or $0.30, or 1.5% + 20p in the UK for European cards) per successful charge. On a €1,000 booking that's roughly €29.30. Compare that to what Airbnb and Booking.com take.

I ran the numbers on a €1,000 booking once and it stuck with me. Booking.com's commission plus the guest-side fees can strip 15-18% out of the same reservation. Stripe took under 3%. That gap is the entire reason direct booking exists. If you want the full breakdown, I went deep on it in this post on OTA fees versus direct booking.

Watch two extra costs. Currency conversion adds about 1% if a guest pays in a foreign currency and you convert. And chargebacks cost €15-25 each if a guest disputes. Rare, but budget for one a year.

Are there hidden fees?

Not really hidden, but easy to miss. International cards can carry a small surcharge. Instant payouts (getting money in minutes instead of days) cost around 1% extra. I never use instant. The daily payout is fast enough and free.

Handling refunds without losing your mind

A guest cancels three weeks out. Your policy says 50% refundable. You open the payment in the Stripe dashboard, click refund, type the partial amount, done. The card gets credited in 5-10 business days.

One thing that catches people: Stripe does not return the processing fee on refunds anymore. They changed this. So if you refund a €1,000 booking in full, you eat the ~€29 you already paid. Build that into your cancellation policy. I state cancellation terms clearly on the booking page and in the guest's confirmation, which kills most disputes before they start. Your direct booking site checklist should have a visible cancellation policy near the payment step, not buried in a footer.

Set your policy inside your booking software, not just in Stripe. Stripe processes the money. Your booking platform enforces the rules and calculates the refundable portion.

Taxes and what Stripe reports

Stripe is a payment processor. It is not your accountant and it does not collect lodging tax for you. Two separate things matter here.

Income reporting: Stripe gives you a full transaction history and, in the US, a 1099-K if you cross the threshold. Download the monthly reports. Hand them to whoever does your books. Do not reconstruct a year of bookings from memory in April.

Lodging / occupancy / tourist tax: This is on you or your booking platform. Some tools let you add a tax line to each booking so the guest pays it and it lands in your Stripe balance, then you remit it to the city. If your area charges 5% tourist tax, add it as a separate line so it's transparent and you're not paying it out of your own margin. Check your local rules. A coastal town in Spain handles this very differently from a county in Texas.

Stripe Connect vs standard Stripe: which do you need?

If you're a single host taking payments for your own properties, standard Stripe is all you need. Stripe Connect is for platforms that route money to multiple other people, like a property manager collecting for several owners and splitting payouts. Most independent hosts never touch Connect. If you manage other people's places and pay them out, that's when Connect earns its keep.

Common setup mistakes I see

• Going live before verification finishes. Guest pays, money sits in a pending account, guest emails you worried. Verify first.
• Mismatched account names. The single most common reason payouts freeze. Match the entity name to the bank name.
• No test booking. You find out the confirmation email doesn't fire when a real guest tells you they never got one.
• Ignoring 3D Secure. European cards trigger a bank verification popup. Make sure your integration supports it or European payments silently fail.

Once Stripe is running, the rest of the direct-booking machine falls into place. Payments are the piece hosts fear most, and it's genuinely the easiest part now. If you're still deciding whether to build the site at all, I made the case for it in why every host needs a direct booking website.

Set it up on a quiet afternoon. Test it with your own card. Then let the next booking come straight to you, fee-light and OTA-free.