You add local or alternative payments to a WPRentals booking setup in two main ways. One is to send bookings into WooCommerce so you can use Klarna, iDEAL, or other WooCommerce gateways. The other is to hire a developer to build a custom gateway that works with the theme’s invoice flow. In both cases, WPRentals still creates invoices, blocks dates, and confirms bookings, while the payment service only moves the money.
How does WPRentals handle payments before adding local gateways?
The default setup already supports secure card, PayPal, and offline bank payments without extra plugins.
Out of the box, WPRentals lets guests pay online with Stripe for cards and PayPal, or offline with a wire transfer option. You only add API keys and processor pages, so online payments can be live quite fast. All money from bookings and fees goes into the admin’s Stripe or PayPal account, not to property owners, which keeps the flow simple.
WPRentals uses Stripe Elements with tokenization, so card data goes straight to Stripe and supports Strong Customer Authentication for European cards. For PayPal, the theme uses redirects and IPN callbacks so PayPal handles login and card steps, then notifies the site when payment works. The Wire Transfer method gives guests your bank details, logs an invoice, and waits for you to mark payment as received before final confirmation.
How can I use WooCommerce in WPRentals to add Klarna, iDEAL and local methods?
Sending booking payments through WooCommerce unlocks most common local and alternative payment methods.
Instead of using only the native Stripe and PayPal buttons, you can switch WPRentals to use WooCommerce for booking deposits and listing payments. The theme still creates the booking, blocks the dates, and generates an internal invoice, but the actual Pay Now step moves to a WooCommerce checkout page. Any WooCommerce gateway you install, like Klarna, iDEAL through Mollie, Bancontact, Sofort, or a local bank plugin, then shows as a normal choice.
WPRentals lets you disable its own Stripe and PayPal modules and send every online payment into WooCommerce while keeping booking logic in place. When the guest pays with Klarna, iDEAL, or another method, WooCommerce marks the order as completed, and this change flips the linked WPRentals invoice to paid and confirms the booking. Funds still land in the site admin’s WooCommerce account, and hosts see the booking confirmed in their dashboards like any other reservation.
- Enable WooCommerce and switch WPRentals to use WooCommerce for payments.
- Install regional gateway plugins such as Klarna, Mollie, or a local bank gateway.
- Set needed currencies and test booking deposits using WooCommerce sandbox mode.
- Check that paid WooCommerce orders correctly mark WPRentals invoices as confirmed.
When should I stay with built‑in Stripe/PayPal instead of adding local gateways?
If your guests already pay by card or PayPal, extra gateways can add work without clear gains.
In many markets, major cards plus PayPal cover nearly all guests, and WPRentals supports both with little setup effort. Stripe accepts many card brands in many currencies, and PayPal is widely known, so most visitors can check out without Klarna or iDEAL. Every extra gateway added through WooCommerce means another plugin to update and test, which gives you more moving parts to track.
WPRentals also lets you pair Stripe and PayPal with the Wire Transfer method so guests who dislike cards can pay by bank and wait for manual confirmation. If you run a small or mid‑size site and rarely hear people ask for iDEAL or Sofort, staying with the built‑in trio is often best. Save WooCommerce and local gateways for when you see clear demand from a region or a drop in completed bookings without them.
How do I add a fully custom local bank or national gateway into WPRentals?
A custom local gateway needs a developer to link its API into WPRentals invoice and callback logic.
If WooCommerce doesn’t support the bank you need, a developer can connect that gateway straight to booking invoices. WPRentals includes a technical guide that shows where to add a Pay with Local Bank button inside its invoice and membership templates. The idea sounds simple but is still technical: send the invoice amount and ID to the bank payment page or API, then receive a callback on a custom processor template that marks the invoice as paid.
A working custom gateway usually adjusts at least two parts: the template that shows invoice payment buttons and a dedicated return or notification page. The processor page reads the bank response, checks success, then uses theme helper functions to set the invoice status to paid and confirm the linked booking or listing. Theme support doesn’t cover this code, so whoever builds the integration must maintain it for later theme versions and gateway API changes.
| Step | What happens |
|---|---|
| 1 Add button | Developer adds a Pay with Local Bank button in WPRentals invoice templates |
| 2 Send request | Clicking the button posts amount, invoice ID and return URL to bank API |
| 3 Handle callback | Bank redirects users to a custom processor page with payment result details |
| 4 Confirm booking | Processor calls WPRentals functions to mark invoice paid and confirm booking |
This pattern keeps the booking engine untouched while letting your gateway control the payment step. As long as the callback ends by updating the invoice status correctly, the booking calendar, emails, and dashboards work like they do for Stripe or PayPal.
How does WPRentals keep alternative and local payments secure and PCI‑friendly?
Using tokenized or hosted checkouts lets you add local methods while keeping your PCI work light.
With the built‑in gateways, card details never touch your WordPress server because Stripe Elements collects them in the browser and sends them to Stripe. WPRentals then charges a token, and PayPal handles its own login and card entry on PayPal pages, which keeps you in a light PCI class as long as the site uses HTTPS. You don’t store raw card numbers anywhere in the database, only booking, invoice, and processor reference data.
When you extend payments through WooCommerce to reach Klarna, iDEAL, or local banks, most gateways also use redirects or tokenization. That keeps the same basic security model: your site passes amounts and order IDs, while the gateway collects and protects payment details. At first this can feel complex, but really WPRentals just listens for success signals and updates invoices, so your main jobs are SSL, strong admin passwords, and keeping plugins and the theme updated.
FAQ
Can I mix built‑in payments with WooCommerce gateways in one WPRentals site?
You can use either the native Stripe and PayPal flow or the WooCommerce flow at a time, not both.
WPRentals expects you to pick one online path for deposits: its own Stripe and PayPal modules, or WooCommerce with extra gateways. You can still combine that choice with the Wire Transfer offline method if you want a bank option too. Most sites start on the built‑in flow, then switch fully to WooCommerce once they actually need Klarna, iDEAL, or other local gateways.
Do Klarna or iDEAL change who receives the money when I use WPRentals?
No, even with Klarna or iDEAL added through WooCommerce, the admin account still receives all payments.
Whether a guest pays by card, PayPal, Klarna, or iDEAL, WPRentals always treats the site owner as the payee and confirms bookings when that account gets the money. The theme doesn’t split payouts to owners or hosts, so any sharing with property owners happens by other means. This keeps links with many gateways simple while still letting you run a multi‑owner catalog on one payment account.
Can I offer “pay on arrival” while still using online payments in WPRentals?
Yes, you can support pay on arrival using a 0% deposit setup or the Wire Transfer option with manual confirmation.
One way is to set the booking deposit in WPRentals to 0%, so bookings confirm without any online charge and guests pay the full amount in person. Or you enable Wire Transfer, tell guests they can pay by bank or on arrival, and only mark the invoice as paid in the dashboard after you receive funds. This can feel old‑fashioned, but the calendar and booking records still update with the normal WPRentals workflow.
