Payments attached to appointments — every pound knows where it came from
Every payment is linked to the appointment it paid for, with its client and its service.
The problem
A list of payments with no context is hard to use. You see amounts and dates, but not which appointment they belong to. Working out who paid for what means cross-checking two tools by hand, line by line.
The problem turns serious at the moment of a refund or a chargeback. You have to prove what was sold, to whom, and when — and a line reading “payment of £45” does not prove it.
Yet the information exists at the moment the money is taken. It just has to not get lost on the way.
How it works in Kagenda
Kagenda creates the payment out of the booking, and keeps the link between the two in both directions.
- The payment is born of the bookingFrom the outset it carries the appointment concerned, its client and its service.
- The appointment shows its paymentFrom the calendar, the detail of a booking states what was paid online and what remains due on site.
- Cancellation finds the transaction againIt is this link that lets the automatic refund bear on the right payment, without your having to point at it.
Who it helps
Frequently asked questions
Can I see a given client's payments?
The history on the client record lists their bookings, and each booking carries its payment. The full financial breakdown stays in your Stripe dashboard.
Does Kagenda issue invoices for my clients?
No. Stripe generates payment receipts; invoicing for your services is a matter for your own obligations and your accounting tool.
What happens if I delete a paid booking?
Cancelled bookings are kept rather than deleted, precisely so that the payment keeps what it is attached to.