A customer saying “the card is closed” does not tell you whether the refund is pending, processed or failed. Check the payment provider first. Trace a processed refund with the customer’s bank, and offer another resolution only after the original route is confirmed failed or rejected. This prevents vague updates and duplicate refunds.
Check the refund state before the card
Start with the original order and refund event, not a new payment. Confirm the amount, currency, initiation date, masked original method and current provider status. Keep the provider transaction reference with the record.
- 1Original eventKeep amount, date and masked method.
- 2Provider stateUse pending, processed or failed.
- 3Trace referenceAdd the ARN when available.
- 4Bank outcomeRecord only what the bank confirms.
- 5ResolutionPay differently only after confirmed failure.
The current Stripe refund guide is one provider example. Stripe sends a refund only to the original payment method. Customers typically see the credit in about five to ten business days, depending on the bank, while a closed method may eventually return as failed. Those are Stripe details, not universal promises. Follow the provider that processed the order.
The wider return status workflow ends at “refund issued.” This case begins there. A processed refund and a failed refund require different next actions even when the customer describes both as missing.
Keep one refund record
Use one case record for the conversation and payment evidence. Do not create a second refund merely to make the queue look resolved.
| Provider state | Evidence to keep | Honest customer update | Next action |
|---|---|---|---|
| Pending | Refund date, amount and provider status | The provider is still processing the original refund | Recheck at the provider’s stated time |
| Processed | Completion date and ARN when available | The refund left the merchant route and now needs bank tracing | Give the reference and ask the customer to contact the bank |
| Failed or rejected | Provider error or bank rejection | The original refund did not complete | Use the approved alternative-resolution process |
| Resolved elsewhere | Proof of the manual resolution | The alternative was recorded against the order | Verify receipt and close once |
A dispute about the invoice belongs in the invoice dispute process. A request before dispatch belongs in the order cancellation workflow. Keep those tasks separate from refund tracing.
Trace a processed refund
When the provider says processed, do not call it failed because the customer cannot see the funds. Check whether an Acquirer Reference Number is available. An ARN can help the customer’s bank trace an eligible card refund; availability depends on the method and provider.

Share only the reference and minimum transaction facts. Never ask for a full card number, security code, password or one-time code in chat. Ask the customer to contact the bank through its official channel and report what it confirms.
Set a dated checkpoint: “The refund is recorded as processed on 3 November. Please ask your bank to trace it with this reference. We will check again on 6 November.” Do not promise rerouting or a cheque. The bank controls that outcome.
Wait for confirmed failure before another payment
A closed card can lead to a bank rejection, but it does not prove that rejection has happened. If the provider still shows processed, a manual transfer, store credit or second refund can create duplicate value if the first refund later reaches the customer.
Move to an alternative only when the original route is recorded as unable to complete. Follow the refund policy and local rules. Record any store credit, gift card or approved manual method against the original order, including who authorised it.
Do not leave an external payment outside the order history. A configured Shopify order context integration can attach supported order activity to customer context, while commerce and payment systems remain authoritative. Bank outcomes do not all arrive automatically.
Give the case one owner and checkpoint
Use the customer support case note guide to record the original refund, provider state, masked method, ARN if available, bank outcome, checkpoint and owner. Exclude card credentials and unnecessary personal data.
A configured shared support inbox can keep the message, owner and private coordination together. It does not decide whether the bank accepted a refund. Close only after the recorded resolution is verified.
Frequently asked questions
Should we refund to a different card immediately
No. Verify whether the original refund is pending, processed or failed. A different payment before confirmed failure can duplicate the refund. Use another method only after the original route cannot complete.
What should we send the customer when the refund is processed
Send the processed date, amount, masked original method, provider status and ARN when one is available. Ask the customer to contact the bank through an official channel, then give a specific time for your next check.
When can the support case close
Close it after the original refund is confirmed received or an authorised alternative is recorded and verified. A sent message, a bank-contact request or a manually changed queue status is not proof that the money reached the customer.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy



