WP Travel Engine - Partial Payment

Charging everything upfront scares off bookings; charging little leaves you exposed

A organized trip costs enough that travelers hesitate before paying it in full, and meanwhile you have to commit to accommodation, guides or transport before the departure date. Asking for a reasonable deposit helps both sides, but handling it by hand (bank transfers, emails, spreadsheets) ends in forgotten balances. WP Travel Engine - Partial Payment adds that deposit to the WP Travel Engine booking process and organizes what comes afterwards.

A trek booked months ahead, step by step with WP Travel Engine - Partial Payment

Imagine an agency with an affordable mountain route and a luxury safari. This is how the process goes:

1. You decide how much is requested upfront for each trip

The deposit is set trip by trip, as a percentage or as a fixed amount. There is also a fixed-per-booking type: a single deposit, whether one traveler goes or six. The cheap route can ask for little and the safari can ask for more, because they don't attract the same buyer.

2. The traveler chooses how to pay

At checkout they see the deposit option and, if you allow it, the full payment option; you can show or hide the latter. They get a clear summary of what they owe, so there is no doubt about the amount due. If the deposit turns out to be higher than the total booking price, the partial option hides itself.

3. You set until when deposits are accepted

With cut-off days you stop accepting deposits a set number of days before departure. Once that date passes, checkout requires full payment even if you have that option disabled. This prevents someone from booking with a deposit three days before leaving and leaving you with an uncollected balance.

4. The balance doesn't get forgotten

You can set how long the remainder has to be paid in (Final Payment Due In), but note: that setting only determines the displayed date and schedules the email reminders; it doesn't block anything by itself. Reminders are not sent when nothing remains to be paid, and in checkout messages you can show the balance with the {amount_due} tag.

If you use WP Travel Engine's Advanced Email Automator add-on, you have two triggers: remaining payment completed and payment pending. That automator is a separate add-on. And remember that this plugin doesn't work on its own: it needs WP Travel Engine installed. Check in the demo how the balance collection works with your payment gateway before building your flow.

Questions before enabling the deposit on your trips

Can I set a different deposit for each trip?

Yes. It is defined on each trip, with a percentage or a fixed amount, and you can add the fixed-per-booking type.

Can I force full payment on last-minute bookings?

Yes, with cut-off days. Once the date is exceeded, checkout asks for full payment automatically.

Does full payment stop being offered?

Not necessarily: there is an option to show or hide it, so you decide.

Does it work without WP Travel Engine?

No. It is an add-on for that plugin and depends on it.

If all your trips are paid in full, this add-on is surplus

It makes sense for agencies and operators selling experiences with a distant date and a high average ticket, where the deposit lowers the barrier to entry. If you sell day trips or cheap activities paid in full at booking, you won't make use of it. Nor is it a tailor-made installment system: the logic revolves around the deposit, the remaining balance and its reminders.