Orders and support

Refund requested, recorded, or still unresolved

They share it by naming the record, not by repeating the word refunded. A buyer's request is not a refund. In WooCommerce, a manual refund records the refund on the order and does not return money through the gateway. An automatic refund uses a compatible gateway, and the order status becomes Refunded only when the full order value is refunded. Changing the status to Refunded or Cancelled without the refund action does not return the money. On Stripe, a Refund object is pending, requires_action, succeeded, failed, or canceled. Stripe says a successful refund appears on the customer's statement in real time, depending on the card network and issuing bank. For a card refund, Stripe holds the refund as pending when the available balance does not cover it. Other payment methods can fail instead. The handoff names which of these is true, who owns the next act, and the date you will check again. It does not approve every request, and it does not promise a date the provider's document does not fix. 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 whose staff, store, and payment provider are not using the same refund status.

Updated 2026-09-21

Three sentences that are not interchangeable

Support can say that a buyer asked. The store can say that a refund row exists on the order. The payment provider can say that a refund object has a status. If those three sentences are collapsed into one, the buyer is told that money has moved when only a request or a store row exists.

This page coordinates that handoff. It does not classify whether the event is a reversal or a payment dispute, and it does not walk through a provider's dispute process. If you cannot tell which event you have, stop and identify the event before anyone promises a refund.

What WooCommerce records, and what it does not send

WooCommerce describes two paths. An automatic refund, available when the gateway supports it, returns the money through the payment method used and can set the order to Refunded in the same process. The order notes are where you look for the gateway's confirmation that the refund was processed. A manual refund records the order as refunded in the store. You still have to return the money in the gateway's own dashboard, or by a transfer outside WooCommerce. The order-status document says the same thing from the other direction: a manual refund can put the order in Refunded without the customer's funds having been returned.

Directly changing the status to Cancelled or Refunded does not refund the customer. A partial refund does not change the status to Refunded, and the email refers to a partial refund. A full refund uses the refunded wording. The email is another record. It is not, by itself, the provider's status.

Whether this order should be refunded is your decision under the policy you have published and the facts of the order. Nothing in the WooCommerce refund document says every request is approved.

What a Stripe status does and does not say

Use Stripe's words only when the payment was processed by Stripe. The Refund object's status is pending, requires_action, succeeded, failed, or canceled. requires_action means Stripe still needs information, such as bank details for some payment methods, before it can process. For card refunds, pending can mean the refund is waiting because the available Stripe balance does not cover it. Stripe says other payment-method types fail instead of waiting in that situation. failed means the bank or issuer could not process it and the amount can return to the Stripe balance. succeeded means Stripe's refund succeeded.

Stripe says it submits the refund to the customer's bank or card issuer, and that successful refunds appear on the customer's bank statement in real time, depending on the card network and issuing bank. That dependence is why a succeeded status is not a date you can promise, and why it is not a statement about any other provider. Refunds go back to the original payment method. A different provider's statuses are unknown until that provider's current document is open.

Do not copy the Stripe identifier, the full card number, or the customer's account details into the Prism form. The handoff can name the status and a reference your own staff can find in the provider dashboard.

How the next message should be written

The person who decides whether to refund writes that decision. The person who can press the gateway refund, or who must finish a manual return of funds, is named separately. Support tells the buyer only the record that exists: requested, declined under your policy, recorded in the store only, submitted to the provider, or still unresolved. The next date is a date your team will check the same records. It is not an arrival date.

Recurring mismatches are a reason to describe the store and the processing setup in a Prism consultation. Confirm who may authorize the refund and who is responsible for each provider action; a consultation does not establish that funds have moved. Scope, fees, and terms are discussed before work. The contact request does not submit a processing application.

Refund handoff

Use one real request. Write unknown when that record was not opened. Do not put a card number or a provider password in the sheet. 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.

Refund handoff. The last column is for temporary notes.
Status someone might say	Record that makes it true	Who still has to act	This case
Requested	Whether a refund request exists, its arrival time, and a non-sensitive description of its stage; keep the original message in the authorized support system.	The person named in your policy to approve or decline the request.	Requested: This case
Not approved	Your written decision and the policy term you used.	Support, to tell the buyer the decision. No provider action is required for a request you declined.	Not approved: This case
Recorded only in the store	A WooCommerce manual refund. The order can show Refunded while the gateway has not returned funds.	The person who can return the funds in the gateway dashboard or by the transfer your process uses.	Recorded only in the store: This case
Submitted to the gateway	The WooCommerce automatic-refund action, or the provider refund you created, plus any order note.	The provider, until its status is no longer waiting. A partial store refund does not set the WooCommerce status to Refunded.	Submitted to the gateway: This case
Provider pending or needs action	A Stripe status of pending or requires_action, or the equivalent status from another provider's document.	The provider, or the customer if that provider still needs details. Do not tell the buyer the statement already shows it.	Provider pending or needs action: This case
Provider succeeded	A Stripe status of succeeded, or the other provider's success word from its own document.	Support may say the provider reports success. Statement timing still depends on that provider. Stripe points to the card network and issuing bank.	Provider succeeded: This case
Provider failed or canceled	A Stripe status of failed or canceled, including the failure reason if the document shows one.	Your team, to decide the alternative. Stripe says a failed refund needs another way to return the funds.	Provider failed or canceled: This case
What the buyer was last told	The last message you sent, quoted, not paraphrased from memory.	Whoever speaks next uses this sheet rather than a new word for the same record.	What the buyer was last told: This case
Next check	A date your team will reopen the same store and provider records.	The named owner. The date is a follow-up, not a promise that funds have arrived.	Next check: This case

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 approve a request merely because it was made, and do not promise a date for funds to appear.
A WooCommerce status and a Stripe refund status are different records. Another provider's words are unknown until its document is open.
Do not send card numbers, provider passwords, or customer account records through the public form.

Related guides

Sources checked 2026-09-21

WooCommerce refunds — checked 2026-09-21. An automatic refund returns money through a compatible gateway. A manual refund records the store order and does not return gateway funds. Changing the status alone does not refund the customer. A partial refund does not set the status to Refunded.
WooCommerce order statuses — checked 2026-09-21. Refunded means the order value was fully refunded. A manual refund can reach that status without the customer's funds having been returned.
Stripe refunds — checked 2026-09-21. Stripe submits refunds to the bank or issuer. Statement appearance depends on the card network and issuing bank. Pending, requires_action, failed, and canceled are distinct, and a failed refund needs another way to return the funds.
Stripe Refund object — checked 2026-09-21. The refund status is pending, requires_action, succeeded, failed, or canceled.
Prism solutions — checked 2026-09-21. Public support is a storefront review, card-processing preparation, or help with a provider's website questions. The provider decides eligibility and account terms.
Prism contact — checked 2026-09-21. Scope, fees, and terms are discussed before work. The form is not a processing application and asks you to leave out card details, passwords, and customer records.

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.

Request a consultation All resources