Payment Gateways in WP Travel Engine and PayLexer Integration
Learn which payment gateways WP Travel Engine supports and connect PayLexer to offer more payment options for your tour business.
Choose the right payment gateway for your tours
WP Travel Engine lets you accept payments through many payment gateways. A payment gateway is the service that moves money from your customer to your business.
Some gateways are built into WP Travel Engine as native add-ons. The remaining gateways connect through PayLexer, a separate plugin and platform.
Together, WP Travel Engine currently lists 94 payment gateways:
- 12 native gateways
- 82 gateways available through PayLexer
This gives you options for local payments, international cards, deposits, and payment plans.
What PayLexer does
PayLexer connects your WordPress checkout to payment gateways that WP Travel Engine does not support directly. A checkout is the payment section your customer uses when booking a trip.
PayLexer does not process or store your payments. Each transaction goes directly through the payment gateway you connect, such as Stripe, Paystack, or Mollie. PayLexer links that gateway to your WordPress checkout and passes the payment result back to WP Travel Engine.
For example, you could connect a local payment service for a trekking business in Nepal, or use a regional bank gateway for day tours in Sri Lanka.
With PayLexer, you can:
- Accept payments through gateways that WP Travel Engine does not support natively, including Stripe, Airwallex, Paystack, and others.
- Manage multiple gateways and websites from one PayLexer dashboard.
- Switch between Test and Live credentials using Debug Mode. Credentials are the login or access details that let one service connect to another.
- Track all transactions in one place.
PayLexer is built exclusively for WP Travel Engine. The same platform also connects to WooCommerce, Fluent Cart, and Easy Digital Downloads.
For a WP Travel Engine site, PayLexer fills gaps in the native gateway list. It is especially useful for regional and country-specific gateways. It also adds partial payments and separate checkout labels for each gateway.
You need a PayLexer account before the plugin can work. Add your gateway credentials inside PayLexer. Then connect PayLexer to WP Travel Engine with a Client ID and Site Key. A Client ID identifies your website connection. A Site Key acts like a private connection key.
What you get with PayLexer
| Feature | Benefit |
|---|---|
| 82 additional gateways | Reach customers who prefer a regional or local payment method that WP Travel Engine does not support natively. |
| Partial payments | Let travelers pay a deposit when they book and pay the remaining balance later. This works well for multi-day treks and group packages. |
| One connection for many gateways | Add or change gateways from PayLexer instead of installing a separate add-on for each one. |
| Debug Mode for safe testing | Run test bookings with test credentials before accepting real payments. |
| Custom checkout labels | Show a familiar label such as “Credit Card” instead of the gateway’s business name. You can also use a label in your customer’s language. |
| Works across your other plugins | Use the same PayLexer connection with WooCommerce, Fluent Cart, and Easy Digital Downloads if you run more than one type of store. |
What you need before you start
Make sure you have:
- WP Travel Engine installed and activated on your WordPress site.
- The latest version of WP Travel Engine.
- Administrator access to your WordPress site.
- A PayLexer account. Create a PayLexer account if you do not have one.
- An account with the payment gateway you want to connect, such as a Stripe or Paystack merchant account. PayLexer connects to your existing gateway account. It does not create one for you.
Connect PayLexer to WP Travel Engine
Connecting PayLexer lets your customers use gateways that are not available as native WP Travel Engine add-ons.
What you’ll need before you start: your PayLexer account, your payment gateway account, and administrator access to your WordPress dashboard.
Create or sign in to your PayLexer account
Open PayLexer and create an account, or sign in if you already have one.
Your PayLexer dashboard is the website where you add payment gateways, connect websites, and view transactions.
Add your payment gateway in PayLexer
Choose the payment gateway you want to use for your tours. Enter the credentials provided by that gateway.
For example, a card gateway may ask for live and test keys. A regional bank gateway may ask for merchant details from your bank account.
The gateway should appear in your PayLexer dashboard after you save its details.
Connect your WordPress website
This connection lets WP Travel Engine send checkout payments to PayLexer.
In the PayLexer dashboard, add your website and copy the Client ID and Site Key. Then open your WordPress dashboard. The WordPress dashboard is the administration area where you manage your website.
On the left sidebar, open Settings, then open PayLexer. Enter your Website URL, Client ID, and Site Key. Save the settings.
Your website should show as Connected in the PayLexer dashboard. If it does not, compare the Website URL with the address of your WordPress site and copy the Client ID and Site Key again.
Enable the gateway in WP Travel Engine
This step makes the connected gateway visible to customers at checkout.
In your WordPress dashboard, open WP Travel Engine from the left sidebar. Open the payment settings and enable the PayLexer gateway you connected.
Save your changes. Create a test booking and confirm that the gateway appears in the payment options.
Run a test booking
Testing protects you from finding payment problems after a customer tries to book.
Open WP Travel Engine, then Settings, then Payments, then General. Turn on Debug Mode and use the test credentials from your payment gateway.
Complete a booking for a trekking package or day tour. The booking should complete without charging real money. Turn Debug Mode off and switch to live credentials before accepting real bookings.
Native payment gateways in WP Travel Engine
Native gateways are built into WP Travel Engine as individual add-ons. They do not require PayLexer.
| Gateway | Coverage |
|---|---|
| Stripe Payment Gateway | Global, with strong coverage in Europe and North America |
| WooCommerce Payments | Works through your connected WooCommerce payment gateways |
| PayPal Express Checkout | Global |
| Razorpay | India |
| WeTravel Integration | Works with WeTravel or a custom booking URL |
| Midtrans | Indonesia |
| PayU Money | India |
| PayHere | Sri Lanka, with wider regional reach |
| Himalayan Bank | Nepal |
| PayFast | South Africa |
| PayU Biz | Global growth markets |
| Authorize.net | North America, Europe, and Oceania |
If the gateway you need appears in this table, install it directly from the WP Travel Engine add-ons page. You only need PayLexer for a gateway that is not on the native list.
Payment gateways available through PayLexer
PayLexer expands the WP Travel Engine gateway list from 12 to 94. The additional 82 gateways mainly serve specific countries or regions.
The list below groups the gateways by market. PayLexer adds gateways over time, so use the linked gateway lists for the latest information.
- Africa: Paystack, Flutterwave, PayFast, PesaPal, DPO, M-PESA, Squad, GetPayIn
- Middle East: AmwalPay, Moyasar, Tap Payments, MyFatoorah, PayTabs, Fatora, UPayments
- Asia-Pacific: 9Pay, DOKU, NICEPAY, Maya, Omise, HitPay, ToyyibPay, SSLCommerz, PAY.JP, KOMOJU, eSewa, Khalti, Fonepay, PayU
- Europe: Adyen, Mollie, MultiSafepay, Barion, Datatrans, Nets, Worldline, iyzico, PAYONE, Quickpay, Tpay, Viva, Montonio, SumUp
- Latin America: Mercado Pago, Conekta, Culqi, Getnet, Openpay, Transbank, TropiPay, ONVO Pay
- North America: Moneris, Elavon, Global Payments, Authorize.Net
- Oceania: Pin Payments, Westpac PayWay, Windcave, Eway
- Global and multi-region: Stripe, PayPal, Square, Klarna, Checkout.com, Airwallex, Braintree, BlueSnap, Paysafe, Revolut, GoCardless
For the full current list, check the WP Travel Engine payment gateways page or PayLexer's gateway list.
Some gateways support recurring billing. WP Travel Engine shows this as “Subscriptions.” This can help when you offer payment plans or let customers pay for a trip in installments.
How WP Travel Engine and PayLexer work together
WP Travel Engine manages your booking. It handles the trip listing, traveler details, and checkout page. It supports both one-time payments and partial payments, such as a deposit followed by a later balance payment.
Each payment attempt, including a partial payment, creates a new order inside PayLexer.
When a customer reaches the payment step, WP Travel Engine shows all connected gateways in one list:
- If the customer chooses a native gateway, WP Travel Engine sends the payment directly to that gateway.
- If the customer chooses a PayLexer gateway, the payment goes through PayLexer first. PayLexer sends it to the connected gateway, receives the result, and sends that result back to WP Travel Engine.
Your customer does not see this handoff. They choose a payment method and complete the payment as they would with a native gateway.
Troubleshooting payment connections
My website says it is not connected to PayLexer
The website connection must be active before PayLexer can send payments from your checkout.
Check that the Website URL in WordPress matches the URL in your PayLexer dashboard exactly. Re-copy the Client ID and Site Key from PayLexer and paste them into Settings, then PayLexer in your WordPress dashboard.
Return to the PayLexer dashboard and confirm that the website shows as Connected.
Test payments work but real payments do not
Test payments use different details from real payments.
Open your WP Travel Engine payment settings. Turn off Debug Mode and replace the test credentials with your Live credentials from the payment gateway. Save the settings before trying another real payment.
A gateway I want is not showing up at checkout
The gateway must be connected and enabled in two places.
First, open your PayLexer dashboard and confirm that the gateway is connected and enabled. Then open the WP Travel Engine payment settings in your WordPress dashboard and confirm that the same gateway is enabled there.
Save both sets of settings and refresh the checkout page.
My customer paid but the booking still shows unpaid
A gateway may take a little time to confirm a payment.
Open your PayLexer dashboard and check the transaction status. If the transaction shows as completed but the WP Travel Engine booking still shows unpaid, contact WP Travel Engine support with the booking and transaction details.
Do not ask the customer to pay again until you confirm the first transaction status. A second attempt could create a duplicate payment.
I am not sure if I should use a native gateway or PayLexer
Start with the native gateway table on this page. If your gateway is listed there, install its WP Travel Engine add-on directly and skip PayLexer.
Use PayLexer when your preferred gateway is not on the native list, or when you want to manage several gateways from one dashboard.
FAQs
If you are unsure which gateway to choose or need help connecting PayLexer, contact WP Travel Engine support. Share your website address, the gateway you want to use, and any error message you see. The support team can help you find the next step.