Field note 47/ E-Commerce · Engineering
Did the Payment Go Through? What to Test Before You Launch Online Booking
Test what happens when customers pay, close the tab or compete for the last slot. Verify the booking and payment separately before launch.
A customer picks the last Saturday appointment, pays a deposit, and closes the tab. The card processor shows a payment. The booking calendar is empty. Which screen should your front desk trust, and what should the customer do next?
That is the test to run before you launch online booking. A polished checkout only proves someone can get to the payment screen. A booking works when the customer, payment record and business calendar agree on what happened, even when the customer never sees the final page.
Decide what you are promising
A request form asks your team to confirm availability. An instant booking promises a specific slot once the requirements are met. Either can be a good fit. Where schedules still need manual approval or availability is unreliable, a clear request with a realistic reply time is better than calling it an instant booking.
If you're accepting a deposit, decide what the guest is buying before you build the button. Is the slot held during payment? For how long? What amount is due now, what remains, and when? If payment and booking disagree, who checks the records and when should the customer expect an answer? Put those decisions in the checkout brief, not just in the terms page.
Check three records, not one green screen
- The customer sees the amount due, the date and time with its time zone, and an honest status. Once confirmed, they have a reference and a way to find help.
- The payment record shows the expected amount and currency, and whether the payment is still pending, authorized, captured or refunded. Keep those labels distinct.
- The business calendar shows exactly one matching booking. The person taking appointments can find it and knows what to do if payment and booking disagree.
The return page should display the outcome, not be the only thing that makes the booking happen. Stripe’s guidance for Checkout, for example, says fulfillment cannot rely on the customer reaching that page. It also notes that the same fulfillment work may be triggered more than once. Your provider may use different terms; ask your developer to show that reopening the page or processing a duplicate notification does not create another charge or reservation.
Run these tests before sign-off
Use a test payment account, a test calendar and fictional customer details. Keep both systems out of live mode: a test card is not enough if the booking still reaches an actual calendar or staff inbox. Stripe’s sandbox testing guide includes declines and additional authentication, so the demo doesn't have to be all successful transactions.
- Pay once. Verify one matching payment, one slot and one booking reference. Compare the amount shown before payment with the amount recorded.
- Decline the payment or cancel the bank’s authentication step. The site should not say “Booked.” Check what happens to any temporary hold and whether the customer can retry without starting a second booking.
- Close the tab immediately after payment, or interrupt the connection. On return, the customer should see the same attempt's status, not an invitation to pay twice. Have a staff member verify the outcome without needing the customer’s card details.
- Try the last slot from two sessions. Only one can end up confirmed. The losing session gets a clear outcome and no retained payment for a booking it did not get. Check what the system does when a hold expires or a slot is no longer available.
- Have the test booking service reject a reservation after the processor acknowledges the payment. Check that the customer gets a truthful pending or failed status, staff can find the mismatch, and the agreed resolution appears in both records. A pending refund is not a completed refund.
- Replay a test notification and revisit the confirmation. Records should stay consistent and neither action should create a second payment or booking. Stripe documents that notifications can be retried and can arrive out of order.
Make the uncertain screen useful
A confirmed page can say “Booked,” show the reference, and explain what happens next. GOV.UK’s confirmation page pattern is a useful design reference for showing the reference and where to get help, not a rule that every business must copy.
If you cannot tell yet whether the slot was booked, say so: “We’re checking your booking. You don’t need to pay again. Use this reference if you contact us.” Give a review window only if the team can meet it. Put each uncertain attempt in a staff queue with a reference, times and both statuses. Staff should be able to check the existing attempt before asking the customer to retry.
The launch decision
Ask the person who manages bookings to run one success and one interruption from a phone. Have them show what the customer saw, what the processor recorded and what appeared on the calendar. Write down who owns exceptions and where they check them. If those records still disagree and no one can reconcile them, keep the flow in test mode or stick with a clearly labeled request form until it is ready.