Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Customers file a chargeback after a refund when they can’t see the money yet, when the refund was partial or failed, or when they disputed before the refund posted. Card refunds often take 5 to 10 business days to show. Check the real refund status before you do anything else.
Written by Chargeflow Experts. Updated 12 November 2026.
Most of these disputes are timing or clarity problems, not bad faith. These are the common causes:
A chargeback after a refund costs you twice if you get it wrong. You lose the refund and the disputed amount, plus fees.
Check before another payment
Choose the action that matches the status
Pending refund
Check: Has the refund finished, or is it stuck?
Next: Read the status in your provider and tell the customer exactly that.
Failed refund
Check: Why it failed, and if the money came back to you.
Next: Fix the cause and send the refund another way your provider allows.
Partial refund
Check: How much you refunded and how much is still disputed.
Next: Show the math and the reason for the partial amount.
Reversal
Check: Did the original charge drop off instead of a credit line showing?
Next: Tell the customer the charge will simply vanish from the statement.
Formal dispute open
Check: Do the refund and the chargeback cover the same money?
Next: Work through your processor. Do not send a second refund.
Pending, partial, reversed and disputed are four different states. Check the provider record before you pay anything else.
Stripe’s refund guide says customers usually see a card refund about 5 to 10 business days after you send it, depending on the bank. A failed refund can take up to 30 days to come back to your balance. Other processors and payment methods run on their own timelines.
Many customers dispute because they don’t know how long a refund takes. Share these numbers in your refund email so they don’t call the bank too early.
Merchant to card issuer
7 days
US credit cards: the merchant must send the credit within 7 business days of accepting a return (Reg Z).
Issuer to account
3 days
The card issuer must then credit the account within 3 business days (Reg Z).
Typical visibility
5–10 days
Business days until a Stripe card refund shows on the statement.
Tracing number
7 days
Business days it can take Stripe to get the ARN for a refund.
The two Reg Z limits come from 12 CFR 1026.12(e) and apply to US credit cards. Debit card refunds follow the bank’s own timing, so a debit card refund timeline can run longer.
If a customer sees “refund record pending,” the refund is sent but not yet posted. They can usually wait. If it is still pending after 10 business days, give them the ARN so their bank can trace it.
Approved, sent and received are different
Give an accurate refund update
Current status and next step
Give the original payment, the refund amount, the date you sent it, its status and the next step. Add the tracing number when you have it. Don’t say the customer has the money just because support approved it.
Partial amount and consistent message
Explain a partial refund before you close the ticket. Split out items, shipping and other amounts so the customer understands the credit. Use shared support and payments records to keep messages consistent.
A double refund chargeback happens when the customer gets your refund and then wins a chargeback for the same money. The bank has already pulled the funds back, so your refund pays them a second time. Use the rules below to avoid it.
| What happened | What it means | What to do |
|---|---|---|
| Refund completed, then a dispute opened | The customer already has the money. | Challenge the dispute with the refund ID, amount, date and ARN. This is the credit processed defense. |
| Refund still pending when the dispute opened | Stripe may fail the refund with the reason charge_for_pending_refund_disputed. | Do not refund again. Accept or challenge the dispute instead, as Stripe advises. |
| Dispute open, no refund sent | The bank has already returned the money to the customer. | Do not refund now. Either accept the dispute or fight it with evidence. |
| Partial refund, dispute for the full amount | Only part of the charge is still owed back. | Show the partial refund and contest only the remaining balance. |
| Bank debit payment (ACH, SEPA) | Stripe warns of a double refund risk with these methods. | Check for a bank dispute before you refund a bank debit. |
The refund-pending rule and the bank debit warning come from Stripe’s failed refund guide. If the network code on the notice is credit not processed, like Visa 13.6 or Mastercard 4860, your refund record is the core proof. See credit not processed disputes for a PayPal version.
Match the refund to the disputed payment. Include its amount, date, status and reference. Say if the refund came before or after the dispute, and if any balance is still contested. A refund record is strong proof, but it does not guarantee a win.
Take a sample $100 purchase with a $30 refund. Show both amounts and the $70 that remains. Do not call the payment fully refunded. See chargebacks versus refunds, partial chargebacks and the response process.
Give one person ownership of finance, support and dispute actions. Check for an existing credit before you approve another payment. Treat failed refunds and repeat contacts as process signals first, not as refund abuse.
If you sell through a marketplace, decide up front who handles disputes and refunds across multiple sellers. One refund per order, owned by one party, stops two sellers from paying the same claim. The marketplace chargeback guide covers how to split that work.
Use duplicate-transaction controls and the workflow audit checklist to stop repeat errors. Chargeback alerts can also warn you before a dispute is filed, so a pending refund and a new claim don’t collide. You can explore Chargeflow’s chargeback recovery workflow and verified Stripe integration.
Sample September 2026 case
See where the refund and dispute overlap
1 September 2026
Payment P-100 completed: USD 100.
Original purchase.
3 September
Refund R-30 initiated: USD 30; pending.
You asked for the credit. That doesn’t mean the customer has it.
4 September
Refund R-30 changed to succeeded.
Save the provider status. The statement can still lag by days.
5 September
Dispute D-100 opened: USD 100.
The claim overlaps the USD 30 refund. USD 70 is still unrefunded.
Before response
P-100, R-30, D-100, the dates, the statuses and any tracing number.
Record the partial refund. Answer the dispute before you send any more money.
USD 100 payment − USD 30 refund = USD 70 unrefunded. Keep the refund record and answer through the dispute, not with a new credit.
The IDs, dates and amounts are made up. The USD 70 is simple math. It is not a ruling on what the issuer will accept.
If R-30 failed, find out why and check if the money came back. If it is still pending, don’t call it complete. If it posted as a reversal, explain that the charge may vanish instead of a credit line appearing. If a dispute is open, settle it through the provider before any new refund.
For card refunds, Stripe’s tracing guidance lists ARN, STAN and RRN numbers where available. An update can say: “Your USD 30 refund R-30 was sent on 3 September. Status: pending. We will confirm the result and share a tracing number when we have it.” Never make up a number or promise the bank’s posting date.
A refund record marked pending means the merchant has sent the refund but it has not posted to the account yet. Card refunds often take 5 to 10 business days to show, so you can usually wait, then ask the merchant for the ARN if it is still pending.
Yes, a customer can file a chargeback after a refund, often because the refund has not shown on their statement yet. If the refund completed first, challenge the dispute with the refund ID, date and ARN instead of refunding again.
A refund request does not prove the customer received money. Check if the refund completed, failed, is still pending or posted as a reversal.
You should not refund again when a dispute appears, because the bank has already returned the money to the customer. Check the payment and dispute status and follow your processor’s process to avoid a double refund.
Proof of refund does not guarantee a win in a chargeback. Send records that tie the refund to the disputed payment and explain any partial or overlapping amounts.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Track dispute performance across multiple accounts with clear rate definitions, a reconciled case register, weighted win rates, net recovery after fees, and a fixed report schedule.
Standardize chargeback evidence with one core record set, a module for each dispute category, a fixed file format, and a check that each response was sent.
Align customer support and payments with a shared case record, complaint-to-dispute playbook, refund and dispute overlap rules, and subscription habits that cut disputes.
Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..
Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.
Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.
Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.
Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.