Skip to content

Payments

An order is paid when its payments add up to its total. Some of that happens automatically, and some you do by hand. This section covers both. Start here for how payment works overall, then follow the page for the task you need.

  • Card, through the platform. Customers pay by card at checkout, and you can charge a saved card or a held authorisation from the order later. Card payments run through Stripe, which you add to your site and turn on once.
  • Payments you record by hand. A bank transfer, cash at the door, or a payment taken on an EFTPOS terminal. You enter these against the order so its balance stays accurate. See Manual payments.

Whether people must pay at checkout or can be billed to pay later is a setting:

  • With up-front payment on, an order has to be paid (or its payment authorised) when it is placed.
  • With it off, people can place an order and pay later, which suits invoiced or trusted-group bookings. Those orders carry a payment due date you can track under Overdue orders.

This is set in Settings, and can be varied per event.

Two card features help when payment and approval do not happen at the same moment:

  • A payment authorisation holds money on a card at checkout and is charged when you approve the order.
  • A saved card is a card the customer has kept on file, which you can charge or place a new hold on.

Whether the card processing fee is built into your prices or added as a surcharge at checkout, and whether tax applies, are both covered in Settings.