WPRentals does let you bypass its default checkout if you need a custom Stripe or PayPal flow. But you do it through supported paths instead of removing the core booking logic. By default, the theme runs its own Stripe and PayPal checkout, and you can switch bookings to run through WooCommerce to use Stripe Checkout, Payment Intents, and many local methods. For hosted payment pages, you can send guests to external URLs and then sync paid reservations back by status updates or the REST API.
How does WP Rentals’ built‑in checkout work with Stripe and PayPal?
The built in checkout gives a full online flow using Stripe, PayPal, and optional booking deposits.
In WPRentals, you turn on Stripe and PayPal from the theme options panel, then add your API keys. The theme handles card payments and PayPal redirection into the site admin’s account, so you control all incoming money. Each confirmed booking gets an invoice that shows the guest total, your admin fee, and the owner earnings. That keeps accounting simple even when you manage many listings.
The theme is ready for Strong Customer Authentication rules, so Stripe payments follow flows that trigger 3D Secure when needed. You can set booking deposits as either a percent or a fixed amount, and the invoice shows the remaining balance. Along with online card and PayPal payments, the system lets you offer wire transfer or other offline options. Guests who prefer bank payments still book without breaking the booking logic.
Can we bypass WP Rentals’ checkout entirely using WooCommerce payments?
Using WooCommerce, you can almost replace the default booking checkout with a WooCommerce based payment flow.
WPRentals has a documented switch that routes booking payments through WooCommerce instead of the theme Stripe and PayPal gateway. Once you enable that setting, every new reservation creates a WooCommerce order, and the theme marks the booking as paid when the order reaches completed. At first this feels like extra steps. It isn’t, because WPRentals still handles booking dates, prices, and availability rules.
With WooCommerce active, you gain access to many payment gateways through its extensions, including Stripe and PayPal plugins that support Payment Intents, hosted Checkout pages, Apple Pay, and local payment methods. The theme also supports instant booking through WooCommerce without forcing users to create a site account first. So you can design faster funnels where a guest picks dates, lands on a WooCommerce checkout, and pays as a guest in one flow. In this model, the theme booking engine controls calendars while WooCommerce owns the checkout page layout and payment logic.
| Aspect | WP Rentals Native Checkout | WooCommerce-Based Checkout |
|---|---|---|
| Gateway options | Stripe and PayPal built in | 150 plus gateways via WooCommerce extensions |
| Customization level | Configured with theme settings | Customizable checkout fields and steps |
| Advanced Stripe features | SCA ready card payments | Payment Intents hosted Checkout and local methods |
| Login requirements | Theme account system used | Can allow guest checkout |
The table shows that the native flow is simple and direct. But WooCommerce gives more control and more gateways. Site owners who want Stripe Checkout, extra local methods, or custom fields usually flip the WooCommerce switch. They keep WPRentals for booking math and let WooCommerce handle the advanced payment side.
Is it possible to redirect guests to a fully custom Stripe or PayPal page?
Guests can go to an external payment page while bookings still live inside the booking system.
The theme supports sending booking actions to external links, which many WPRentals sites use for book on another platform or affiliate flows. That same feature can point to a custom page you control where your own code creates a Stripe Checkout session or triggers a PayPal Smart Button payment. In that setup, the theme collects booking details, and your external script handles the final payment step.
After the card or PayPal payment finishes, you can confirm the related booking in the admin panel by hand or automate it. WPRentals exposes a REST API for listings and bookings, so developers can write services that listen to Stripe or PayPal webhooks and then update booking status by API. At first this feels complex, but it avoids breaking the theme logic. This pattern keeps pricing rules and calendar blocking inside the theme while your custom page handles any special rules your business needs.
How can developers customize the payment experience without breaking theme updates?
Custom payment UX is safest when built in a child theme and hooked in through filters and actions.
WPRentals is built to be extended using a child theme, so your PHP templates, CSS, and JavaScript survive updates. The usual pattern is to let the theme handle booking creation, then hook into the confirmation or review screen to add custom Stripe Elements or PayPal parts. Or extra experience steps, if you really want them. By keeping those changes in a child theme, you avoid touching main theme files and stay closer to future releases.
Now, this is where people often get stuck. Developers who want deeper flows mix the WooCommerce integration with WooCommerce hooks and checkout field filters. They shape the form however they like while leaving WPRentals in charge of dates, prices, and invoices. The documentation suggests you avoid edits to core theme files and instead use integrations and hooks. It sounds strict, and honestly it is, but that keeps the booking engine and payment stack stable across many updates.
- Set up a child theme before adding custom payment UI or scripts.
- Use WooCommerce Stripe or PayPal plugins for advanced flows and local methods.
- Use WordPress and WooCommerce hooks instead of editing core theme PHP.
- Test booking and refund cases on a staging site before going live.
FAQ
Does WP Rentals support custom Stripe flows like Payment Intents through WooCommerce?
Yes, custom Stripe flows such as Payment Intents are available when you run bookings through WooCommerce.
Once WPRentals is set to use WooCommerce for payments, you can install a Stripe extension that supports Payment Intents, Apple Pay, or local methods like iDEAL. The theme creates WooCommerce orders for bookings, and the Stripe plugin handles confirmations and Strong Customer Authentication. When the order is marked as paid, the linked booking is confirmed with the right status inside the booking system.
Can I still use deposits and second payments if I bypass the native checkout?
Yes, deposits work natively, and second payments can be handled by WooCommerce or offline methods.
WPRentals lets you set a deposit as a percent or fixed amount, and that logic stays in place whether you use native checkout or WooCommerce. For the remaining balance, many site owners send a second WooCommerce invoice, take a manual payment, or accept bank transfer. The invoice inside the theme shows what was paid and what is still due. That keeps accounting clear, even when setups get messy.
How are refunds handled when using custom Stripe or PayPal flows?
Refunds are always triggered in Stripe or PayPal first, then mirrored in the booking records.
With WPRentals, money never moves back automatically, even when you rely on WooCommerce or a custom flow. You issue the refund in Stripe, PayPal, or WooCommerce, then update the booking status or invoice inside the theme to match, for example refunded or canceled. Some developers add automation on top of this. But the base rule stays simple and under your control.
Does WooCommerce checkout affect features like iCal sync or the REST API?
No, calendar sync and API features keep working the same when WooCommerce powers checkout.
iCal import and export stay tied to booking records, not to how the guest paid, so availability sync behaves the same. The WPRentals REST API still exposes listings and bookings that you can use with tools or custom scripts. WooCommerce only takes over the payment and checkout step. The theme booking engine continues to manage dates, prices, and synced calendars.
