Support and returns
Your Refund Has Been Sent: A Shopify Email That Sets the Right Expectation
A refund confirmation should tell the customer what the merchant has actually done: the amount, currency, original order, destination, and verified transaction status. It should also explain that merchant initiation and visible bank posting are different events.
Send the message after checking the payment record. A support promise, an approval note, and a refund transaction are not interchangeable. If the refund is still waiting for internal approval, describe that state accurately instead of using a subject line that says the money has been sent.
Confirm the amount and the order scope
Start with the order reference and the exact refund amount in its currency. Identify whether the credit concerns the whole purchase, specific items, shipping, or another agreed adjustment. Customers should not have to infer the scope from a number that differs from the original order total.
Shopify supports full and partial refunds. Use the actual completed merchant action as the basis for the message. Shopify refunding orders.
Check earlier credits before writing. If the customer already received a partial refund, distinguish the new amount from the cumulative amount. A message saying “refunded 50” can be confusing when 20 was previously refunded and the current action is only 30.
For a mixed-payment order, describe the confirmed destinations separately where relevant. Do not imply that every refunded unit of currency went to a card if some went to a gift card or agreed store credit. Use only the identifying detail needed for recognition, such as a masked payment reference supplied by the actual workflow.
Explain processing without inventing a bank deadline
Use the payment provider’s current guidance for the relevant method and region when describing expected posting. Avoid a universal promise that every customer will see money within the same number of days. Weekends, payment-method behavior, and provider processing can affect how an individual credit appears.
Stripe, for example, documents refund status and tracing in its own payment workflow. Those details apply to the relevant Stripe arrangement, not automatically every Shopify payment. Stripe refund documentation.
As a customer-communication principle, separate what you can confirm from what the customer may observe. “We initiated the refund on this date” is a merchant fact. “Your bank has credited your account” requires confirmation of that event. If the actual provider status is pending or failed, the merchant should investigate and send wording that matches it.
Explain that the customer should check the original payment method or the specific agreed destination. If a card has been replaced or closed, follow the provider’s documented guidance and refer the customer to the appropriate financial institution for account-specific handling. Do not collect new card details through an email reply.
A reusable refund confirmation email
Use this template only when the refund action and status have been verified. Replace the bracketed fields with actual information.
Subject: Refund update for order [order reference]
We have [accurate action and status] a refund of [amount and currency] for order [order reference] on [date].
This refund covers [items, quantities, shipping, or adjustment]. [If relevant: An earlier refund of amount and currency was issued on date; today’s amount is additional to that refund.]
The refund destination is [confirmed original payment method or other expressly agreed destination, using limited identifying detail].
The merchant refund action and the payment appearing in your account are separate stages. Based on [the applicable provider’s current guidance], the expected posting information is [accurate expectation or link].
If you still cannot locate the credit after that relevant period, reply to this message. We will check the transaction status and provide any available reference that your payment provider can use to trace it.
[Support owner or team]
In a hypothetical example, an order total was 120 units of currency and the merchant refunds a returned item worth 40. The confirmation names that item and says that 40 was refunded. It does not say the order was fully refunded or imply that the remaining goods have been canceled.
Check the message the customer actually receives
Review the standard notification and any separate support email together. If the system sends one amount while support describes another, correct the discrepancy before sending a second explanation. Avoid duplicate messages that appear to confirm two different refunds when only one transaction exists.
The sender and reply route should be recognizable and monitored. Customers with a missing-credit question should be able to continue the conversation without finding a new contact form. Keep the order reference in the subject or body so staff can locate the correct payment without requesting unnecessary details.
Do not attach an unredacted internal payment export to make the message look authoritative. A concise amount, date, destination, and status is usually more understandable. Provide a trace reference later if the actual provider makes one available and it is useful for the customer’s investigation.
Before closing the support task, check that the financial action, order scope, and wording agree. That final consistency check prevents a refund confirmation from creating a new misunderstanding about what was returned, where it went, or whether the rest of the order remains active.
Explore Lower Chargeback for visibility into dispute reasons and status alongside your merchant workflow.
Related reading in this collection: