A refund still in progress needs an answer about the actual stage rather than “we already sent it”. Check the payment operation, separate approval from execution and establish the next verification point. Do not guarantee a receipt date without a basis.
Refund approval does not establish a completed operation
The customer receives approval for a refund and later asks about the money. An operator sees the decision but not the payment history and replies “the funds are on their way”.
That adds an unverified fact. Establish whether the operation actually began before describing its progress. A conversation note alone is not the transaction result.
“In progress” can mean different things in different systems. Read the current operation state and its meaning in the solution being used. Do not transfer wording from a conversation into the payment system without checking it. Complaint handling covers the general decision route; the payment stage requires a separate check.
Scroll the table sideways to see all columns.
| Verified stage | What to communicate |
|---|---|
| Refund approved | The decision is confirmed; execution still needs checking. |
| Operation initiated | Identify its actual status and scope. |
| Operation processed | Confirm the system state, not visibility in the customer account. |
| Operation failed | Identify the outcome and appropriate verification route. |
Check what the refund concerns too. It may cover one line, part of the order or a particular amount. Do not say “the whole order was refunded” if the record shows only a part. Answer about the same operation the customer is asking about rather than a similar earlier case or another line in the order.
Check the relevant transaction before requesting new information
Begin with the order number and existing payment record. A complete bank statement is unnecessary for a simple store-side status check. Establish the amount, current status, completed action time and any error message. This distinguishes an operation never performed from one still being processed, without making the customer supply information you already hold.
- Match the operation.Check the order and particular refund entry. With several entries, compare scope and amount so the answer concerns the right one.
- Read status at its source.Use the store or payment-provider system according to the actual process. An approval note does not replace operation history.
- Check the message meaning.Do not translate pending as certain receipt today. Apply the current description and instructions for the provider used.
- Select the next verification point.Establish who will check progress or raise the issue with the relevant provider. Promise an action the team can actually control.
If you lack access, hand verification to an authorised person. Tell the customer the status is being checked instead of filling the gap with an assumption. Never ask for passwords, authorisation codes or full card numbers. Match the operation using the company’s established identification method, not a new improvised request for secrets. The same applies to BLIK codes, as explained in our guide to a BLIK payment missing in a Polish store.
Reply according to the stage actually verified
Approval without execution confirmation: “The decision to refund the specified amount is approved. We are checking execution confirmation; we do not yet have a basis to say the funds were sent. We will provide the actual operation status after review by the authorised person.” Use this only when the check will really be undertaken.
Processing: “We checked the refund for this order. The system shows the specified amount being processed. We do not yet have confirmation of completion or visibility in your account. The next action is another status check according to this provider’s instructions; we will share its result once established.” Do not add a guessed date to make the message sound complete.
Processed: “The payment system shows the refund as processed. It concerns the amount and operation identified in this conversation. That record does not confirm when the funds will appear for you. If they remain unavailable after the expected period for this method, we will check available confirmation and the appropriate next verification route.”
Failed: “The checked refund attempt did not complete successfully. We are not describing it as an executed refund. We are passing the exact error to the appropriate person or provider to establish the next action. We will not request a repeat operation before clarifying the available route.” Avoid sharing technical secrets contained in an error response.
Share provider guidance without guaranteeing receipt
Do not insert one universal number of days into every answer. Guidance can depend on provider, method and current state. If you share an indicative period, identify its source and conditions.
Keep an estimate distinct from a guarantee. A familiar figure found for another payment method does not become applicable to this particular refund.
A defined next check is often more useful than “please be patient”. You can confirm that the team will review status and report the result if it has an actual process for doing so. Do not turn receipt of funds into your own commitment when its timing depends on other systems. Name the step within your control.
If current instructions require contacting the provider, prepare only the relevant operation information. Avoid forwarding the entire conversation with unrelated private attachments. Preserve who received the question and what remains unresolved. Contacting a provider does not itself repair the operation; the customer should hear about a confirmed result when one becomes available.
This article explains communication about a refund already under review. It does not determine refund entitlement or recommend financial products. Return policy and purchase decisions covers store conditions; payment status is another question requiring the appropriate record. A policy decision cannot substitute for checking that record.
Record confirmed status and remaining uncertainty
In Meetlead customer support, conversations and tickets preserve the answer and operation context. You need an account, website and permissions. Meetlead does not process refunds or automatically read every store’s refund status. Verification takes place in the relevant payment system; the support record preserves what the authorised person established.
Distinguish approval, verified operation state and customer confirmation of receipt. These facts arise at different stages. Record the check time so another operator does not present an old result as current.
Avoid copying full payment details into the description. For a partial refund, identify the line so the next reply does not imply the entire order amount.
If the customer asks again, review the last check and establish whether the state changed. Do not send the same reassurance without verification. The WooCommerce customer support guide covers store work. Your explanation needs facts from the actual platform, rather than a universally promised timeline detached from its operation.
Remove assumptions about funds before sending
- The answer concerns the correct order and refund scope.
- Status was read from the actual operation system.
- Approval, execution and receipt are separate.
- Any stated period has an applicable source and conditions.
- The next action belongs to an identified authorised person.
- No unnecessary secrets or full statement were requested.
Another request requiring verification of an external operation is a delivery address change. Receipt of that request also does not establish execution. The response should follow the actual order state, just as refund wording follows the checked payment operation rather than the support message alone.
When the customer still cannot see the funds
Does processed mean money has arrived? Do not equate these facts. State the checked system status and the limits of that confirmation.
Establish customer-side visibility separately through the relevant route. The wording should make it clear which source provides each piece of information.
Should the refund immediately be repeated? Do not repeat an operation merely because the customer has not replied. First check the previous attempt and provider instructions.
A duplicate can concern the same scope; an authorised person makes the decision. Missing confirmation is not evidence that nothing happened.
What if status cannot be established? Say that verification is underway and identify the actual action. Do not turn approval into execution evidence.
Missing information calls for investigation rather than an invented reassuring explanation. Share the checked result when available instead of repeating a guess.
Shopify recommends checking order history and the particular refund record. Its instructions apply to the methods used there, not every payment: troubleshooting pending or failed refunds.
