Cancel or change an order after payment: check which action is actually available
Check the matching provider payment before choosing a store action. An uncaptured payment may have a cancellation route; money already captured requires the applicable refund process if you approve returning it. An existing pending refund must be traced before another action. Separately establish whether fulfillment can still be stopped or changed. Shipping does not itself convert an authorization into a capture, and a WooCommerce Cancelled or Refunded label does not itself return money. Tell the buyer which request you accepted, which action actually completed and which part remains unresolved.
For: An owner or support lead at a research-only merchant handling a buyer's cancellation or change request after a payment attempt.
Identify the requested change precisely: the whole order, selected items, a quantity or the delivery arrangement. Then match the store order to its provider payment using the recorded reference. Read the authorized amount, captured amount, any earlier refunds and the current payment state. A request to cancel the order is not evidence that the payment is still cancelable.
For Stripe, the refund documentation permits Dashboard cancellation when the payment is uncaptured. It describes refunding all or part after a payment succeeds. Other methods and states have their own cancellation conditions, so this is not a rule that every pending payment can be canceled through the same button. Use the action available for the actual payment and method; if that state is unresolved, investigate it before promising either cancellation or refund.
The authorized staff member should recheck the payment immediately before acting because capture or another refund may have occurred since support first read the order. Keep the result tied to the same reference. An order edit, a payment cancellation and a refund are separate records even when the buyer uses one word for all three.
Choose cancellation or refund from the amount already captured
When the payment remains uncaptured and the provider offers cancellation for that state, cancellation addresses the authorization. Record the provider's confirmed result before describing it as done. Do not capture merely to make a refund button usable. Check the actual authorization deadline and available actions rather than assuming a capture window applies to every country, card or integration.
A reduction before capture is a different choice from canceling the entire payment. Stripe's capture guidance says that capturing less normally releases the remainder, and most payments allow only one capture. Keeping the remainder available for later capture requires supported multicapture. A reduced order does not establish that the installed gateway supports that feature, and a later shipment does not authorize a second capture. Establish the intended final amount and actual support before any capture decision.
If the relevant amount was captured, use the approved refund route for that payment rather than relabeling it as an authorization cancellation. For Stripe, total partial refunds cannot exceed the original charge, and refunds return through the original payment method. Check earlier refund amounts before selecting the next amount. State the provider's actual refund result; a request or a store record alone does not establish that funds reached the buyer.
Run a separate fulfillment check
Captured but not shipped means there are two decisions: whether the authorized fulfillment owner can stop or change the work, and whether an approved amount should be refunded. Confirm the stop or change in the fulfillment record. A support message asking the warehouse to stop is not confirmation that the parcel stayed there.
If the parcel is already in transit, identify the actual shipment stage and the carrier or fulfillment process available for the requested change. If it is delivered, use the business's applicable return or remedy process. Neither stage reverses a capture or establishes a legal cancellation right. The buyer may need a shipment-stage conversation as well as a payment action, and the record should say which one is still open.
WooCommerce's order-status documentation says a Cancelled order can still need a refund and can return stock to store inventory when inventory management is enabled. Check that side effect against the physical goods before treating the inventory figure as usable stock. The financial action, application inventory and physical shipment must remain separately traceable.
Confirm the result before sending the buyer's answer
WooCommerce distinguishes automatic gateway refunds from manual refund records. Automatic refunds need gateway support; a manual record does not return funds through that gateway. Changing the status alone does not move money. A partial refund need not put the order into Refunded status, so inspect the amount and the matching provider record instead of using the order label as the final check.
If a refund is already pending, trace that refund before creating another. Stripe says insufficient available balance leaves card refunds pending, while other payment-method types fail in that situation. Canceling a pending refund is also different from canceling the original payment: availability depends on refund type and state, and some card refunds have only a short Dashboard cancellation window. Do not assume that changing the order or withdrawing the buyer's request cancels a refund already in progress.
The buyer's reply should name the accepted request, the confirmed payment action, the confirmed shipment action and the remaining follow-up. Distinguish a released authorization from a submitted refund, and a refund submitted from a refund's arrival on a statement. Set a time your team will check again if needed, without promising a bank posting date. Fee consequences belong to the actual provider terms; this decision sheet does not calculate savings from either route.
For repeated disagreements between the available payment action and the store's controls, bring the platform, gateway and a non-sensitive description to a Prism checkout-review consultation. Agree the investigation or implementation scope, responsibilities, fees and terms before work. Leave customer records and payment details out of the public inquiry.
Available-action check
Apply the relevant rows to one existing order. Record actual payment and fulfillment states, the approved action and the owner in the final column. Several rows can apply at once; a shipment row does not replace the payment row. Mark unknown when the responsible system has not been checked, and keep private references in authorized records.
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.
Available-action check. The last column is for temporary notes.
State or request
Record to inspect
Decision the record supports
This order's action
Authorized but not captured
Record to inspectThe provider's current authorization, amount, deadline and available cancellation action.
Decision the record supportsConsider cancellation only where supported for this state. Confirm its result; do not assume a store cancellation cancels the authorization.
Captured but not shipped
Record to inspectCaptured amount, prior refund records and confirmation from the fulfillment owner that dispatch can stop.
Decision the record supportsChoose the approved refund amount and separately confirm the fulfillment stop. Neither operation proves the other happened.
Shipped and in transit
Record to inspectThe payment state plus the actual dispatch or carrier event and the requested shipment change.
Decision the record supportsResolve the shipment-stage request under the applicable process. In-transit status does not undo a capture or authorize a refund by itself.
Delivered
Record to inspectDelivery evidence, the buyer's requested remedy and the applicable business process, alongside payment and refund history.
Decision the record supportsRecord the remedy decision separately from any refund action. Do not infer a legal right or a returned parcel from a status label.
Refund already pending
Record to inspectThe matching provider refund, amount, status and any stated blocking reason.
Decision the record supportsTrace the existing refund before another attempt. Do not assume that order cancellation cancels a pending refund.
Buyer's requested change
Record to inspectThe real request and whether it changes items, quantities, the whole order or only the delivery arrangement.
Decision the record supportsIdentify the financial and shipment actions actually needed. An uncaptured reduction requires a supported capture decision; it is not an automatic later second capture.
Store and provider result
Record to inspectWooCommerce refund type, amount and note compared with the corresponding provider result.
Decision the record supportsSeparate manual record, gateway request and confirmed result. Keep partial refunds visible even when the order status remains unchanged.
Buyer update and next check
Record to inspectThe actions actually completed, open uncertainty and the role responsible for follow-up.
Decision the record supportsExplain the verified stage and next check without promising that the issuer or bank will finish on that date.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
Payment-state examples describe Stripe and store-record examples describe WooCommerce. Check the actual method, gateway and account; no universal capture window or fee rule is supplied.
This operational choice does not decide legal cancellation rights, approve a money movement or establish provider eligibility for a research-only business.
Keep card numbers, authentication codes, bank details, private payment links and credentials out of the worksheet and public inquiry.
Stripe authorization and capture: partial capture boundary — checked 2026-09-29. Capturing less normally releases the remainder. Most payments allow one capture; retaining and capturing the rest requires supported multicapture. This does not establish gateway support or a universal authorization window.
WooCommerce refunds — checked 2026-09-29. Status changes and manual refund records do not move money. Automatic refunds require gateway support. Partial refunds need not change the order to Refunded; verify provider records separately.
Current WooCommerce order-status and draft behavior — checked 2026-09-29. The saved order-status document says a Cancelled order may still require a refund and returns stock when inventory management is enabled. Store status and stock effects do not establish provider movement of money.
Stripe refunds — checked 2026-09-29. The saved document distinguishes cancellation of uncaptured payments from refunds after success. Refunds use the original payment method and cannot total more than the charge. Insufficient available balance leaves card refunds pending; refund cancellation depends on type and state.
Get help with store operations
Need help with the order, email or fulfillment step itself?