Follow the money, literally

Checkout Not Working? When Customers Can't Pay, Walk the Money Path Yourself

Traffic looks normal. Carts fill up. Then nothing: no orders since Tuesday afternoon, and nobody wrote to complain, because customers who cannot pay rarely explain why. They close the tab and buy from the next one. A broken checkout is the quietest emergency a business can have.

November 19, 2026 · 10 min read

acmecoffeeroasters.com · checkout, last 24 hours
Carts fill up; payments never arrive
Shoppers reach payment, and every attempt stops there
Viewed a product412
Added to cart188(46%)
Started checkout126(67%)
Submitted payment109(87%)
Order confirmed0(0%)

Payment form submits, then the gateway rejects a test-mode key

Illustrative: sample checkout funnel for a fictional coffee roaster's online store

The short answer

If customers can't pay on your website, buy something yourself first, on a phone off Wi-Fi, and note exactly where it fails. Then check your payment provider's status page and dashboard, the webhook deliveries that confirm orders, and the site's security certificate. Undo the most recent change if one lines up. Never collect card numbers by email as a workaround.

On this page
  1. An outage with no error page and no complaints
  2. Buy something from your own store, start to finish
  3. Webhooks, the confirmation call your store may be missing
  4. The card-number workaround that creates a second emergency
  5. WooCommerce, Shopify and custom checkouts each break their own way
  6. Five fixes that cost more than the outage
  7. Getting the register open again: who to call and what it costs

An outage with no error page and no complaints

When a home page goes down, someone notices within the hour. When checkout breaks, the site looks perfect right up to the last click, and the only signal is an absence: orders that do not arrive. Owners find out from a sales report, a puzzled regular, or a bank deposit that looks thin. By then the leak has been running for days. Checkout fails in four distinct ways, and each one points at a different part of the machine.

The pay button does nothing

A script error, a cached page or a plugin conflict stops the form from submitting. The opposite failure is worse: a tampered outside script can skim cards from a checkout that still works, as it did on some sites in the Optimizely hack, while payment fields hosted by the processor stayed out of its reach. No payment attempt ever reaches the provider. Our card skimmer response handles a tampered checkout script, and our PCI payment page script work builds the inventory and change alerts that notice the next one.

Every card is declined

The store sends payments with wrong or expired keys, test keys in live mode, or to a provider account that has a hold on it.

Charged, but no order

The provider took the money, but the confirmation that creates the order never reached the site. Customers notice this one, angrily.

An order, but no payment

The site created the order and the charge failed or never happened. Ship it and you have given away stock.

For WooCommerce stores, the WooCommerce checkout walkthrough covers the script, caching and gateway causes in detail, and we will not repeat it here. This page is about the first hour, for any platform: finding which of the four you have, stopping the losses, and not making it worse.

Buy something from your own store, start to finish

No dashboard, log or plugin tells you as much as an honest purchase. Do it the way a customer does, on a device that is not logged in as an administrator. Keep a notepad open. The aim of this hour is to find where the money path stops and to keep customers from hitting the same wall.

  1. 1

    Place a real order on a phone off Wi-Fi

    Use a real card, a cheap product and a guest checkout if the store has one. Go all the way to the confirmation page and the confirmation email. Note the step that fails, the exact message and the time. Refund yourself later.

  2. 2

    Try a second way to pay

    If the store offers another payment method and it works, the fault sits with one provider or its settings, not the whole checkout.

  3. 3

    Check the provider's status page

    Stripe publishes a status page titled Stripe system status; most providers do. An incident there means waiting and posting a notice, not editing your site.

  4. 4

    Open the payment dashboard

    Look for payments in the last day: none at all, a wall of declines, or successful charges with no matching orders. Each points to a different card above.

  5. 5

    Check the webhook deliveries

    In Stripe, the destination's Event deliveries tab shows when the next retry of a failed delivery is due. Failures here mean the store is missing confirmations.

  6. 6

    Click the padlock

    An expired certificate breaks checkout for customers and the provider alike. The expired SSL certificate page covers the fix; if the domain itself lapsed, see domain and DNS emergencies.

  7. 7

    Undo the most recent change

    A plugin or app update, a theme edit, a deploy, a new shipping rule. If the failure started right after one, reverse that one change and test again.

  8. 8

    Tell customers the truth on the cart page

    Post a short notice with your phone number. Take any payment you can only through your provider's own hosted tools, never by collecting card numbers yourself.

Webhooks, the confirmation call your store may be missing

A webhook is the provider calling your site back to say the payment went through. Miss that call and you get the third card: charged, no order. Stripe's webhook documentation, as of November 2026, says it retries failed live-mode deliveries "for up to three days with an exponential back off," which is a mercy. It also says that if the destination has been disabled or deleted when a retry comes due, future retries of that event stop. Delete and recreate an endpoint in a panic and you may cut off your own backlog.

Webhook failures Stripe's documentation lists, as of November 2026, and what tends to cause them
What Stripe counts as failedHow it often happens on a small storeFirst thing to check
Redirect responsesOur reading: a switch to https or to www turns the old endpoint address into a redirectThat the endpoint URL in the provider matches the final address exactly
4xx responsesSignature checks failing, for example a test secret in production or a body altered before verificationStripe says test and live secrets differ, and verification needs the raw request body
5xx responsesThe site's code crashes while handling the eventThe site's error log at the time of the failed delivery
TLS errorsAn expired or mismatched certificate on the endpoint's domainThe certificate dates and the domain it covers
TimeoutsHeavy work done before the site answersStripe says to return a 2xx quickly, before complex logic
Layered colored-paper scene of a blank browser window with an empty shopping cart, a bandage across its lower corner and a small paper wrench beside it, soft shadows
Checkout can look fine on the surface while the confirmation behind it never arrives.

Once deliveries succeed again, the missed events need replaying and the orders need reconciling against payments. Our payment processing failing page walks through resending Stripe events and the subscription retries that sit behind a failed renewal, so we will not duplicate it here.

The card-number workaround that creates a second emergency

Every broken checkout produces the same well-meant idea: just have customers call or email their card details and we will run them by hand. Please do not. The PCI Security Standards Council says, on its merchant page as read in November 2026, that its standard applies to all entities that store, process or transmit cardholder data, regardless of size. A card number in an inbox or a spreadsheet is stored cardholder data, and now your email account is part of the problem.

Stripe's PCI guide, read in November 2026, says its Checkout and Elements qualify for SAQ A, the shorter self-assessment, because the card fields come from Stripe's own domain. Its security guide says a business handling sensitive card data directly might face more than 300 security controls. The safe workaround keeps cards out of your hands entirely: take payment through the provider's hosted pages or tools, and nothing else.

WooCommerce, Shopify and custom checkouts each break their own way

The first hour is the same everywhere. The second hour depends on what the store runs on, because the owner controls different switches on each platform.

  • WooCommerce: checkout lives inside WordPress, so plugins, caching layers and the gateway extension all share the blame. Our fixed-price theme, builder or plugin conflict repair is $199 on the WooCommerce checkout page; if the whole site is down, the site down repair is $249. The WooCommerce repair guide covers the rest.
  • Shopify: Shopify's status page lists Checkout as its own component, and warns, as of November 2026, that "Some issues affecting a small percentage of stores may not be reflected here." An unpaid Shopify bill can freeze a store, and Shopify's help says customers can't view a frozen store. The Shopify store down page covers both.
  • Custom and headless checkouts: the payment flow is your own code, so keys, environment settings and the webhook endpoint are the usual suspects. A recent deploy is suspect number one; see Next.js and React sites down for rolling back.
A store with no orders and no errors is not quiet. It is broken in a way that does not complain.

Five fixes that cost more than the outage

  • Switching the gateway to test mode to see if it works. Then forgetting to switch it back, so every customer gets a cheerful confirmation and you get no money.
  • Turning off signature verification to make webhooks pass. Stripe warns that without verification, an attacker could send fake events to trigger actions like fulfilling orders.
  • Deleting and recreating the webhook endpoint. Stripe generates a unique secret for each endpoint, so the new one needs a new secret in your site settings, and retries to the old one stop.
  • Refunding everyone in a panic. Reconcile first: some charges have orders, some do not, and some customers already received goods.
  • Updating every plugin or app at once. If the last update broke checkout, ten more updates bury the cause.

Each of these is a reasonable impulse with a nasty side effect. When in doubt, change one thing, buy something again, and write down the result. If checkout works but order emails or contact forms do not arrive, the forms stopped sending leads page is the next stop.

Getting the register open again: who to call and what it costs

Our response comes the same business day, inside the hours posted on our contact page. For WooCommerce, the Fix it now repairs above are paid online at a fixed price; we start within one business day of payment, with a full refund if we can't fix it. More WordPress options sit on the WordPress repair page.

Shopify, custom builds and headless stores are from $575, depending on complexity, with a written estimate before any work begins; the emergency pricing guide lists what raises or lowers it. A broken connection to a payment provider is an integration repair, and we restore those connections the same day once access is in hand. Before we call it done, we buy something, check the order, the email and the payment record, and refund it. The emergency website repair page lists the logins to gather.

Afterward, ecommerce development and API integrations cover longer projects, and the emergency repair overview shows every other kind of outage we take. DataCram has built for the web since 1999 from San Antonio, Texas, working with stores across the US by phone, video and a shared project page. Look through our work or call (210) 346-0848.

Questions owners ask in an emergency

Place a real order for a cheap item with your own card, follow it to the confirmation email and the payment record, then refund it. Test or sandbox modes are useful on a staging copy, but a gateway accidentally left in test mode on the live store is an easy way to break checkout, so switch back and buy once more.

Most likely the payment provider's confirmation, the webhook, never reached your site or failed when it arrived. Check the provider's webhook delivery log for errors. Stripe, as of November 2026, retries live-mode deliveries for up to three days with an exponential back off, so fix the endpoint quickly and then reconcile charges against orders.

Avoid it. The PCI Security Standards Council says its standard applies to every business that stores, processes or transmits cardholder data, and a card number in an inbox or spreadsheet is stored data. Take payment only through your provider's own hosted tools, and ask your provider which of them suit your situation.

Our Fix it now conflict repair, for themes, builders and plugins including broken WooCommerce checkouts, is $199 paid online, with a full refund if we can't fix it. If the whole WordPress site is down, the site down repair is $249. Other platforms and custom checkouts are from $575, depending on complexity.

A common reason is the webhook endpoint. Stripe's documentation says it treats redirect responses to webhook requests as failures, so an old endpoint address that now redirects to https or www stops confirming payments. Update the endpoint to the exact final address, and check the certificate covers it.

Check the provider's status page, then its dashboard. If payment attempts never appear there, the problem is on your site, before the provider. If attempts appear and fail, read the decline reasons. If payments succeed but orders are missing, look at webhook deliveries.

Keep reading

Free · No obligation

Tell us where the money stops

Describe the platform, the step where checkout fails and when it started. We reply the same business day with what we would check first and a price.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote