A store may say a refund was ‘issued’ at noon, yet a customer still sees no money a week later. Both statements can be true. A card refund passes through at least four actors—merchant, payment processor/acquiring bank, card network and issuing bank—and the event recorded in the merchant’s dashboard is not necessarily the event that makes funds available. The financially useful question is not just how many days to expect but which institution currently controls the next step.
The actual clock starts after the merchant acts
The advertised baseline for standard card refunds is often five to ten business days. Stripe’s published guidance says customer refunds commonly take that long to appear on a statement, with exceptions for reversals, insufficient merchant funds and bank processing [1]. That is a practical servicing range from one large processor—not a universal Visa or Mastercard promise. A merchant may first take several days to approve the customer’s return, inspect merchandise or release a deposit. The total consumer wait can therefore be longer than the card-processing window.
For a common settled-card transaction, the sequence is: customer asks for return; merchant accepts; merchant creates credit; processor validates and transmits it; acquirer and network route information to issuer; issuer applies the credit and displays it on the account. Settlement and statement presentation can also differ. The same refund may be recorded immediately in an internal system yet appear only after end-of-day files, weekends, local holidays and issuer posting rules.
For a transaction that was only authorized and not captured, the right operation may be an authorization cancellation. The pending hold disappears or the original amount is reduced; the customer may never see a separate positive ‘refund’ entry. Stripe warns that a fast cancellation can appear as a reversal and that a partial reversal may simply replace the initial transaction with a lower charge [1]. Treating the missing refund line as automatic evidence of a missing refund confuses two different accounting events.
Four payment events that customers call a refund
| Event | What the customer usually sees | Mechanism | Main investigative contact |
| Authorization reversal | Pending charge disappears; available balance recovers | Hold released before settled payment | Issuer and merchant |
| Ordinary merchant refund | New credit entry, often days after purchase | Credit routed back through card ecosystem | Merchant/processor, then issuer |
| Partial reversal or adjustment | Original charge reduced | Reduced or reversed authorized amount | Merchant/issuer |
| Dispute/chargeback | Temporary or final bank credit may appear | Contested charge under separate rules | Issuer’s dispute team |
Visa’s own consumer information draws a sharp line between a normal merchant return and unauthorized transactions: its Zero Liability Policy refers to replacement of unauthorized funds within five business days of notification, subject to conditions. That is *not* a five-day promise for a pair of shoes returned under a retailer’s policy [2]. Chargebacks are also not ordinary refunds. They involve investigation, defenses, evidence deadlines and potentially provisional credits that may later be reversed.
The US adds a useful statutory benchmark. Under Regulation Z, 12 CFR 1026.12(e), a merchant accepting a return to be reflected on a credit-card account generally must transmit the credit statement to the issuer through normal channels within seven business days. The card issuer generally must credit the account within three business days after receiving that statement, although backdating the effective credit can satisfy the rule even if the visible posting comes later [3]. These are two separate duties and their timing should not be read as one universal ten-day rule for every card or country. They apply in the relevant US credit-card context, not automatically to every debit card or foreign issuer.
Mastercard publishes transaction-processing rules governing returned merchandise and refund records, while Visa likewise publishes its Core Rules. Those network rules set obligations for members and merchants; their existence should not be conflated with one global promise about the specific number of days that money shows in a consumer app [4][5].
FIGURE 1 | Three illustrative clocks from return acceptance to card credit. Each stacked bar separates merchant delay from downstream processing; not a network SLA.
Why a refund approved on Friday can appear much later
Consider three explicitly hypothetical timelines, counting only business days. In a fast case, the merchant acts one business day after accepting the return and the payment chain needs another three business days; the customer sees a credit around day four. In a middle case, the merchant spends three business days on internal processing and the downstream chain requires seven: ten business days in total. In a slow-but-not-necessarily-broken case, a merchant waits seven business days and the processor/issuer chain takes another ten: seventeen business days from the return request, even though a processor might have met its typical window after the actual refund was issued.
These are *process illustrations*, not empirical percentiles, promises or network standards. The point is the change of origin: ‘ten business days since return’ and ‘ten business days since merchant submitted a refund’ are different dates. If a weekend intervenes, ten business days is commonly close to two calendar weeks. Holidays, cross-border card processing and card-account changes can make the wait longer.
A support agent’s phrase ‘completed on our side’ is also ambiguous. The merchant may have entered an instruction that is pending because its processor account has insufficient funds. Stripe explicitly lists pending refunds caused by merchant-balance problems [1]. A processor might validate a refund, send it for clearing and later receive a failure status. Adyen’s technical description notes that a refund accepted by its own validation can still be rejected by a card scheme subsequently [6]. ‘Completed’ should be tied to a traceable transaction event.
How to prove where the refund went
The Acquirer Reference Number (ARN) is an evidence tool, not merely jargon for customer support. Adyen says the ARN is assigned as a card transaction progresses from the acquiring to issuing bank; the issuer can use it to locate a payment or refund. Stripe similarly offers ARN tracking for Visa and Mastercard transactions and may provide a System Trace Audit Number (STAN) or Retrieval Reference Number (RRN) where appropriate [7][8].
A practical escalation starts with the merchant: ask for the exact refund date, amount, original payment identifier, status and ARN if generated. If the credit has been transmitted, ask the card issuer to trace the ARN. If the merchant cannot give an identifiable refund and its processor shows ‘pending’, repeatedly calling the issuer is unlikely to solve a merchant-side blockage. If the issuer identifies a posted credit, check the statement for a reduction of the original charge rather than assuming the money must appear as a new positive entry.
The reference is not always available immediately. Stripe says ARN visibility may take another one to three business days. For early reversals, a STAN may be the more useful identifier, while some payment methods use other references [8]. This means a customer’s ‘show me the ARN five minutes after canceling’ demand may be premature. It also means a merchant providing a screenshot with no transaction reference has not fully resolved a delayed credit complaint.
FIGURE 2 | Refund state map: why a disappeared pending authorization is not necessarily a separate credit. Analytical process diagram.
A cancelled card is usually not a lost refund
Customers often fear that replacing a compromised or expired card invalidates an old refund. Stripe’s support guidance says banks generally redirect refunds to the replacement card or related bank account, and otherwise may return funds to the processor for follow-up [9]. That is a typical path, not an ironclad guarantee: if the underlying bank account has been closed, an issuer may need additional investigation or alternative disbursement. The merchant cannot simply assume the original card number’s expiry proves the refund failed.
A second complication is the currency. If a customer purchased abroad, the issuer may convert a refund at an exchange rate different from the original purchase date and apply its own terms. Even a full merchant refund in the merchant’s currency can yield a different home-currency amount. The original foreign-transaction fee might not be reversed. In the example of a €500 purchase billed at $550 and subsequently refunded when exchange rates imply $540, a ten-dollar difference is an illustrative FX effect, not proof that the merchant short-refunded. An accurate reconciliation needs purchase currency, refund currency, scheme conversions and issuer fees.
Refunds also affect merchants economically. Stripe says standard payment processing and currency-conversion charges from an original payment generally are not returned when a merchant refunds it [10]. A consumer sees ‘100% refund’ while a small retailer still absorbs nonrecoverable acquiring costs, returns handling and lost inventory value. That explains part of the commercial friction in liberal return policies without justifying a merchant’s failure to honor applicable consumer rights.
The cost of waiting is more than inconvenience
A delayed $2,000 credit can matter to someone revolving high-interest debt. As an illustrative simple-interest estimate—not a determination of actual card interest calculations—$2,000 × 24% annual rate × 10/365 equals $13.15 in ten calendar days. A $5,000 credit at the same annual rate represents $32.88 over ten days. Actual interest depends on whether the balance was interest-bearing, grace periods, average-daily-balance rules, statement cutoffs and when the effective credit is applied. Regulation Z’s distinction between effective crediting and visible posting is therefore economically relevant [3].
A debit-card user has a different exposure: cash is unavailable for another payment, potentially triggering overdraft, borrowing or failed bill collection. A credit-card user may temporarily lose available credit without an immediate cash shortage. Neither economic burden is captured by the processor’s average refund timeline. A family waiting for an airline reimbursement faces a liquidity question; a merchant waiting for returned goods faces a verification and fraud-loss question.
FIGURE 3 | Simple-interest opportunity cost of delayed credit: $2,000 at hypothetical 24% APR, ignoring grace periods and issuer posting conventions.
Refund, dispute or fraud: choose the correct route
If the merchant agreed to refund but has not initiated it, request a dated confirmation and then use the merchant’s complaints channel. If the merchant says it has sent it, ask for the trace reference and involve the issuer. If the retailer refuses a refund allegedly required by contract or consumer law, the issuer may offer a dispute process depending on network rules, jurisdiction and the nature of the evidence. For an unauthorized transaction, notify the issuer promptly through the fraud channel rather than waiting for the merchant to issue a voluntary refund; statutory and network protections are different from returns policy [2][3].
A cardholder should preserve the order confirmation, cancellation email, item return tracking, the merchant’s stated refund date and any ARN. The most useful question is specific: ‘Was this authorization reversed, was a settled credit transmitted, or has no refund file been sent?’ Once the state is identified, the next action becomes measurable. Filing multiple overlapping disputes and refund requests without telling the merchant or bank what has happened can complicate reconciliation.
Cross-border travel deserves special care. Hotel deposits, rental-car holds and pay-at-pump authorizations may have different hold-release mechanics from purchased goods. The merchant’s cancellation may occur immediately, while the issuer’s available-balance display lags. These are not all ‘Visa refunds taking two weeks.’ In some cases there is no settled charge to refund at all. The distinction is especially important when the cardholder uses a debit account with limited free cash.
What would falsify the ‘it’s the bank’s fault’ explanation?
If the acquirer has no refund instruction or the merchant’s processor status is ‘pending’ for lack of funds, the issuing bank cannot post a credit it never received. Conversely, if a verifiable ARN shows clearing to the issuer and the issuer cannot explain the missing credit after the relevant period, the investigation should shift away from the merchant. If the original charge simply disappeared, search for an authorization reversal rather than a separate refund entry. These are falsifiable operational tests rather than guesses about which participant is slow.
The short answer remains that five to ten business days after an actual refund submission is a common operational expectation, but consumers should track the *submission date*, not the return-request date, and recognize distinct timelines for reversals, disputed or unauthorized transactions. A clear reference and the correct institution beat repeated generic calls to ‘Visa’ or ‘Mastercard.’
A refund investigation that preserves evidence
The first day after a retailer agrees to a return, preserve the correspondence that states whether the item must be inspected first. When the merchant says the refund was actually submitted, note that new date separately. Check whether the original entry is still pending or has posted, because a pending authorization is not the same as a completed card sale. Record the card’s last four digits, the billed currency and the amount; this avoids mistakenly matching the return to a later purchase from the same merchant.
After the processor’s ordinary display window, request a traceable ARN where available, and ask whether the refund was approved, settled, reversed or rejected. Send the ARN to the issuer rather than relying solely on a generic transaction screenshot. If the merchant says its refund has failed, request the failure reason and corrected disbursement plan. If a fraud dispute has already been opened, tell both the merchant and issuer before initiating a parallel refund process. The goal is to prevent double claims and a later clawback that creates another unexplained statement entry.
For cardholders who use a budgeting app, it is worth reconciling the *available balance*, the *posted balance* and the statement’s effective posting date. A hold release may change available funds before a statement does. A credit-card refund may reduce a bill even if it is not a withdrawal to a deposit account. A refund that arrives after a statement closes may alter the next billing cycle rather than immediately erase the amount shown on the old statement. These are three different financial outcomes despite a single word—refund—being used for all of them.
This approach also avoids a frequent trap in personal-finance reporting: comparing issuer service agents’ quoted timelines without establishing whether both cases began at the same transaction stage. A four-day hold release and a nine-day settled refund can both be correctly processed under their respective pathways. Counting from return shipment rather than acceptance introduces another variable. Consumers can make the timing comparison meaningful only by anchoring each case to the same documented event.
Methodology
This article uses published network policies, US Regulation Z and processor documentation reviewed as of 10 October 2026. Timeline charts are additive examples using stated hypothetical merchant and downstream processing delays; they are not empirically observed distributions. Interest illustrations use principal × annual rate × calendar days / 365 without compounding; consumer-account interest may be calculated differently. Rules and deadlines are jurisdiction-, product- and fact-specific. A processor’s published range is not a legal guarantee or a universal network requirement.
Sources and Primary Documentation
Source list checked 10 October 2026. Bracketed numbers in the article refer to entries below. Hyperlinks open the original publishers.
[1] Stripe: where is a customer refund?
[2] Visa: Zero Liability protection and unauthorized funds
[3] CFPB: Regulation Z §1026.12(e), crediting returns
[4] Mastercard: Transaction Processing Rules
[5] Visa: Visa Core Rules and Policies
[6] Adyen: preauthorizations, cancellations and refund status
[7] Adyen: where to find ARN reference
[8] Stripe: trace refunds using ARN, STAN or RRN
[9] Stripe: refunds to cancelled or expired cards
[10] Stripe: processing fees on refunded payments
[11] Stripe: how to refund a customer
[12] Stripe: refund FAQ, pending and missing credits
[13] Visa Direct: OCTs versus purchase refunds
[14] Stripe: refunds for inactive issuing cards
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574