Why Does My Booking or Checkout Page Keep Failing?

Because the part of your website that takes money is the most complicated part, and it quietly breaks when something around it changes. A plugin update, a theme update, an expired payment key, a mail sending change or a new caching setting can each stop a booking or checkout page without any obvious error. The page still looks fine. It just stops working. The remedy is to test the money path after every change, not only when a customer complains.

Why the money path breaks

A checkout or booking page is not one thing. It is a form, a payment connection to a bank or payment company, a stock or calendar check, an order record, and a chain of notification emails to you and the customer. Each of those is usually a separate plugin or service, and each gets updated on its own schedule. When one changes shape, the others stop talking to it.

The usual culprits

  1. A plugin or theme update. The booking plugin updates, the payment plugin has not caught up, and the pay button spins forever. Check what was updated in the days before the failures started.
  2. An expired or rotated payment key. Payment companies issue keys that connect your site to your account, and they get rotated or revoked when an account changes. The customer sees a vague error at the final step.
  3. Notification emails going missing. Orders are going through, but neither you nor the customer get the email, so it looks like nothing happened. This is usually the site’s mail sending breaking, the same fault that stops contact forms.
  4. Caching. A caching plugin or hosting cache starts serving a frozen copy of the cart or calendar, so customers see old availability or an empty cart. Checkout pages should be excluded from caching.
  5. A security plugin or firewall blocking the payment company’s callback. The payment succeeds at the bank but your site never hears about it, so the order shows as pending.
  6. A certificate problem. If the padlock has gone from your site, browsers and payment companies refuse to pass card details through it.

Test the money path after every change

After any update, do a test transaction as a customer would. Pick the product or time slot, enter details, pay with a test card or a small real payment you refund, and then confirm that the order appeared in the admin area and that both emails arrived. Doing this takes a few minutes and catches nearly every failure before a customer does. Put it in the checklist of whoever applies updates.

Reduce the breakages

Keep the number of plugins involved small. Apply updates on a copy of the site before the live one where possible. Use a dedicated mail sending service for the site’s emails rather than relying on the hosting server. Keep the payment company’s account email going to a mailbox someone reads, because that is where the warning about an expiring key arrives.

What to do next

Updates, testing after updates and watching for silent failures are the day to day work of our website care and hosting service. If the orders are going through but the emails are not, our post on why your contact form is not sending you emails explains the mail sending side, which is the same fault.

Customers say they paid but I have no order. Where did the money go?
Almost always it is sitting in your payment company account and the site never recorded it. Log in there first, then fix the callback or plugin that failed.

Should I turn off automatic updates to stop this?
Not entirely, because security updates matter. Have updates applied by someone who tests the checkout afterwards, rather than leaving them fully automatic and unwatched.

Is it my hosting?
Sometimes, especially for caching and mail sending. Cheap shared hosting is a common factor in sites whose checkout fails after updates.

If this is happening in your business and you would like it sorted, call DM1 on (08) 6202 6012 or send us a message. We look after IT, Microsoft 365, websites and domain names for Perth small businesses.

Need IT help? Chat with us
DM1
DM1 Assistant
Perth IT Support Guide
Scroll to Top