WP Travel Engine - WooCommerce Payments
Antivirus scan
Powered by ClamAV
✅ Verified clean
This product file has passed our security filters.
Want to run a fresh ClamAV scan right now? Takes a few seconds and shows scanner version, signature DB and live result.
This can take 5 to 30 seconds.
Clean file Threat detected
No threats detected in this file.
- File
- Size
- Scanned
- ClamAV
- Signature database
⚡ Powered by ClamAV
Scan could not be completed
Report product
If you detected an issue (broken file, malware, inappropriate content, etc.) let us know and we'll review it ASAP.
Sign in to report
About WP Travel Engine - WooCommerce Payments
Taking trip payments through the WooCommerce gateways
WP Travel Engine handles trips well: itineraries, departure dates, places and travellers. Where it falls short for many agencies is payment, because the gateways it supports out of the box do not always include the one the local market uses.
This add-on solves that by connecting the booking system to WooCommerce, and therefore to **more than 78 payment gateways**, WooPayments, Penso Pay, PayMob and Apple Pay among them.
For an agency outside the big markets, that is often the difference between being able to take payment online or not.
How the two systems fit together
The booking still lives in WP Travel Engine, with its travellers and itineraries, and WooCommerce handles payment only. That is the correct split: you do not end up managing bookings from a shop that was never designed for it.
- The trip's featured image syncs with the WooCommerce product.
- Cart data is stored in the WooCommerce order.
- Booking status stays synchronised with the order status.
- The order ID appears on the booking detail page, so the two can be cross-referenced without searching.
The detail that prevents the worst problem
If payment fails, **the booking is not created**. That sounds obvious and it is not: the classic breakage in these integrations is creating the booking when payment starts and not cleaning it up if the charge fails, leaving you with places held by people who never paid and a trip that looks full when it is not.
Storing cart data in the order runs in the same direction: it stops a booking getting lost mid-process.
Other details
Checkout captures tax amounts and traveller details alongside standard WooCommerce data. Transactions are encrypted. There is REST API support for configuring gateways, and HPOS compatibility, WooCommerce's high-performance order storage.
Frequently asked questions
Do I need WP Travel Engine?
Yes. It is an add-on for it: connecting its booking system to the WooCommerce gateways.
Do I have to manage bookings from WooCommerce?
No. Bookings stay in WP Travel Engine; WooCommerce handles payment only.
What happens if payment fails?
The booking is not created, which prevents places being held by orders that were never paid.
How many gateways does it support?
More than 78, the WooCommerce-compatible ones, WooPayments and Apple Pay included.
Topics
Version history
-
v
1.1.1 Current 8 Jan 2025
Customer reviews
Sign in to leave a review. Only people who have the product can review it.
No reviews for this product yet.
Frequently asked questions
-
GPL (General Public License) is the license under which WordPress and most premium plugins/themes are distributed. It grants you the right to use, modify and redistribute the software in as many projects as you want, with no domain restrictions.
-
Yes. With membership you get automatic updates via our GPLClub Updater plugin (installed on your WP, detects new versions and applies them). With individual purchase, you get one year of manual updates from your account.
-
Depends on the plan. Monthly: 3 domains. Semi-annual: 7. Annual and Lifetime: 15. Individual purchase: 1 domain.
-
GPLClub offers its own support for installation, configuration and compatibility. For direct support from the original author (feature requests, product-specific bugs), a license purchased from the author is required.
