The next step is deciding on the best payments approach for your venue and processes. Let's look at each approach in detail.
The Upfront approach
When on the upfront payment approach, your users are charged in the final step of the online booking process. The booking holder's credit card is debited the full booking price. If they are allowed to create a weekly recurring pattern, they will pay the total series price in a single transaction. After the booking is complete, the booking is always 'locked-in' and the holder cannot cancel it in a self-service manner online (only an administrator can remove the booking). Review the frequently asked questions area for information on cancelling / refunding upfront bookings.
You should choose this approach if your organization requires full and immediate payment for the confirmation of a booking, and cancellations are rare (or simply not allowed).
The Book now, Pay later approach (BNPL)
When on the book now, pay later approach, your users are not charged anything immediately to secure a booking online. The booking holder is however required to provide a valid credit card to show that they're genuine. Card details only need to be added once and are stored securely in your payment gateway's vault.
You and your co-administrators then have the ability to charge the credit card for the full booking price from any of the interface views (day, month, grid and list), once the booking (or all bookings within the series) are 'locked-in', meaning that they cannot be cancelled by the user with respect to your cancellation lock-in window!
For more information on this, check into the article 'Charging Book now, Pay later' bookings.
Alternatively, you could decide to take payment another way, e.g., in cash and simply mark the booking or the full booking series off as paid.
The Book now, Pay later approach is ideal if:
You often deal with refunds and/or cancellations
You want to make the booking process attractive and frictionless for your users
You want to offer alternative payment options to your users (e.g. cash on arrival or customised invoicing)
You want to have card details for a booking as a security measure, even if you don't plan to charge their booking at all
If you'd like to see either of these approaches in action, use the system's test mode!