Ecommerce refund support guide
Refund approved but not received response templates
Opening
A missing-refund message is different from a refund request. The refund may already be approved in your store record, but the buyer still needs a calm explanation of processor timing, the safe reference details you can share, and the next support checkpoint. The safest reply confirms what your system shows, avoids collecting payment credentials, and does not promise a deposit date controlled by a bank, card issuer, wallet, marketplace, or gateway.
This guide is for support wording only. It does not change checkout, pricing, Gumroad files, DNS, email systems, credentials, OAuth, tax, payout, refund policy, customer accounts, payment handling, payment gateway settings, processor rules, chargeback handling, bank timelines, or marketplace permissions.
Example 1: refund approved today
Hi [customer name],
Thanks for checking in. I can see that the refund for order [order number] was approved on [date].
Refunds can take time to appear after approval because the payment processor, card issuer, bank, wallet, or marketplace account may post the credit on a separate timeline. We will keep the refund record open and follow up by [timeframe] if it still does not appear.
Thank you,
[store name]Use this when the approval is recent and you need to explain the gap between approval and buyer-visible posting.
Example 2: buyer says their bank has no refund
Hi [customer name],
I understand your bank is not showing the refund yet. Our record shows the refund status as [status] on [date] for order [order number].
Please check the original payment method and statement activity for that date range. If you send a screenshot, please hide card numbers, bank details, balances, transaction IDs, and unrelated personal information.
If the refund is still not visible by [date], we will review the refund record again and confirm the next support step.
Thank you,
[store name]Use this when you need to acknowledge the bank-side view without asking for sensitive financial records.
Example 3: refund reference available
Hi [customer name],
Thanks for your patience. The refund for order [order number] shows as [processed/settled/submitted] in our system on [date]. The safe reference we can share is [refund reference or last-safe identifier].
This reference may help when you contact your payment provider, but please do not send us card numbers, passwords, bank login screenshots, or payment-app credentials.
We will check this record again by [timeframe] if your provider still cannot see the refund.
Thank you,
[store name]Use this only when your platform exposes a safe, non-secret refund reference. Do not invent a reference if your system does not provide one.
Example 4: marketplace or wallet refund delay
Hi [customer name],
I checked order [order number], and the refund is marked [status] on [marketplace/wallet/payment platform] as of [date].
Some platforms show the refund in account balance, original payment method, or order history at different times. Please check the original payment route and any platform refund history screen that you normally use.
If it is still not visible by [date], reply here and we will review the support record again.
Thank you,
[store name]Use this when the buyer paid through a marketplace, wallet, or hosted checkout where posting locations can vary.
Example 5: refund amount or partial refund confusion
Hi [customer name],
Thanks for the note. I see a refund record for [amount] on order [order number]. If the amount you see is different, we should compare the order total, shipping, discounts, taxes, fees, and any partial refund already processed.
Please send the refund approval message date or the order page view with unrelated personal details hidden. We will review the amount and confirm the next support step by [timeframe].
Thank you,
[store name]Use this when the buyer may have received a partial refund, fee adjustment, or split refund rather than no refund at all.
Example 6: follow-up after the stated window
Hi [customer name],
Thanks for waiting. We reviewed the refund record again after the follow-up window. The current status is [status] from [date].
The next step is [processor review / marketplace support check / internal payment record review / documentation resend]. We will update you by [date] with the result of that review.
Thank you,
[store name]Use this when the buyer has already waited through the first support window and needs a defined escalation path.
Refund-not-received checklist
- Confirm that the refund is actually approved or processed before using this guide.
- Quote the approval, submitted, processed, or settled date from the support record.
- Explain that bank, card, wallet, marketplace, and gateway posting times can differ.
- Share only safe refund references that your platform exposes; never invent processor details.
- Ask for minimum useful evidence with sensitive payment details hidden.
- Give a support follow-up date instead of promising a bank deposit date.
- Move amount disputes to a partial-refund or refund-process path instead of mixing topics.
Refund status decision table
| Buyer message | Safer first reply | Use this adjacent guide if needed |
|---|---|---|
| “You said the refund was approved but I do not see it.” | Confirm approval date and explain processor posting timing. | Refund process |
| “My bank says there is no refund.” | Share your safe refund status and ask them not to send sensitive bank data. | Invoice or receipt request |
| “I only received part of the money.” | Compare the amount, tax, shipping, discount, fee, and prior refund record. | Partial refund |
| “I want a refund now.” | Do not use this guide until refund approval exists; start with refund request wording. | Refund request |
| “My payment failed but I was charged.” | Separate failed-payment authorization holds from approved refunds. | Payment failed |
When to use a different guide
If the refund has not been approved yet, use refund request. If the buyer asks how the refund process works, use refund process. If only part of the amount is disputed, use partial refund. If the payment did not complete or may be an authorization hold, use payment failed. If the buyer needs a document instead of a status check, use invoice or receipt request.
FAQ
How should ecommerce support reply when a refund was approved but not received?
Confirm the approval date, explain that card, wallet, bank, and marketplace processors can show refunds on different timelines, share the safe refund reference or status your system exposes, and give a clear follow-up window without asking for payment credentials.
What details are safe to ask for in a missing-refund follow-up?
Ask for the order number, refund approval message date, payment method type such as card or wallet, and a screenshot with card numbers, bank details, transaction IDs, balances, and unrelated personal information hidden. Do not ask for full card numbers, passwords, bank login screenshots, or payment-app credentials.
Should a seller promise exactly when money will appear after a refund is approved?
No. The reply can state the refund approval or processing date and the usual review path, but the final posting time is controlled by the payment processor, bank, card issuer, wallet, marketplace, or gateway. Give a support follow-up date instead of a guaranteed deposit date.
When should a refund-not-received case move to another guide?
Use refund-request wording when the refund is not approved yet, partial-refund wording when the amount is disputed, payment-failed wording when the original charge did not complete, and invoice or receipt wording when the buyer needs documentation rather than a missing-refund update.
Need adjacent wording? Compare refund process, refund request, partial refund, payment failed, invoice or receipt request, and the SellerTone guide hub before adapting any template to your store policy, payment provider, order record, refund record, marketplace rules, and customer history.