How to accept card payments from your vacation rental website
This guide is for hosts who already want direct bookings and are ready to add guest card payments without turning the rollout into a big project. It covers the full host flow: preparing one booking-ready rental, connecting payouts, finishing verification, choosing how guests pay, and testing the real website flow before you invite guests to use it.
Why hosts add guest card payments
Accepting card payments means a guest can pay for a stay directly during your website’s booking flow instead of you collecting payment by bank transfer, cash, or an external link. RentalBeam connects this to Stripe Connect so the money goes straight to your payout account.
Direct booking requests are a strong first step, but many hosts eventually want a smoother way to collect deposits, confirm a stay faster, or let a guest complete payment without back-and-forth messages. The goal is simple: give your website a real direct payment path when a guest is already ready to book.
- Capture higher-intent guests while they are still on your site
- Collect deposits or full payment without sending guests back to an OTA
- Keep your guest communication and website brand experience tighter
- Reduce manual payment chasing when the host flow is already clear
- Choose between inquiry-first, request-now-bill-later, or pay-in-widget flows
Payment setup works best after availability is already dependable
Make sure your rental setup already feels trustworthy before you ask guests to pay. A confirmed paid booking deserves the same dependable availability foundation as any other direct booking flow.
Card payments vs. bank transfer or cash: what changes
| Guest pays by card (Pro, Stripe Connect) | Guest pays by bank transfer or cash | |
|---|---|---|
| Setup needed | Payout account with Stripe Connect verification | None beyond your usual banking details |
| RentalBeam fee | None | None |
| Card processing fee | Standard Stripe card fee, paid to Stripe | Not applicable |
| Speed | Can complete during the website flow | Depends on how quickly the guest transfers or pays |
| Best paired with | Pay in widget or request now, bill later | Inquiry only or request now, bill later |
What to have ready first
- One live RentalBeam rental with the right iCal sources already connected
- Booking settings that match your real stay rules, fees, and guest policies
- The bank account where payouts should land
- Business and identity details ready if the payout setup asks for them
- A test plan for one real booking request and one real guest payment path
Start with one property, not your whole portfolio
Launch guest payments on the rental that already gets the clearest website traffic or the fewest edge-case requests. Once that flow is proven, copy what worked to the rest of your rentals.
Step-by-step setup
- 1
Prepare one booking-ready rental
- Open the rental you actually want to take direct bookings on
- Confirm your OTA or iCal sources are connected and healthy
- Check the booking form rules, pricing visibility, fees, discounts, and guest limits
- Make sure the rental is the one you want to route paid stays through first
If you still need to finish the booking widget itself, start with the direct booking setup guide.
- 2
Add your payout account in Payments
- Open the RentalBeam dashboard and go to the Payments tab
- Click Add payout account
- Choose the business country for the payout owner
- Complete the guided payout setup flow
Why this step looks like a verification flow
The guided setup asks only for what is currently needed for payments and payouts to go live. In plain host terms, that means the flow may ask for business, identity, or bank information before card payments can be switched on with confidence.Keep it guided, not technical
RentalBeam keeps the host-facing setup inside the dashboard, so your job is to finish the payout details and verification - not to stitch together a technical payment setup by hand. - 3
Finish verification before you depend on live payments
- Return to the payout account if RentalBeam shows Action required
- Upload or confirm any identity, business, or bank details the setup requests
- Wait for the account to move to a ready state before promising instant guest payment
Readiness matters before money moves
Card payments and payouts rely on the payout account being fully ready. If required details are still missing, payment collection or payout delivery can be held back. Do not skip the readiness check. - 4
Assign the payout account to the rental and choose the guest path
- Open the rental’s booking settings
- Pick the payout account that should receive guest card payouts
- Choose whether the rental stays inquiry only, request now bill later, or collects payment right after submission
- Save the rental settings before testing
RentalBeam supports all three host flows: Inquiry only, Request now, bill later, and Pay in widget. You do not have to jump straight to the most aggressive checkout flow on day one.
- 5
Run one real end-to-end test before launch
Which guest path should you start with?
Inquiry only
Best if you still quote manually, want to screen every stay, or are just getting comfortable with direct website demand.
Request now, bill later
Best if you want the guest to commit to the stay first, then send a secure payment request after you confirm the booking details.
Pay in widget
Best when your pricing rules are already reliable, your availability is healthy, and you want the shortest path from guest intent to paid booking.
You do not have to start with instant payment
Many hosts get better results by starting with request now, bill later. It proves guest demand, keeps the flow short, and still gives you a confirmation checkpoint before money moves.
For a deeper comparison of these three flows, see inquiry only vs request now vs pay in widget.
Common mistakes to avoid
- Turning payments on before the rental setup is ready: make sure the dates, rules, and guest flow already feel dependable before you ask a guest to pay.
- Skipping a real guest test: preview mode is not the same as a real checkout or payment request journey.
- Launching the hardest flow first: if your policies or pricing are still evolving, keep the first version inquiry-first or bill-later.
- Forgetting the payout owner: each rental needs the right payout account attached, especially when multiple properties or owners are involved.
- Focusing only on headline fees: payment success also depends on trust, clarity, guest messaging, and how quickly you respond after a request.
What to watch in the first week after launch
Booking quality
Payout readiness
Cost check
When you are ready to go deeper, continue with the Stripe Connect explainer and the monthly fee vs transaction fee guide.