
When your payment gateway is down, the store stays online and keeps taking carts, but customers cannot pay. First confirm where the fault is: the provider's status page, your own failed-payment rate, and one real test transaction. If the provider is at fault, move customers to a second payment method that you set up and tested before the incident. Pause paid traffic and campaign emails that send people into a broken checkout. Once the provider recovers, reconcile every order created during the window against the provider's records.
A backup only helps if it already exists. A second provider usually needs an account, an application and a test order before it can take live payments, so the latest sensible time to prepare is the first half of November. Black Friday falls on 27 November 2026 and Cyber Monday on 30 November 2026.
Peak weekend concentrates revenue into a few days, so a 30-minute payment problem costs more on 27 November than on an ordinary Tuesday. The problems also do not always start with your own provider.
On 18 November 2025, Stripe's status page recorded an incident titled "Elevated errors for Multiple Payment Methods". Between 11:35 and 12:08 UTC, PayPal, Alma, FPX and PayTo had brief periods of unavailability, which Stripe attributed to a widespread outage external to Stripe. A store taking cards through Stripe kept working for card payers, while customers who chose PayPal through the same integration saw errors. The lesson for store operators is that "the gateway" is several dependencies: the processor, each payment method behind it, the plugin or app that connects them, and your webhook endpoint.
Status pages help, with a limit. Shopify's status page states that "some issues affecting a small percentage of stores may not be reflected here." Stripe's status site offers email, text message, Slack and RSS subscriptions, which is useful for early warning, but your own order data will often show a problem first.
If you have not yet read how failed orders behave, see WooCommerce failed orders: what a spike, a stall and a silence each mean. The patterns there are the same signals you watch for during a gateway incident.
Stripe retries webhook events for up to three days in live mode with exponential backoff. You can resend an event from the Dashboard for up to 15 days after it was created, and from the Stripe CLI for up to 30 days. So an order created during the outage can move from pending to paid, or to failed, long after the incident closes. Export every order created during the window and match it to a charge or payment in the provider's dashboard. Look for three mismatches: paid in the provider but unpaid in the store, paid in the store with no payment behind it, and duplicate charges from customers who retried.
If your integration creates payments through your own code, Stripe's idempotency keys let you retry a request "without accidentally performing the same operation twice." Ask your developer whether retries in your checkout use them.
| Risk | Owner | Check | Frequency |
|---|---|---|---|
| Primary card provider unavailable | Store owner | Status subscription active; backup method enabled and tested | Weekly in November, daily on peak days |
| Single method (for example a wallet) failing inside a working processor | Ecommerce manager | Failed-payment share by method compared with normal | Hourly on peak days |
| Webhook endpoint failing after a deploy | Developer or agency | Webhook delivery status in the provider dashboard | After every deploy |
| Backup provider account suspended or unverified | Store owner | Log in, confirm account status, place a test order | Once before peak |
| Orders stuck in pending after recovery | Operations | Reconcile outage window against provider records | Within 24 hours of recovery, again after 3 days |
PAYMENT OUTAGE RUNBOOK (store: ________ last tested: ________)
On call: ________ (phone ________)
Can change checkout: ________
Customer messages: ________
Reconciliation: ________
Payment paths
Method Provider Plugin/app Webhook URL Status page
________ ________ ________ ________ ________
Normal numbers (same weekday and hour)
Orders per hour: ____ Failed-payment share: ____%
1. CONFIRM (target: 10 min)
[ ] Provider status page checked
[ ] Failed orders in the last 30 min reviewed
[ ] One test order placed with the affected method
[ ] Recent deploys / plugin updates / key changes ruled out
2. SWITCH
[ ] Failing method disabled or moved down
[ ] Backup method visible at checkout, test order placed
[ ] Checkout notice added naming the working method
3. CONTAIN
[ ] Scheduled campaign emails paused
[ ] Paid traffic reviewed
4. TELL
[ ] Site banner live
[ ] Support reply template shared
5. RECOVER AND RECONCILE
[ ] Provider marked resolved; failing method re-enabled and tested
[ ] Banner and notices removed
[ ] Orders in window exported: from __:__ to __:__ (UTC)
[ ] Matched against provider records; mismatches listed
[ ] Re-check after 3 days for late webhook updates
Banner text you can adapt:
Some card payments are failing because of a problem at our payment provider. You can still order using [working method]. We are watching it and will remove this notice once cards work again.
The numbers here are invented for illustration. A homeware store normally takes about 40 orders an hour on a Saturday in late November, with roughly 3% of payment attempts failing. At 14:10 the on-call manager sees 9 orders in the last half hour and a failed share near 40%, almost all of them card payments. The card provider's status page shows nothing yet.
The manager places a test order and gets a card error. No deploy happened that day. At 14:22 they move the wallet option, set up and tested two weeks earlier through a different provider, to the top of checkout, add the banner, and pause a campaign email due at 15:00. Orders recover to about 30 an hour through the wallet. The provider posts an incident at 14:35 and resolves it at 15:20. On Monday, the reconciliation lists 6 orders that were paid in the provider dashboard but still pending in the store, all updated by later webhook deliveries, and 2 duplicate charges that support refunds.
This plan has limits. A second provider adds fees, another dashboard and another account to keep in good standing. It does not help when the cause is your own code, a hosting problem or an expired domain, so keep the "your fault or theirs" step. Payment providers' terms differ by country and business type, and this article is operational guidance, not legal or financial advice.
Compare three things: the provider's status page, your failed-payment share against your normal level, and a test order. If the provider shows an incident and other methods work, the provider is the likely cause. If only your store fails and nothing is posted, check recent deploys, plugin updates, API keys and webhook delivery first.
Usually yes. WooCommerce lets you enable several providers and order them at checkout. Shopify allows a third-party credit card provider alongside Shopify Payments, except for US stores whose sales tax Shopify manages. On custom platforms, it depends on how the checkout was built.
Some fail, some stay pending and some complete later when the provider delivers delayed webhook events. Stripe retries for up to three days in live mode. Reconcile the window against provider records once on recovery and again after three days.
If you maintain WooCommerce stores, Pingvera's WordPress connector sends order.created and order.failed events and compares the order rate with an hourly baseline, so you get an alert when the site is up but customers stop completing orders. Deploys and incidents appear on the same timeline, which helps with the "your fault or theirs" step. WooCommerce checkout monitoring explains the setup, and Is Shopify down? covers platform-wide outages.
Last reviewed: 2026-11-05
Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.
Start freeRead next: Stripe API Version Upgrade: A Safe Pre-Peak Plan · Website Stress Test Before Black Friday: Store Plan · How to Test a Website Backup Restore · Marketplace and Store Reconciliation · Check availability from several regions.
Read next: Stripe API Version Upgrade: A Safe Pre-Peak Plan · Is Cloudflare Down? An Outage Plan for Online Stores · Stripe Payment Declined? Diagnose Declines Before Peak · How to Test a Website Backup Restore · Check availability from several regions.