Every Payment Matched to a Booking

The payment and the booking were created by two different systems and the handoff failed. Typically the checkout opens in your processor, the student pays, and your booking system is supposed to hear about it through a webhook or a redirect back to a confirmation page. If the student closes the tab before the redirect, or the webhook call errors and nothing retries it, the payment completes and the booking never does. Nothing is broken loudly enough to notice. The fix is to stop treating the redirect as the source of truth and instead reconcile against the processor itself: pull completed charges, match them to bookings, and raise an alert on any charge that has no booking behind it.

You need something reading your payment processor continuously rather than waiting to be told. Every completed charge is checked against open and recent bookings on email, phone, amount, and course. Most match instantly. The ones that do not become orphans and trigger an immediate notification with the student's name, the amount, the timestamp, and the likely session, so you can attach it in the dashboard in under a minute. The value here is entirely in the speed. An orphan caught in five minutes is a confirmation email that arrives slightly late. The same orphan caught in five days is a refund request and a one-star review.

Usually because the confirmation is wired to the wrong event. Many setups send it on payment success from the processor's side, which means anything that interrupts that callback also kills the email. We send the owner notification at intake, the moment the booking is created, so you know a student is in play even if the payment never completes. The student confirmation then fires when the payment is matched. Splitting those two events means a stalled checkout shows up as a recoverable lead rather than as silence, and a completed payment always produces a confirmation because it is triggered by the money arriving rather than by the browser behaving.

Automatically and daily, on two sides. The first side is the one everyone thinks of: payments with no booking, which cost you a customer relationship. The second is bookings with no payment, which cost you a seat, because a held seat that never got paid for is inventory you could have sold. Run both checks every day and each becomes a short worklist instead of a discovery. Doing this by hand means exporting from Square, exporting your roster, and eyeballing two spreadsheets, which is exactly the task that gets skipped in a busy week, which is exactly the week it matters.

More than the ticket. A student who paid and got nothing back has already decided you are disorganized before you have said a word, and that judgment shows up in the review long after you have refunded her. If she bought through an ad, you also paid to acquire her and then lost her at the last inch: our own cost per booked student is about $21, so an orphan payment burns both the seat and the acquisition. Then she never enters the renewal cycle, so the two-year repeat purchase disappears too. One failed handoff quietly deletes three separate pieces of revenue.