---
title: Payment Gateway Down? A Backup Plan for Online Stores Before Black Friday
description: What to do when your payment gateway is down — confirm the cause, switch to a tested backup payment method, tell customers, and reconcile orders afterwards.
source: https://pingvera.com/blog/payment-gateway-down-backup-plan.html
---
# Payment Gateway Down? A Backup Plan for Online Stores Before Black Friday

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.

## At a glance

- A payment outage rarely takes the whole site down. Uptime checks stay green while orders fail or never arrive.
- Outages can hit one payment method inside a healthy processor. Stripe's status history shows PayPal and three other methods unavailable for about half an hour on 18 November 2025.
- The backup plan has three parts: a second payment method already live at checkout, a written switch procedure, and a reconciliation step for the outage window.
- WooCommerce lets you enable several payment providers and reorder them in WooCommerce > Settings > Payments. Shopify allows a third-party credit card provider alongside Shopify Payments, with a restriction for some US stores.
- Stripe retries undelivered webhooks for up to three days in live mode, so orders may change status hours after the outage ends.
- Decide who switches, who tells customers and who reconciles before the peak, and write their names into the runbook.

## Why it matters now

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](https://pingvera.com/blog/woocommerce-failed-orders.html). The patterns there are the same signals you watch for during a gateway incident.

## Step by step: prepare this week

1. List every payment path. Write down each method shown at checkout, which provider processes it, which plugin or app connects it, and which webhook endpoint receives its events. Include express buttons such as wallets, which often run through a separate component.
2. Add a second, independent method. Pick one that does not share the failing dependency. If cards run through one processor, a wallet or card option through a different provider is a real backup. A second method routed through the same processor protects you against fewer failure types.
3. Get it approved and live now. Complete the provider's onboarding and verification, enable the method, and place one real low-value order through it. Refund it afterwards. Do not leave this step for the outage.
4. Decide how the backup is shown. On WooCommerce, enabled providers appear at checkout in the order you set with the drag handle in WooCommerce > Settings > Payments, so the backup can sit visibly second. On Shopify, check that your store qualifies for a third-party provider: Shopify's help centre says US stores whose sales tax is managed by Shopify cannot use third-party payment providers until sales tax is set to self-directed. On Magento or custom builds, confirm with your developer how a method is disabled and re-enabled without a deploy.
5. Subscribe to status updates for every provider in your list and route them to the person on call, not a shared inbox nobody reads at weekends.
6. Know your normal numbers. Note your typical orders per hour and failed-payment share for the same weekday and hour. During the incident you will compare against these.
7. Write the runbook (template below), store it outside the store admin, and run a 15-minute dry run with whoever will be on call.

## During an outage: confirm, switch, tell, watch

1. Confirm the fault. Check the provider's status page, your recent failed orders, and the provider's dashboard for declined or errored attempts. Place one test order with the affected method.
2. Separate your fault from theirs. If only your store is affected and the provider shows no incident, look first at recent deploys, plugin updates, expired API keys and webhook delivery errors. [Orders marked as paid without payment](https://pingvera.com/blog/orders-marked-paid-without-payment.html) covers the webhook side in detail.
3. Switch. Disable or move down the failing method so customers land on the working one. If cards are failing and the only backup is a wallet, add a short notice at checkout that names the method that works.
4. Stop sending traffic into the problem. Pause scheduled campaign emails and, if the outage is long, reduce paid ad spend pointing at product pages.
5. Tell customers once, plainly. Use a site banner and a reply template for support. Do not promise a recovery time you do not know.
6. Log times. Record when you noticed, when you switched and when the provider resolved. Reconciliation needs this window.

## After recovery: reconcile

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.

## Who owns what

## Copyable runbook

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.

## A worked scenario (illustrative)

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.

## Common mistakes

- Signing up for a backup provider during the outage. Verification can take longer than the outage itself.
- Choosing a backup that shares the failing dependency, such as a second method routed through the same processor and plugin.
- Leaving the backup disabled until needed, so nobody knows whether it still works.
- Treating a green uptime check or an empty status page as proof that payments work.
- Re-enabling the primary method without a test order.
- Reconciling once on the day and missing orders that change status when delayed webhooks arrive.

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.

## FAQ

### How do I know if my payment gateway is down or if it is my store?

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.

### Can I run two payment gateways at the same time?

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.

### What happens to orders placed during the outage?

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.

## Pingvera

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](https://pingvera.com/blog/woocommerce-checkout-monitoring.html) explains the setup, and [Is Shopify down?](https://pingvera.com/blog/is-shopify-down-outage-checklist.html) covers platform-wide outages.

## Sources

- Stripe status, "Elevated errors for Multiple Payment Methods", 18 November 2025: https://www.stripestatus.com/incidents/l2rfd306b763
- Stripe status subscriptions: https://www.stripestatus.com/
- Stripe Docs, webhooks (retries and resending events): https://docs.stripe.com/webhooks
- Stripe API reference, idempotent requests: https://docs.stripe.com/api/idempotent_requests
- Shopify Help Center, third-party payment providers: https://help.shopify.com/en/manual/payments/third-party-providers
- Shopify status page: https://www.shopifystatus.com/
- WooCommerce documentation, configuring WooCommerce settings (Payments): https://woocommerce.com/document/configuring-woocommerce-settings/

Last reviewed: 2026-11-05
