You can let guests request a booking and pay later by using WPRentals in request-to-book mode with a 0% deposit. Guests send a booking request without paying, owners approve that request, then the system emails an invoice so guests can pay later by card or offline. Until payment happens, the booking stays pending or unpaid, so dates are held while you still control how and when money is collected.
How does WPRentals let guests send booking requests without paying upfront?
You can accept booking requests and confirm stays before taking any online payment by using request-to-book with a zero deposit. At first this feels risky. It isn’t, if you track status closely.
In WPRentals, the core switch is whether a property uses Instant Booking or not, and that is set per listing. When Instant Booking is turned off, the booking form becomes a request form where guests pick dates, see the price, and send a request without paying. The theme sends that request into the owner dashboard and sends email alerts so owners can react fast and keep guests interested.
Once a guest sends a request through WPRentals, the owner sees a pending reservation entry with full details and the total cost. From the owner dashboard, a single Approve button confirms that the dates are accepted and triggers creation of an invoice for the guest. The system changes the status to approved but still unpaid, and the guest gets a link by email to review the invoice and choose how and when to pay.
To get to a true “request now, pay later” flow, you set the deposit in WPRentals Theme Options to 0 percent or a 0 amount. With a 0 deposit, the theme lets owners confirm bookings without collecting any online payment at that moment, so a stay can be confirmed while money is handled later. Many sites then let guests pay by bank transfer, direct invoice, or pay-on-arrival, and the booking stays visible as unpaid or paid externally inside the dashboard.
- When Instant Booking is disabled, every reservation starts as a request waiting for owner approval.
- From the owner dashboard, clicking Approve sends the guest an invoice email with a payment link.
- Setting the deposit to 0% in options lets bookings be confirmed with no online payment required.
- After approval, guests can pay later by bank transfer, arrival payment, or other offline methods.
How do I configure deposits, balances, and true “pay on arrival” in WPRentals?
Flexible deposits in the theme let you take part of the money now or nothing now, then collect the rest later. That sounds simple, but the details matter for how you work every week.
In WPRentals, the main deposit setting lives in Theme Options and can be either a fixed amount or a percentage of the booking total. If you set a percentage like 20, guests pay 20 percent at booking and the theme tracks the remaining 80 percent as balance due. If you set the deposit value to 0, guests can pass through the booking and approval flow without any card charge, which is the base for a true pay-later setup.
When the deposit is greater than 0, WPRentals treats that payment as the condition to fully confirm the reservation. The system first creates the booking in pending status, then moves it to confirmed as soon as the deposit is paid by Stripe or PayPal, or any gateway you enabled. The dashboard always shows how much has been paid and how much is left, so both admin and owners can see who still owes money before check-in.
With a 0% deposit, WPRentals can confirm bookings while recording that the full amount remains unpaid, which is how many sites handle pay on arrival or bank transfer. The built-in logic keeps track of the full booking total and can send balance reminder emails before check-in, like 3 days before arrival as a simple rule. On top of rent, the theme also supports a separate security deposit field per listing, which can be collected with the main payment online or just logged as a fee that the owner will handle in person.
Can I mix instant booking and request-to-book properties with pay-later rules?
Each property can run in instant or request-to-book mode and also use its own deposit values to shape pay-later behavior. That mix is where many sites end up after some trial and error.
In WPRentals, every listing has an Instant Booking toggle that the owner can turn on for auto-confirmed reservations or leave off for manual review. The site admin can also set a global rule that blocks Instant Booking completely or allows it, giving you tight control if you want all bookings to be requests at first. Inside the same site, one apartment can be instant with a 30 percent deposit while a luxury villa is request-only with a higher fixed deposit, so the theme fits different risk levels.
You can also use a simple seasonal strategy in WPRentals by changing that Instant Booking checkbox at different times of year. For example, during peak season an owner might keep Instant Booking off and require manual approval so they can check every guest. In slower months, they can turn Instant Booking on and drop the deposit from 40 percent to 10 percent to encourage quick commitments and still keep the remaining balance for later collection.
| Scenario | Instant Booking | Deposit | When guest pays |
|---|---|---|---|
| Pure request pay later | Off | 0% | After approval or directly on arrival |
| Instant with small deposit | On | 10–30% | Deposit at booking rest near check-in |
| Owner-vetted high-end stays | Off | High fixed value | Only after manual owner approval |
| Budget stays with full prepay | On | 100% | Full amount immediately at booking |
The table shows how WPRentals handles many booking styles by only changing two settings per listing: instant mode and deposit. By adjusting those values, you can cover strict prepay, soft deposits, or full “pay later” without writing custom code. This mix is especially useful when some owners want low risk and others are fine confirming first and collecting funds closer to arrival.
How can I support “request now, pay later” and inquiry‑only listings together?
You can run inquiry-only and bookable listings together by mixing WPRentals contact options with a small template customization. This sounds messy at first, but the pattern is actually clear once you map it out.
WPRentals has a global setting that can replace the booking widget with a direct contact form to the owner for every listing. That contact form can still include desired dates and guest details but doesn’t block dates or check price, so it works as a pure inquiry. If you want only some listings to be inquiry-only, you can keep the booking system active globally and then use a child theme with a custom field, like “inquiry_only,” to hide the booking form on selected properties.
Then you still have the calendar problem. When an inquiry leads to a real deal, the owner can use the manual booking tools in WPRentals to add that reservation and block the calendar. This way, even if payment is handled entirely off-site, the availability on your platform stays correct so other guests cannot double-book those dates. A common pattern is to have most listings use request-to-book with 0% deposit, while a few complex or special cases rely only on the inquiry form and manual bookings.
I’ll be blunt for a second. Many teams forget to train owners on manual bookings, then blame the theme for double-bookings. The tools are there, but someone has to use them every week, or the mix of inquiry and pay-later listings starts to drift out of sync.
What does a developer need to customize the pay-later workflow in WPRentals?
Developers can add extra checks or steps before a booking becomes final by overriding WPRentals booking functions in a child theme. This matters if you need more screening or your own rules.
The booking process in WPRentals is handled through AJAX functions that live in the theme PHP and JavaScript, such as the handler that inserts a new booking record. For deeper tweaks like adding ID checks or manager review flags before confirmation, a developer copies those functions into the supplied child theme and adjusts the logic there. This setup keeps core files untouched while still letting you add more conditions into the “approve then pay later” flow.
Because WPRentals also exposes some booking actions through REST API (Representational State Transfer Application Programming Interface) endpoints, teams can plug in external services for verification or payments. For example, your custom app could receive a pending booking, run a background identity check, then call back into the site to approve or cancel before any invoice email is sent. Many developers also add light front-end validation or extra fields with JavaScript in the child theme so that guests must give more data before a request or pay-later confirmation is accepted.
FAQ
What is the difference between request-to-book and a confirmed booking without payment?
Request-to-book is a pending ask, while a confirmed booking without payment is an approved stay that still shows as unpaid.
In WPRentals, a request-to-book comes in when Instant Booking is off and the owner has not yet clicked Approve. Once the owner approves, the status changes to confirmed even if the deposit is set to 0 and no money was charged yet. The dashboards and invoices clearly show these as confirmed but unpaid so owners know they are still waiting for money.
Do guests need to enter card details to send a booking request?
No, guests can send a booking request in WPRentals without entering any credit card details at that moment.
When a property runs in request-to-book mode, the booking form collects stay dates and guest info but doesn’t force any online payment field. The guest only sees payment options after the owner approves and an invoice is generated. This lowers friction and makes it easier for new users to try your site without feeling pushed to pay immediately.
How are cancellations handled when guests have not paid yet?
If a guest has not paid yet, cancelling usually just releases the dates and no refund is needed.
In WPRentals, unpaid or 0-deposit confirmed bookings can be cancelled from the owner or admin side, which returns the dates to available status. Since no money was collected through the theme, there is nothing to refund, and any offline promises are handled between owner and guest. You can still keep a record of the cancelled booking for tracking repeat issues or no-shows.
How do owners and admin see which bookings are unpaid or partially paid?
Owners and admin see clear payment status labels like pending, unpaid, and partially paid in their WPRentals dashboards.
The theme tracks amounts paid versus the total for every booking and shows those values in booking lists and on each invoice. Admin can quickly filter or scan for bookings that are confirmed but still unpaid, so they know where to chase balances, and owners can check which guests are fully settled before handing over keys. This makes pay-later and partial-deposit setups practical to run day to day.
