Skip to main content

Partial Payments (Deposits)

ProSince 3.10Requires Events Manager Pro. Compare plans

Events Manager Pro can take a deposit when an event is booked and the rest later. The customer pays part of the price now, keeps their spaces, and pays the balance from a link before the event. Events Manager sends reminders as the balance comes due, and a notice if it is late.

It suits events that are booked well ahead or cost enough that people prefer to pay in two steps: workshops, courses, retreats, tours, venue hire or anything with a big ticket price.

VideoTaking deposits on bookings3:31

How it works​

  • The booking form offers the choice between paying a deposit now and paying in full. You can also make the deposit the only option.
  • The customer pays the deposit with any payment method that can take part payments. The booking is marked Deposit Paid, which keeps their spaces the same way an approved booking does.
  • They get an email with what they paid, what is still to pay, and a link to pay it.
  • Before the balance is due, Events Manager emails them a reminder with the same link. If the due date passes without payment, they get an overdue notice and you get one too.
  • The link opens the payment page, where they pay the balance with any method that takes part payments, not only the one they used for the deposit. Once it is paid, the booking is approved.
Before you start

Offline payments work too, with you recording the payments by hand (see Offline payments below). The other gateways (PayPal Standard, Authorize.net and Xero Invoice) can still be used to pay in full, but not to pay a deposit.

Settings​

Go to Events then Settings then Bookings then Partial Payments (Deposits).

  • Take deposits: switches partial payments on. Off by default.
  • Default deposit: how events work out their deposit, unless an event sets its own:
    • Percentage of the booking price, for example 25%.
    • Fixed amount per booking, the same amount whatever is booked.
    • Fixed amount per space, multiplied by the number of spaces booked.
  • Default deposit amount: the percentage or amount for the setting above. 0 means events take no deposit unless they set their own.
  • Allow paying in full: when on, customers choose between the deposit and paying in full, and paying in full is selected to begin with. When off, every booking for an event with a deposit pays the deposit.
  • Balance due: how many days before the event the balance is due. Customers see this date on the booking form, in their emails and on the payment page. 0 means there is no set date, and the balance is due any time before the event.

A deposit works out on the booking's total price, after any coupons and with any taxes. If a deposit would come to the whole price or more, for example a $50 deposit on a $40 booking, that booking pays in full.

Setting a deposit for one event​

Each event can use the site default, take no deposit, or have its own. Edit the event and find Deposit in the Bookings/Registration box.

  • Site default uses the settings above. The option shows what that is, for example Site default (25%).
  • No deposit, pay in full turns deposits off for this event.
  • Custom deposit uses the type and amount beside it: a percentage, an amount per booking or an amount per space.

Emails​

The same box has the email the customer gets when their deposit is paid, and the one the event's admins get. They are sent in place of the usual booking confirmation, because the booking is not fully paid yet.

The customer's email includes #_BOOKINGPAYURL by default, so they can pay the balance from it straight away. The placeholders written for partial payments are listed under Placeholders.

What customers see​

Booking the event​

When an event takes a deposit, the booking summary shows both options, with what is due now and what is due later.

Choosing the deposit changes the amount the payment method charges, so a card form asks for $20 rather than $80. If the customer picks a payment method that cannot take a deposit, the form asks them to choose another one or pay in full.

If your booking form doesn't show the booking summary, the same choice appears just above the booking button instead.

The deposit email​

Once the deposit is paid, the customer gets the Deposit Paid email.

Paying the balance​

The balance can be paid at any time before the event, from the link in any of the emails, or from My Bookings, where a Deposit Paid booking has a Pay balance action.

Both lead to the payment page. It shows what was paid, the balance and when it is due, and offers the payment methods that can take part payments. The link in an email works without logging in, so a guest who booked without an account can pay too.

If a balance payment is declined or the customer leaves the payment page without paying, nothing changes: the booking stays Deposit Paid with its deposit, and they can try again. Once the balance is paid, the booking is approved and the customer gets the usual booking confirmation. If the payment method is set to need your approval for payments, the booking waits for it instead, as any paid booking would.

Balance reminders​

Events Manager emails customers whose booking is Deposit Paid as the balance comes due, each time with the link to pay it. The settings are in the Balance reminders section at the bottom of the Partial Payments box.

  • Send balance reminders: on by default once deposits are on.
  • Send reminders: the days before the balance due date that a reminder goes out, separated by commas. The default, 7,1, sends one a week before and another the day before. 0 sends one on the due date itself. Bookings with no due date count back from the day the event starts.
  • Reminder email: the email for each reminder.
  • Send an overdue notice: once the due date has passed and the balance is still unpaid, the customer gets one more email, and the admins get their own. This is only for bookings that have a due date.
  • Overdue email and Overdue admin email: those two emails. Leave the admin subject or email empty to send admins nothing.

After the due date, the payment page warns that the balance is overdue:

When reminders go out​

Reminders are sent by the WordPress scheduler once a day, at the WP Cron Time of the Event Email Reminders settings in Events then Settings then Emails (midnight unless you change it). They use that time whether event reminders are switched on or not. If your site runs the scheduler from a server cron job, reminders follow that job; see WP Cron and Events Manager.

Each reminder goes out once. For an event on December 12 with the balance due on December 5 and reminders set to 7,1:

BookingWhat it gets
Booked on November 10A reminder on November 28, another on December 4, and an overdue notice on December 6 if the balance is still unpaid.
Booked on November 30No 7 day reminder, because it would have gone out before the booking was made and the Deposit Paid email had just sent the link. A reminder on December 4.
The site was down from November 27 to 29The 7 day reminder goes out on November 30, the first day the scheduler runs again. The days it missed don't each send one.
Balance due set to 0 (no due date)Reminders on December 5 and December 11, counting back from the event. No overdue notice.
Paid on December 1Nothing more after the November 28 reminder.

Reminders stop once the balance is paid, the booking is cancelled or is no longer Deposit Paid, or the event starts. They also wait while a balance payment is in progress, so nobody is reminded to pay while they are paying.

Managing deposits as an admin​

Finding Deposit Paid bookings​

Deposit Paid has its own filter in the bookings list. Deposit Paid bookings count as booked, so their spaces stay taken, and they never expire the way bookings awaiting payment can.

The payment plan on a booking​

A booking that pays a deposit has a Payment plan box on its admin page: the deposit, what has been paid, what is left, when it is due, the reminders that have gone out and when the next one will.

Send balance reminder now emails the customer straight away, outside the schedule: a reminder before the due date, the overdue notice after it. It goes to the customer only, the scheduled reminders carry on as before, and the log records who sent it.

The booking's Payment link box, just above, has the same link the emails carry, to copy and send another way. Reset link stops every link sent so far from working; the next email carries a new one.

The deposit and the balance are separate payments in the booking's transactions:

Refunds​

You can refund a deposit or a balance from the payment provider, as with any payment. If money is still left paid after the refund, the booking keeps its status and its spaces. If everything paid has been refunded, the booking is cancelled and its spaces are released. See Refunds and disputes.

Offline payments​

A customer can choose the deposit and pay offline, for example by bank transfer. The booking waits for payment as usual. When the money arrives, record it with Add Offline Payment on the booking's admin page. The first payment that is less than the full price moves the booking to Deposit Paid, and a payment that brings it up to the full price approves it.

Moving a booking​

If you move a Deposit Paid booking to another event, it gets the balance due date it would have had if it had been booked there, and its reminders start again from that date.

Placeholders​

These booking placeholders work in any booking email or format:

PlaceholderShows
#_BOOKINGPAYURLThe link to pay what is due on the payment page. Anyone with the link can see the booking and pay it, without logging in.
#_BOOKINGAMOUNTPAIDWhat has been paid so far.
#_BOOKINGAMOUNTDUEWhat is still to pay.
#_BOOKINGDEPOSITThe deposit the booking chose.
#_BOOKINGBALANCEDUEDATEThe balance due date, or the event date when the booking has no due date.

See Placeholders for the rest.

Questions​

Can customers pay a deposit in a Multiple Bookings cart?​

No. Deposits are offered on single event bookings only, so a cart is always paid in full.

What happens to an overdue booking?​

Nothing automatic. It stays Deposit Paid and keeps its spaces until you cancel it or the balance is paid. The overdue notice goes out once, and you can send more with Send balance reminder now.

Do Deposit Paid bookings get the event reminder?​

Not yet. The Event Email Reminders in Events then Settings then Emails go to approved bookings only.

Can I take a deposit on some tickets and not others?​

The deposit is set per event, not per ticket. For an amount that grows with the booking, use Fixed amount per space or a percentage.

Does it work on a multilingual site?​

Yes. The deposit and reminder emails can be translated like other booking emails, and each one is sent in the language the booking was made in.

Will bookings made before deposits were switched on get reminders?​

Only bookings that paid a deposit are Deposit Paid, so bookings that paid in full, or were made before deposits were on, are not affected.

For developers​

Hook or nameWhat it is
Status 9Deposit Paid, a booking status Events Manager Pro adds.
payment_plan booking metaThe plan a booking chose: type (deposit), rule (the deposit type and value) and balance_due (a Y-m-d date, or empty).
em_payment_deposits_enabledFilter on whether deposits are on.
em_payment_deposit_ruleFilter on the deposit rule an event uses: ( $rule, $EM_Event ), where $rule is an array with type and value, or false for no deposit.
$supports_partial_paymentsGateway class property. A gateway that sets it to true is offered for deposits and balances, and charges EM\Payments\Gateways::get_charge( $EM_Booking ), which returns the amount due now and its purpose (deposit or balance).
em_gateway_payment_receivedAction after a recorded payment moved a booking on: ( $result, $EM_Booking, $gateway_class ), where $result is paid, partial or pending.
emp_cron_deposit_remindersThe daily scheduled event for balance reminders. wp cron event run emp_cron_deposit_reminders runs it by hand.
em_payment_deposits_reminder_messagesFilter on the reminder emails before they are sent: ( $msg, $EM_Booking, $step ), where $msg holds user and admin subjects and bodies and $step['type'] is reminder or overdue. An empty subject or body skips that email.
deposit_reminders booking metaWhat reminders were sent: steps (each step against the due date it counted from) and log (each email, when, and who sent it by hand).