Record the page, the time you first saw the failure, the checkout step, the exact error, who owns the status, and the next time you will update it. Tell customers only what you have confirmed. Separate a failure on your store from an incident a vendor has actually posted. Stripe's public status page is one place to look, and its first response can be a loading screen rather than an incident list. Do not publish a second checkout or a different payment path while you investigate. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or operator of a research-use-only peptide store whose live checkout cannot complete an order.
Updated 2026-09-21
Write the failure you can see
An outage note starts from observation. Record the checkout URL, the first time the failure was seen, the step that failed, whether a customer could reach payment, the words of any error, and whether you can reproduce it. WooCommerce's self-service guide uses the same kind of questions when it asks support to collect when the problem was first noticed, whether updates, theme changes, or new plugins came first, whether it happens on more than one device, whether it is one browser or all of them, and whether there is a screenshot of the error.
Those questions also stop the team from treating a single browser on one computer as a storewide outage. If you cannot yet reproduce it, say that. Do not announce that checkout is down for everyone until someone has checked more than one path.
Separate your store from a vendor incident
WooCommerce's system status report describes software installed on your site and the server hosting it, including the WooCommerce version and the web server. A checkout failure can therefore be local to that installation, a plugin, or the host. The self-service guide says almost half of the support interactions it describes come from conflicts with a third-party theme or plugin, and it asks whether anything was updated immediately before the problem. A recent update is a lead. It is not, by itself, the cause.
For the payment provider, open that provider's status page and copy an incident only after the page displays one. Stripe's status address, https://status.stripe.com, returned a page titled Stripe system status whose body said Loading when checked on 2026-09-21. A loading screen is neither an all-clear nor an outage. Wait until a status is visible, or use the notice the provider sent you. This guide does not cite a WooCommerce-wide status board. Your host may have its own notice. Copy that notice rather than guessing.
The self-service guide describes a conflict test that deactivates plugins. Do not start an outage by turning off payment, fraud, or required notices on the live store. WooCommerce's Health Check document says its troubleshooting mode does not sandbox the payment gateway, so a test order can take a live payment. Restoration work belongs with the person who maintains the site and with the vendor whose component failed.
The customer message uses confirmed facts
Decide who may speak for the store and the next time that person will update the message. The message can say that checkout cannot take an order, the time that was last confirmed, and where an existing customer can ask about an order that was already placed. It cannot promise a restoration time unless a vendor's posted incident states one, and it cannot blame a vendor you have not confirmed.
Stripe's dispute-prevention guidance says customer-service contact should be easy to find and that customers should be updated through the order. That is a reason to keep the contact path available. It is not a script for this incident, and it does not authorize a new payment method. Do not ask customers to pay through a private message, a different website, or a description that hides the business.
What this outage does not authorize
You can assign an owner, keep the timeline, and tell customers the confirmed facts. You cannot restore the provider's systems, and you should not open a second, hidden checkout while the first one is being fixed. A payment provider's account status is a different problem from a page that will not load. Do not treat them as the same incident.
Prism's contact page accepts a consultation request and follows up by email. It does not book an appointment, and the public pages do not promise round-the-clock incident help or a restoration time. Sending the form does not repair checkout. Whether the payment provider will keep the account, and when the software vendor will fix a defect, stay unknown until those parties say so.
Checkout incident worksheet
Complete this while the checkout failure is being worked. Write unknown when you have not confirmed the fact. Do not put card numbers or customer lists in the notes. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Checkout incident worksheet. The last column is for temporary notes.
Outage fact
Why the team needs it
What the customer message may say
Your note
What failed and where
Why the team needs itThe URL and the checkout step stop the team from treating every page as down.
What the customer message may sayYou may name the step you confirmed. Do not describe a step nobody has opened.
First time seen
Why the team needs itThe start time separates a new failure from an old one. WooCommerce's support questions begin with when it was noticed.
What the customer message may sayYou may say when it was last confirmed. Do not invent when it began.
Who else can reproduce it
Why the team needs itOne browser is not a storewide outage until someone checks another device or browser.
What the customer message may sayIf it is not yet reproduced, say the report is being checked.
The error text
Why the team needs itThe words on the screen are the fact. A paraphrase can send the vendor to the wrong component.
What the customer message may sayDo not quote an error you do not have. A screenshot belongs with the person handling the vendor case.
Recent changes
Why the team needs itThe self-service guide asks about updates, themes, and new plugins before the problem.
What the customer message may sayDo not tell customers a plugin caused it until that is confirmed.
Vendor status
Why the team needs itCopy a posted incident only after the status page or the vendor's notice shows it. Stripe's status page can load before it shows a status.
What the customer message may sayDo not say the provider is down, or that it is healthy, from a loading screen.
Case owner and next update
Why the team needs itOne person owns the message, and the team needs the next time it will change.
What the customer message may sayTell customers when you will update them. Do not promise when checkout will return.
What you will not open
Why the team needs itA second checkout or a private payment path is not a status update.
What the customer message may sayThe message does not offer an unannounced payment method.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
Do not publish a hidden checkout, a disguised payment description, or an unapproved payment method.
Do not turn off fraud controls or payment protections as the first response.
WooCommerce self-service guide — checked 2026-09-21. Almost half of the interactions described are third-party theme or plugin conflicts. Support questions include when the problem started, recent updates, theme changes, new plugins, devices, browsers, and the error. The guide also describes a deactivation test.
WooCommerce system status report — checked 2026-09-21. The report describes the WooCommerce version installed on the site and the server hosting it, so a checkout failure can be local to that installation.
Stripe system status — checked 2026-09-21. The public status page is titled Stripe system status. On this date its initial response body said Loading, so a status was not yet displayed.
WooCommerce Health Check troubleshooting — checked 2026-09-21. Troubleshooting mode does not sandbox the payment gateway. An order placed during it can take a live payment.
Stripe dispute-prevention best practices — checked 2026-09-21. Stripe says customer-service contact should be easy to find and that customers should be kept updated through the order and about deliveries.
Prism contact — checked 2026-09-21. A consultation request is followed up by email. It does not book an appointment, purchase a service, or submit a processing application. No incident-response hours are stated.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.