Refunds and chargebacks should sit in one queue, on one customer record, handled by people who can see both. The refund history is the evidence a dispute needs, and the dispute deadline, usually 7 to 21 days, is short enough that splitting the work puts the evidence with one person and the deadline with another.
Why does splitting refunds and chargebacks cost you?
Splitting them separates the evidence from the deadline. In many small merchants the person who issues refunds and the person who answers disputes never see each other's work.
Support has the customer thread and the refund button. Finance or the owner gets a processor email about a chargeback and usually has 7 to 21 days to respond, the range both Stripe and Shopify give.
A dispute needs the refund history as evidence. When a customer disputes a $100 order after receiving $60 back, Stripe's guidance is to respond anyway and show the amount and date of the refund. If the dispute lands with someone who cannot open the support thread, the response goes out without the one document that shows the merchant was fair.
Which deadlines does support control?
Support controls several clocks that finance never sees. The first is the refund window itself, which closes the moment a dispute opens: Stripe says you cannot refund outside the dispute process once one is open.
Before then, Stripe says about 40% of Visa and Mastercard early fraud warnings become fraud disputes if the charge is not refunded. The fraud report is removed only if the refund is processed as a reversal, usually within about 2 hours of capture. A warning arrives in a finance mailbox, and in a split team the decision to refund it waits for a forward.
Pay-later providers add clocks of their own. Klarna's merchant documents say that choosing "adjust statement" commits the merchant to a refund, and Klarna charges back automatically if the refund is not issued within 96 hours. A support agent who clicks that option and then waits for the warehouse is building a chargeback with a four-day fuse.
Regulation Z, the federal credit card rule, adds a legal clock on the refund side. After a merchant accepts a return, it has 7 business days to send the credit statement to the issuer, and the issuer credits the cardholder within 3 business days of receiving it. A support lead who knows every clock can decide a refund and a dispute response in the same sitting.
How do you set up one queue?
One queue needs very little software. A shared inbox or help desk where refunds and dispute notices both arrive, keyed on the order number, lets one search show the original purchase, the delivery scan, the refund, the customer's messages and the dispute together.
Each dispute notice then needs one owner on the day it arrives. Type the deadline into the ticket from the processor's date, never your own calculation; the seven-day clock article explains why a processor deadline can be sooner than the network one. Stripe also says issuers usually take 60 to 75 days to decide, and Shopify says review takes up to 75 days, so keep tickets open until the outcome arrives.
For a team with no software budget, a spreadsheet keyed on order number that lists refund date, dispute date and deadline does the same job. Review the open list every morning.
Who should be allowed to refund or accept?
Agents should be able to see disputes without being able to accept them, since accepting a dispute is a decision about money. A reasonable arrangement lets any agent refund an order under a set amount.
Larger refunds, and any case with an early fraud warning attached, then need a second person. Keep the rule in writing, so a new hire on a December shift does not guess.
Takeaway: what to do this week
- Route refunds and dispute notices to one inbox. Key everything on the order number so one search shows the whole history.
- Give every dispute an owner on day one. Copy the processor's deadline into the ticket the day the notice arrives.
- Find the fast clocks. List every early fraud warning and every Klarna "adjust statement" case, and decide each one the same day.
- Write down the refund limits. Set the amount an agent can refund alone and when a second person must sign off.
Sources: Stripe Docs, "How disputes work"; Shopify Help Center, "Chargeback process"; Klarna Docs, "Merchant evidence gathering"; CFPB, Regulation Z, 12 CFR 1026.12(e); Stripe Docs, "Dispute best practices". All checked 24 October 2026.
Sources
- Stripe: merchants usually have 7-21 days to respond to a dispute; cardholders typically have 120 days to file; issuers usually take 60-75 daysStripe Docs, How disputes work (https://docs.stripe.com/disputes/how-disputes-work), checked 24 October 2026
- Shopify: merchants usually have 7-21 days to submit; issuer review takes up to 75 daysShopify Help Center, Chargeback process (https://help.shopify.com/en/manual/payments/chargebacks/chargeback-process), checked 24 October 2026
- A merchant cannot refund outside the dispute process while a dispute is openStripe Docs, How disputes work (https://docs.stripe.com/disputes/how-disputes-work), checked 24 October 2026
- About 40% of Visa and Mastercard early fraud warnings become fraud disputes if not refunded; a refund prevents the report only when processed as a reversal, usually within about 2 hours of captureStripe Docs, How disputes work (https://docs.stripe.com/disputes/how-disputes-work), checked 24 October 2026
- Klarna: choosing 'adjust statement' commits the merchant to a refund and Klarna charges back automatically if it is not issued within 96 hoursKlarna Docs, Merchant evidence gathering (https://docs.klarna.com/payments/after-payments/disputes/evidence-gathering/merchant-evidence-gathering/), checked 24 October 2026
- Reg Z: merchant has 7 business days to send the credit statement to the issuer after accepting a return; the issuer credits within 3 business days of receiving itCFPB, Regulation Z 12 CFR 1026.12(e) (https://www.consumerfinance.gov/rules-policy/regulations/1026/12/), checked 24 October 2026
- If a customer disputes the full amount after a partial refund, respond and show the amount and date of the refundStripe Docs, Dispute best practices (https://docs.stripe.com/disputes/best-practices), checked 24 October 2026