Automatic payment confirmation — the booking confirms itself as soon as it is paid
Stripe tells Kagenda about the payment, and the booking becomes confirmed with no intervention.
The problem
Between payment and confirmation there is a technical round trip. The client pays on a Stripe page, then comes back — or does not. If they close their browser during the redirect, the payment has happened but nobody has told the software to validate the booking.
Relying on the client's return alone therefore creates ghost bookings: paid for, but left pending. The slot ends up freeing itself while the money has been taken, and you discover the problem when the client turns up.
The reliable source is the payment system itself, which knows what has been settled regardless of what the browser does.
How it works in Kagenda
Stripe tells Kagenda directly, server to server, without going through the client's browser.
- The payment goes through at StripeThe transaction is approved by the bank and by Stripe.
- Stripe notifies KagendaA notification is sent to Kagenda, regardless of what the client is doing at that moment.
- The booking is confirmedThe temporary hold becomes permanent, the confirmation email goes out and the appointment enters your calendar.
Who it helps
Frequently asked questions
What happens if the client closes the page after paying?
Confirmation does not depend on their coming back: it is Stripe that tells Kagenda. That is precisely what this mechanism is for.
How do I check that a paid booking really is confirmed?
It appears in your calendar with its payment attached. On your first paid bookings, check this explicitly: this mechanism has not yet been observed under real conditions.
And if the notification does not arrive?
The slot stays held until the hold expires, then frees itself. The payment itself is visible in your Stripe dashboard: that is where to look if in doubt.