Damage Signal

Checkout or Booking Not Working

Customers are trying to pay or book. The system will not let them complete the transaction.

Damage Signal Record — Operator Rescue

What operators see · What it means · When it happens · Linked disaster pattern documented

What Operators Usually See

Customers reach the checkout or booking page and something fails. Payment errors appear. The submit button does not work. The form clears without confirmation. The mobile experience crashes at the payment step. The business learns about it when customers call to complain — or, more often, when a revenue report shows the period of failure after the fact. Some customers try to contact the business. Most do not. They go somewhere else.

What This Usually Means

The revenue pathway is broken at the highest-intent moment in the customer journey. This is not a traffic problem. The customer has already decided to purchase. The infrastructure that should complete the transaction is not functioning. Most commonly: a payment gateway API key expired or was rotated without being updated in the checkout configuration; a platform update changed the checkout behavior and broke mobile payments; calendar sync failed so booking slots show as available when they are not; or a security certificate lapsed on the payment page. The business is losing every customer who reaches the payment step while the failure persists. Every hour matters.

When This Happens

After a website platform update that changed checkout plugin behavior. When payment processor API credentials expire and are not rotated in the checkout settings. After migrating hosting providers without fully transferring SSL certificates and checkout configuration. During high-traffic periods when payment gateway rate limits are exceeded. When the booking tool vendor pushes an update that resets calendar sync or payment settings to defaults.

Related Disaster Pattern

Authority Record — How We Know This

Documentation Basis

Signal recorded from operator intake cases. Each entry maps to at least one documented business failure where this exact surface-level symptom appeared.

Coverage

What operators see · What the signal means · When it typically appears · Which disaster pattern it connects to · 2 related signals cross-linked.

Next Step

Each damage signal links to a full disaster pattern record and a Fix Pack. If you are seeing this signal, the fix is already documented. See Fix Packs.

Operator Rescue · Direct Intake

Recognize this pattern?

Describe what is happening in your business. You do not need to diagnose it. Start talking and I will identify the pattern and what to do first.

Seeing this signal?

Send the mess now. The earlier we get it, the faster we respond before it compounds.

Send the Mess

Response timing depends on urgency level selected during intake.