Refund Says Complete, but the Customer Has Not Received the Money—How to Trace It

A refund can be marked complete in an ecommerce dashboard while the customer still sees no credit. That does not automatically mean the refund failed. It means the store, payment processor, card network and customer’s bank are reporting different stages of the same transaction.

The safest response is not to click Refund again. First establish whether money actually left the merchant side, identify the reference that can trace it, and determine whether the customer should look for a separate credit or for the original charge to disappear.

Start with the evidence, not the status label

A store status is useful, but it is not the final proof. Open the order and record the original payment ID, refund ID, amount, currency, date, time, payment method, gateway and current refund status. Save the processor response or order-timeline entry. If support becomes necessary, this small evidence pack prevents repeated explanations and accidental duplicate work.

If the original payment succeeded but the store never created an order, use Webcurry’s payment-without-an-order diagnostic first. A refund investigation needs a confirmed source transaction.

What “complete” can—and cannot—mean

The word complete may describe only the store’s action. For example, a manual refund can update an order record without sending money through the payment gateway. WooCommerce explicitly distinguishes an automatic gateway refund from a manual refund, and changing an order to Refunded does not by itself move money.

A processor-confirmed refund is stronger evidence. Even then, the customer’s bank controls when the result appears. Some refunds post as a separate credit. Others become a reversal: the original debit disappears instead of being followed by a new incoming line. Ask the customer to check the original transaction as well as recent credits.

A safe refund-tracing workflow

1. Confirm the refund amount and destination

Match the refund to the original charge, not merely the order number. Check whether it was full or partial, whether shipping and tax were included, and whether the order used more than one tender. A split payment, gift card, store credit or buy-now-pay-later method may return value through more than one route.

Confirm the last four digits or payment-wallet route shown in the transaction record. If the customer replaced a card, the issuer will often route the refund to the replacement account, but the customer may need the bank to locate it.

2. Separate automatic refunds from manual records

Find the action that actually submitted the refund. An automatic refund should produce a gateway event, refund identifier or transaction note. A manual refund requires a separate transfer outside the store platform. If there is no processor-side refund, the dashboard label is bookkeeping—not evidence that funds moved.

This distinction also matters for Wix orders paid with manual methods or providers that must be refunded outside Wix. In WooCommerce, use the gateway refund action when supported; the manual option only records the adjustment. In Shopify, inspect the order timeline and refund details rather than relying on the order’s fulfillment or cancellation state.

3. Read the processor status

Look for pending, succeeded, failed, canceled or requires action. Pending means the request is still moving or waiting for sufficient account balance. Failed means the merchant must resolve the stated reason before trying again. A succeeded status means the processor accepted the refund, but it does not guarantee that the customer’s statement has updated yet.

Check the merchant balance too. Some platforms hold a refund when the payments balance is too negative. Also verify that the original payment is not under dispute, because an active dispute can change which refund actions are available.

4. Apply the correct waiting window

Use the payment provider’s documented timeframe and count business days, not calendar days. Wix Payments advises allowing 3–5 business days. Shopify Payments says a processed refund can take up to 10 business days depending on the bank. WooPayments and many card processors describe a typical 5–10 business-day window. These are operational ranges, not promises; the provider and customer’s bank remain the authoritative sources for that transaction.

Do not tell every customer to wait an arbitrary fixed number of days. Give the refund date, the provider’s published window, and the exact date on which you will escalate if it still has not appeared.

5. Find the trace reference

After the normal window, look for an Acquirer Reference Number (ARN), System Trace Audit Number, refund ID or similar network reference. For eligible Visa and Mastercard refunds, Shopify may expose an ARN in the order timeline. Give the customer the reference and ask their issuing bank to trace the credit. A bank agent searching only by merchant name may miss it.

If no trace reference is available, contact the payment provider with the original charge ID, refund ID, amount, currency and dates. Ask whether the refund reached the card network, was rejected, or was returned to the merchant.

6. Rule out a reversal

When a refund is issued soon after payment, the processor may reverse the original charge. In that case there is no separate credit for the customer to find. Compare the customer’s settled statement—not only a banking-app notification—and verify whether the original debit is still present.

Platform-specific checks

Wix Stores and Wix Payments

Open the order’s Payment info and verify whether the refund is pending or completed. For Wix Payments, compare the refund record under Payments with the order. If the payment used a manual method or a provider that Wix cannot refund directly, confirm that the external refund was actually issued. After the published waiting window, contact Wix or the provider with the transaction details.

If the customer never received the store’s message, treat that as a separate notification problem and follow the missing order-confirmation email workflow. An email is not proof of movement of funds.

Shopify

Review the order timeline for Pending, Failed or processed status and inspect the Shopify Payments balance. If a processed card refund is outside the expected window, locate the ARN in the refund details when available. Send that number to the customer with instructions to contact the card issuer—not the card network or the merchant’s bank.

WooCommerce and WooPayments

Check the order notes for a successful gateway refund message, then confirm the same refund in the gateway dashboard. If the merchant clicked the manual refund button, verify the separate bank or gateway transfer. For WooPayments, also inspect the transaction record and merchant balance. A WooCommerce order status alone is not sufficient proof.

What to send the customer

Use a short factual update: the refund amount and date; the destination payment method; the processor’s current status; the expected business-day window; and the next action date. Once available, include the trace reference. Avoid sending full card numbers, screenshots containing sensitive payment data, or internal fraud notes.

For example: “We issued a $75 refund to the Visa ending 1234 on 6 October. The processor confirms it succeeded. Your bank may show it as a credit or may remove the original charge. If it is not visible after the provider’s 10-business-day window, please give your bank ARN [reference] so it can trace the refund.” Replace the figures and timing with the actual record.

Do not create a second refund until you reconcile the first

Issuing another refund because the first one is not visible can produce a double payment. Before retrying, confirm that the first attempt is failed or canceled—not merely pending—and document who authorized the retry. If the processor cannot determine the outcome, escalate with the original and refund IDs before taking further action.

If checkout itself cannot expose a usable payment route, start with the no-payment-methods troubleshooting guide. For promotion-related disputes, use the coupon rejection diagnostic rather than altering the refund record.

Build a refund process that customers can trust

A reliable refund process records the payment and refund IDs, keeps provider timeframes in the support playbook, gives staff a clear escalation threshold and requires evidence before a retry. Test the workflow with a low-value order after changing payment providers, checkout apps or automation rules.

If your store’s order, payment and customer messages disagree, ask Webcurry to audit the transaction flow. The goal is not another reassuring status label—it is a refund trail that the merchant, processor, bank and customer can all reconcile.

Authoritative references

Wix Payments refund guidance explains the Wix workflow and expected bank delay.

Shopify’s refund troubleshooting guide covers pending refunds, bank timing and ARNs.

WooCommerce refund documentation distinguishes automatic gateway refunds from manual order records.

Stripe’s refund reference documents processor refund statuses including pending, succeeded, failed and canceled.