What it means
A customer returns a jacket and the store approves a refund on Monday, the store submits the payment reversal on Wednesday, and the bank posts it the following week; these are three different points on the refund journey. Shopify distinguishes refund initiation from the time funds appear with a customer's bank, and Adyen documents refund requests and outcomes.
These are provider-specific processes and do not set a universal legal refund deadline. Define the first and finish events, because the customer request, receipt of goods and approval may each start a different clock, and merchant approval, processor acceptance and customer receipt each end one differently.
Label the measure clearly and do not claim the business controls the entire bank posting interval. Measure stages, such as request-to-decision, decision-to-initiation and initiation-to-confirmed settlement, to identify where a delay sits.
Use consistent units: calendar days show customer elapsed time, while business days may reflect payment processing. Track eligibility, since a return may require inspection under the stated policy, and do not start an approval clock at a hidden date without explaining it.
Identify an owner at each handoff, as customer service may review the case, operations verify goods and finance submit the refund. Check the original payment method, because processors often route refunds back to it subject to their rules, and do not promise an alternative rail that may be unsupported.
Avoid double refunds by reconciling the transaction identifier before retrying, since repeated customer queries during settlement can cause a second payment. Monitor pending statuses too, because a submitted request may remain pending or fail, and marking a case complete at initiation can hide failed transfers.
Communicate accurately with the customer, stating the approval, initiation date and any provider estimate without presenting an estimate as a guaranteed arrival. Handle partial refunds by linking the cycle record to the actual approved amount, record factual reason codes for exceptions such as fraud review or payment method expiry, use transaction references rather than card details, and measure business-to-business credit memos separately because a credit memo can reduce an invoice without cash being returned.
Consumer refund requirements vary by market and circumstances, so check local rules before choosing a service target. Segment cases, since instant cancellations, physical returns and complex disputes have different legitimate steps and one average can hide preventable delays; report tail cases, because a healthy median can coexist with a few customers waiting much longer.
Check the denominator by including approved refunds awaiting initiation and unresolved requests, support the timeline with return receipt, inspection outcome, approval and processor reference, and avoid backdated closure by creating a separate settlement status if finance closes at initiation. For owners, refund cycle time is useful when it separates controllable decisions from external settlement and keeps failed cases visible, and recurring causes such as a repeatedly failing payment method call for a configuration fix rather than more generic reminders.
In practice
Real-world examples.
Example
A refund request waits two days for condition review because the returned goods have not yet been inspected. The case shows a clear waiting reason and an owner in the warehouse. The measure therefore points to inspection capacity, not to the finance team.
Example
A processor accepts the refund on Thursday, but the bank has not posted it by the following Monday. The support agent tells the customer the initiation date, the refund reference and the provider's typical processing range, without promising an exact arrival date. The case stays open until settlement is confirmed.
Example
A failed refund remains open for investigation rather than closing at initiation. The finance team finds that the original card had been replaced and follows its approved exception process. The customer is paid, and the failure is recorded as a cause for later review.
Formula
Calculation
Merchant-controlled cycle = Initiation date - Approved request date
Total cycle = Confirmed settlement date - Request date
Worked example. A customer requests a refund on a Monday (day 0). The store approves it on Tuesday (day 1), initiates the payment on Thursday (day 3), and the bank confirms settlement the following Wednesday (day 9).
- Request to decision = 1 day.
- Decision to initiation = 3 - 1 = 2 days.
- Initiation to confirmed settlement = 9 - 3 = 6 days.
- Total cycle = 1 + 2 + 6 = 9 calendar days.
- Merchant-controlled share = (1 + 2) / 9 x 100 = 33.3%, so two-thirds of the elapsed time sits with the processor and bank and should not be blamed on the support team.Case study
Seen in the real world.
This entirely fictional example follows Willow Shop. Its support system marked refunds done when an employee clicked submit, even though some processor requests failed. The team separated submitted, accepted and settled states and reconciled references. When the new states went live, the team found that about one in twenty refunds marked as done were actually still pending or had failed.
Customers had been waiting and writing in again, which created duplicate work and a risk of second payments. With the three states in place, the team could see that its own review and submission took about three days on average, while the remaining time depended on the processor and banks. It then focused on the part it could control. The case does not promise any bank settlement time.
Watch out
Common mistakes.
- Equating refund submission with money received.
- Retrying without checking for an existing transaction.
- Excluding failed or unresolved refunds from the queue.
Questions
People also ask.
When does the clock start?
At a documented request or approval event, as defined for the metric.
When does it stop?
At the stated finish, such as initiation or confirmed settlement.
Who controls the delay?
The merchant controls its review and submission; processors and banks affect later stages.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%