Support patterns that deserve a checkout or processing review
Investigate a checkout or processing problem when more than one dated case shows the same mismatch at the same stage of the order. The customer's words are a report. The store's order status and the provider's payment status are separate records, and similar wording does not make them the same fact. You can group the cases you actually have. The provider decides what its own payment record means. One complaint, a shipping delay, or a missing email is not, by itself, this kind of pattern, and there is no published count that turns a report into a finding. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or authorized representative of a research-use-only peptide business who is reviewing repeated complaints about checkout or payment.
Updated 2026-09-21
Count dated cases, not the strength of the wording
A support message says what someone believes happened. It becomes evidence only when you can point to a store order, a payment record, or both, and write the date. WooCommerce shows orders to Administrator and Shop Manager users. An order is usually created when someone completes checkout, but an administrator can also add an order manually, and another system can create one through the REST API. Mark that origin in the tally. A manually created order is not a checkout result.
Two people using different words for the same order are one case. The same words on two orders are two cases. If you cannot find an order or a payment record, keep the message as an open report and do not invent the missing record. This page does not set a minimum number of cases. One unexplained order can still need its own investigation. It is not yet a pattern.
Read the store status and the payment status as different facts
WooCommerce uses Pending payment when the order is received and no payment has been made, Failed when the payment failed or was declined and no payment succeeded, and On hold when the order is awaiting payment confirmation. Processing means WooCommerce has recorded the payment as received and the order is awaiting fulfillment. Completed means the order has been fulfilled. Refunded means an admin or shop manager fully refunded the order's value after payment. The manual-refund option can reach Refunded without the customer's funds having been returned. Failed and On hold may not update immediately when the gateway uses a delayed notification.
Those are store statuses. If the payment record is a Stripe PaymentIntent, Stripe uses a different list. A succeeded PaymentIntent means that payment flow is complete and the funds are in the Stripe account. After a failed attempt, the PaymentIntent can return to requires_payment_method so it can be retried. Processing, in Stripe's list, means an asynchronous method is not finished and can take days. Do not copy those words onto a WooCommerce order. If the provider is not Stripe, or the record is not a PaymentIntent, leave the provider's result in that provider's own words.
A missing payment method is a checkout fact, not a decline
Some repeated complaints happen before an order has a payment status. WooCommerce's cart and checkout documentation says that if the only enabled payment gateways are incompatible with the Checkout block, no payment method is available at checkout. Compatibility for an extension sold on WooCommerce.com is marked on that extension's product page. Cart and checkout are paired: the documented way back to the classic shortcodes is to change both pages.
A repeated 'no way to pay' report is a reason to compare the checkout type with the gateway that is actually enabled. It is not a statement that a provider declined the business. A gateway that does not appear is also not proof that a different gateway would be accepted.
Leave shipping and email reports out of this tally unless payment also disagrees
WooCommerce sends particular emails when order statuses change. A missing email can be a real store problem, and a shipping delay can be a real fulfillment problem. Neither one is a checkout or processing pattern unless the payment record and the store status also disagree. Do not relabel those reports as declines, refunds, or disputes to make them fit this page.
You can decide which dated cases share a symptom and a stage, and whether the next question goes to the person who maintains checkout or to the provider named on the payment record. The provider decides the payment result and any effect on the account. The cause stays unknown while the store status and the provider record have not been read together. A Prism consultation can discuss the pattern and the storefront or processing question. Scope, fees, and terms are discussed before work. The consultation does not decide the payment result.
Repeated-case tally
Use one row for each symptom you have actually seen. In the last column, list dates and order references from your own records, or write that you have only one case. Do not type card numbers or a customer list. Leave a row blank when you have not seen that symptom. 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.
Repeated-case tally. The last column is for temporary notes.
Observed symptom
Order stage it touches
What the report still is not
Your dated cases
Customer says the payment went through, while the store order is Pending payment, Failed, or On hold.
Order stage it touchesThis is the payment stage, before fulfillment. Pending payment means no payment has been made. Failed means WooCommerce recorded no successful payment. On hold means the store is still awaiting payment confirmation.
What the report still is notThe customer's sentence is not a store status and not a provider status. One order with this mismatch is a single case, not a pattern.
The store order is Processing or Completed, while the customer reports a second charge.
Order stage it touchesProcessing means the store recorded payment as received and is waiting for fulfillment. Completed means the store recorded the order as fulfilled. Neither status counts the provider's payment attempts.
What the report still is notTwo complaints are not two confirmed payments. Compare the store order with the provider's payment record before naming a cause.
More than one order remains On hold or Failed, and the order notes do not name a payment result.
Order stage it touchesOn hold can come from an offline method, a delayed notification, or separated authorization and capture, depending on the gateway. Failed can appear later when a delayed payment is rejected.
What the report still is notA stack of store statuses is a reason to read the gateway record. It is not a decision about the merchant account.
A customer says an order was refunded, but the funds record is a different fact from the store status.
Order stage it touchesRefunded means an admin or shop manager fully refunded the order value after payment. A manual refund can set that status without returning funds.
What the report still is notA request, a store status, and money returned are three facts. Repeating disagreement is the pattern. The tally does not decide a dispute.
Checkout offers no payment method on more than one attempt.
Order stage it touchesThis happens at checkout, before a paid order exists. It can occur when the only enabled gateways are incompatible with the Checkout block.
What the report still is notA missing payment option is an extension and checkout-type fact. It is not evidence that a provider declined the business.
The repeated report is a shipping delay or a missing email, and the payment records do not disagree.
Order stage it touchesShipping sits after Processing, when the store is awaiting fulfillment. Email is sent when particular statuses change, and that setting is separate from the payment record.
What the report still is notThese can be real problems. They do not belong in a checkout or processing tally unless the payment record and the store status also disagree.
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.
There is no industry benchmark and no minimum complaint count on this page. A blank row means you have not recorded that symptom.
Stripe PaymentIntent statuses apply only to a Stripe PaymentIntent. They are not a translation table for every provider.
Do not send payment-card data, passwords, or customer lists through the public form.
WooCommerce order statuses — checked 2026-09-21. Pending payment, Failed, On hold, Processing, Completed, and Refunded have the store meanings used on this page, including delayed updates and manual refunds that do not themselves return funds.
WooCommerce managing orders — checked 2026-09-21. Orders are visible to Administrator and Shop Manager users. They are usually created at checkout, and they can also be added manually in WP Admin.
Stripe PaymentIntent lifecycle — checked 2026-09-21. A succeeded PaymentIntent means that payment flow is complete and the funds are in the Stripe account. A failed attempt can return the status to requires_payment_method. Processing applies to asynchronous methods and can take days.
WooCommerce cart and checkout blocks — checked 2026-09-21. If the only enabled payment gateways are incompatible with the Checkout block, no payment method is available. Extension compatibility is marked on the WooCommerce.com product page. Classic shortcode rollback applies to both cart and checkout.
Prism solutions — checked 2026-09-21. Public support is a storefront review, preparation for a processing review, or help with a provider's website questions. The provider decides eligibility and account terms. Scope is established in the consultation.
Prism features — checked 2026-09-21. The provider determines eligibility, approval, and account terms through its own underwriting. A website review is informational and does not guarantee approval or continued processing.
Prism contact — checked 2026-09-21. The form asks for the website, products, and question. Follow-up is by email. A request does not book an appointment, purchase a service, or submit a processing application. Card details, passwords, and customer records should be left out.
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.