When a store says your refund was “initiated” (or “processed”) but you haven’t received it, it usually means the merchant has sent the refund instruction into the payment system, but the credit hasn’t finished moving through bank posting yet. In other words: it’s often in transit, not missing.
This page is the hub for the most common reasons refunds feel stuck, and the fastest checks that usually clarify what’s going on.
First, match the situation to what you’re seeing
Instead of guessing, anchor to one of these patterns:
A) The charge is still pending
Sometimes there’s no “refund” because the payment never fully posted. What you’ll see is the pending charge disappearing (an authorization reversal), not a separate credit line.
B) The charge posted, and the refund is a separate credit
This is the classic refund flow. The credit exists, but it can take time to show up depending on the bank.
C) The refund can’t land where it was sent
This is when the refund was sent correctly, but the destination can’t accept it (like a closed account, or certain prepaid products).
Most people are in A or B. C is less common, but it’s the one that changes what you need to do.
What “initiated” actually signals (plain English)
“Initiated” usually means the merchant’s system has created and submitted the refund through their payment processor.
It does not always mean:
- the issuing bank has already posted it to your account, or
- you’ll see it immediately in online banking.
Think of it like a shipped package: the sender has handed it off, but it hasn’t been scanned in at every checkpoint yet.
The three most common reasons you don’t see it yet
1) Bank posting lag (most common)
Even after the merchant pushes the refund, banks often post credits on their own schedule. Some apps also hide credits behind filters or separate tabs.
This is especially common when the store refunds to a card that looks “inactive” to you (expired/replaced), even though the bank can still map it. If your card expired, the refund often still posts to the same underlying account, it just may not appear where you’re looking.
2) You’re expecting a “refund line,” but it’s actually a reversal
If the original purchase is still pending, the cleaner outcome is usually cancellation of the authorization. That looks like:
- pending charge disappears, and
- no separate refund entry appears.
People often interpret that as “I never got refunded,” when it’s actually the system avoiding a duplicate entry.
3) The destination can’t accept the credit
This is the scenario that creates the longest confusion loop: merchant says “done,” bank shows nothing.
Most commonly it happens when:
- the underlying account is closed, and the issuer rejects the credit because there’s nowhere to post it
- the payment method was prepaid/temporary/virtual and credits are handled differently
If this is happening, the refund may eventually bounce back to the merchant and they may need to re-issue it.
A fast troubleshooting path that avoids back-and-forth
Step 1: Decide whether the original charge is pending or posted
- If it’s pending, watch for it to drop off (reversal/void behavior).
- If it’s posted, you’re looking for a separate credit.
This one distinction eliminates a lot of wasted support conversations.
Step 2: Check the right “place” in your banking view
People miss refunds because they’re checking the wrong screen:
- Look at account activity, not just the newest card controls page.
- Look for credits, not only for “refund” labels.
- Check the full date range (some banks post credits with slightly different effective dates).
If you recently got a replacement card, a new card number usually doesn’t prevent the refund from arriving, but it can change where it displays in the app.
Step 3: Ask the bank to search for an incoming credit (the productive question)
Instead of asking, “Where’s my refund?”, ask:
“Can you check for a credit from [merchant] for [amount] around [date], and tell me if it’s pending, posted, or rejected?”
This prompts a trace-style search rather than a generic explanation.
Step 4: If the bank can’t see it, get a trace/reference number from the merchant
If the merchant can provide a processor reference (often described as a trace/reference number), it gives your bank something specific to locate in their system.
This is the step that typically resolves the “merchant says completed” vs “bank says nothing” stalemate.
What this usually does not mean
- It doesn’t automatically mean the merchant lied.
- It doesn’t automatically mean your refund is lost forever.
- It doesn’t automatically mean you should jump to a dispute.
Most “initiated but not received” cases are timing, posting, or visibility problems, until you confirm the destination can’t accept it.
Common wording variations you may see
- “Refund processed”
- “Refund completed”
- “Refund issued”
- “Refund pending”
- “Credit in progress”
- “Allow X business days to post”
Quick summary
- “Initiated” usually means the merchant sent the refund instruction, not that your bank has posted it.
- If the original charge is pending, you may see a reversal (disappearing charge) rather than a refund line.
- If the charge posted, the refund is typically a separate credit that can take time to appear.
- Missing refunds are most often posting/visibility delays unless the destination can’t accept the credit.
- Closed accounts and some prepaid/virtual products are the most common “can’t accept it” cases.
- The fastest path is: pending vs posted → bank credit search → merchant reference if needed.
Conclusion
A refund that’s “initiated but not received” usually isn’t a dead end, it’s a timing and tracing problem. Once you determine whether the original charge is pending or posted, and whether the destination account can accept a credit, the next steps become straightforward: let posting catch up, have the bank search for the credit, and if needed use a merchant reference to track it through the system.