Skip to main content
Back to modules

Payments module

Deposits and payments to protect calendar time and higher-value services

Payment becomes part of the booking journey: customers understand what they are confirming, while the business reduces no-shows, wasted slots, and manual recovery.

Quick answer

How it fits the flow

The module connects service, amount, payment status, and booking. Use it for deposits, full balance, or recovery of pending payments.

Availability: Enterprise only
1 Service deposits
2 Online balance
3 Tracked payment status
4 Connectable providers

Plan for

  • Payment provider configured
  • Clear rules for deposit, balance, and cancellation
  • Services with updated price and conditions

Decision guide

Understand whether this is the right module before activating it

Each module should be read as an operational investment: it should reduce friction, improve a decision, or strengthen the customer journey.

When to activate it

Long or expensive treatments

A deposit reduces weak bookings and protects slots that are hard to fill at the last minute.

Before starting

Prepare the conditions that make it useful

The module works better when rules, content, and responsibilities are already reasonably clear.

  • Payment provider configured
  • Clear rules for deposit, balance, and cancellation
  • Services with updated price and conditions

What to watch

Measure the value it adds to the flow

After activation, watch practical signals: less manual work, more clarity for customers, and better confirmations.

  • Service deposits
  • Online balance
  • Tracked payment status

Checkout example

Deposits, balances, and pending bookings are readable at a glance

The dashboard highlights which services require payment, which appointments are confirmed, and which ones need recovery.

Provider active

Business dashboard

Payments linked to booking

Ready

Deposit

30%

Rule on selected service

Confirmed

18

Bookings with payment completed

Pending

2

To recover or verify

1

Service rule

The business decides where deposit or balance is required.

2

Payment in summary

Customers see amount and conditions before confirming.

3

Tracked status

Booking and payment always remain connected.

Operational flow

From service to payment without disconnected steps

Customers do not receive a generic link: they pay inside a journey that matches the booking.

1

Define which services require payment

Protect only the services that are more delicate, more expensive, or more exposed to no-shows.

2

The customer confirms with clear commitment

Deposit or balance appears in the summary, so the choice is transparent before confirmation.

3

The business controls the status

Booking and payment remain connected, making it easier to understand what is confirmed, pending, or needs recovery.

Practical cases

When asking for payment makes sense

Not every service needs it: the module is strongest where time, materials, or economic value require commitment.

Long or expensive treatments

A deposit reduces weak bookings and protects slots that are hard to fill at the last minute.

Online consulting or remote sessions

Payment and meeting links can work together, keeping the pre-appointment experience orderly.

Packages, events, or limited services

When seats are limited or preparation is required, payment helps separate interest from real confirmation.

Combine with

Connected modules

Next step

Want to make bookings more reliable?

Start with the services where a no-show hurts most: payments should protect the work, not complicate every booking.

Cookie preferences

We use essential, analytics, and marketing cookies. You can choose now or change your mind later.

Manage your cookie categories. Necessary cookies are always enabled.