Library · Refunds · Calculator on this page
Refunds
A refund and a chargeback can both debit the same ticket. Type the dollars. Do not send a second credit.
Chargeback after you already refunded
GuideA refund and a chargeback are two messages. Both can debit you. Type the dollars already credited and the chargeback. We do not fill a fee.
No universal safe day after a refund. Filter the claim. Type clocks you have. We do not invent N.
| Claim | Reality | Type / read | Do not |
|---|---|---|---|
| Safe after 30 days from refund | No. Issuer windows run from the transaction (or network clock), not your CS refund date | Transaction / delivery date and any written window you have | Invent a safe day from a blog |
| Posted refund blocks all future chargebacks | No. Separate messages. Both can still post | Whether the credit posted on the card | Tell CS the case is closed forever |
| Pending refund is the same as posted | No. Pending can race a chargeback and both finish | Refund status — posted vs pending vs failed | Assume pending will net the dispute automatically |
| This map types the overlap dollars | No. Overlap cash is the refund-then-CB calculator | N/A — open that tool when both messages posted | Skip dollar recon because the refund was ‘old’ |
| Alert refunds share the same safe clock | Alert hours are a different clock. Bank dispute windows are still separate | Which door fired — alert vs bank CB | Mix alert SLAs into issuer day-count myths |
| Amazon A-to-z grant ends Visa windows | No. Amazon and bank are two doors | Whether a bank case also exists | Treat Seller Central as the card network clock |
A refund and a bank chargeback are two messages. The network does not net them. If the credit already posted and the chargeback also posts, you are out both amounts plus the fee on the statement.
Type those dollars in the calculator above. The overlap is the smaller of the two amounts. That overlap is the double debit. Ask the acquirer to reverse it. Do not send a second credit.
Posted, pending, or failed
Posted. The customer already has the money. The bank still pulled a chargeback. Send the refund proof. Chase the overlapping pull. CS should not “make them whole” again.
Pending. Stop the credit if the chargeback is already in. Letting both finish is how you pay twice.
Failed. The refund never left. Treat it as a chargeback. Fight or eat it on the usual rules.
Sparing a ratio before a chargeback is a different job. That lives on Chargebacks as refund-to-deflect. This page is after the refund already went out.
RDR is still a refund. Alert auto-refunds are still refunds. If those credits never hit the helpdesk book, you already have two books. Alert and CS both refunding one order: alert vs CS double refund. Marketplace offer refund share vs written line: marketplace refund gravity. Store credit vs refund names when CS credit is not a card reverse. Refund to save a MID spends refunds only when headroom is gone. One helpdesk ticket before a CB: refund this ticket. RMA vs keep-the-goods is the inventory move. CS labor on those tickets: helpdesk RMA cost. Macro-touched tickets that reopen: macro miss rate. Macros that attach refunds ÷ macros used: macro-refund attach rate. Macro vs non-macro CSAT: macro CSAT delta. Handle minutes vs CSAT points: CSAT vs handle time. First-reply hours vs CSAT: first reply vs CSAT. One-touch resolves ÷ tickets: one-touch resolve rate. Reopens ÷ closed tickets: ticket reopen rate. Aged tickets × AOV risk: aging cost. Channel ticket mix vs SLA breaches: channel SLA mix. Handoff hours ÷ tickets: channel handoff lag. CSAT lift vs refund fees: CSAT vs refund cost. Escalations that refund: escalation-to-refund rate. First-response hours vs refund share: first response vs refund. Repeat contacts ÷ tickets: repeat contact rate. Reason code mix: refund reason mix. Tickets past SLA: SLA breach cost. Tickets that escalate into bank CBs: escalation to chargeback. When CS refunds vs fights is the state table before those moves. Partial refund $ ÷ order $: partial refund skew. Guarantee vs chargeback language is when PDP promises feed dispute reasons.
Pair: Chargeback after you already refunded. There is no universal safe day after a refund: overlap window. Amazon A-to-z is a different door: A-to-z is not a bank chargeback. After a denial, the appeal clock: A-to-z appeal window. After a grant on FBA: what happens to fees.
Chargeback after you already refunded
CalculatorA refund and a chargeback are two messages. Both can debit you. Type the dollars already credited and the chargeback. We do not fill a fee.
Type the refund and the chargeback from this ticket. Fee can stay blank. Blank is zero. We do not fill a network fee.
The credit is on the card. The chargeback still arrived.
Type the refund and the chargeback. The overlap is the smaller of those two amounts once the refund has posted.
Policy
GuideStore credit ≠ card refund. When to fight vs RDR
CS credit vs processor refund vs bank dispute. Store credit does not stop a chargeback.
| Door | What it means | Your move | Do not |
|---|---|---|---|
| Unhappy, no alert, no CB | CS retention choice | Credit or refund by margin policy | Pretend credit protects the MID |
| CDRN / Ethoca in window | Filing path — hours | Processor refund or cancel on the card | Offer store credit instead of reversing the sale |
| Chargeback posted | Bank already took the money | Fight with a packet or accept | Stack store credit on a lost case |
| RDR already fired | Rule accepted liability | Confirm RDR credit posted; recon only | Manual refund on top without recon |
| Retrieval only | Issuer wants the draft | Return the draft; refund only if policy says | Treat as a bank CB already |
| Helpdesk credit after CB win | You already got the money back | No extra credit unless marketing chooses | Double gift the shopper |
Type alert $, CS $, and overlap orders on the matched set. We invent no overlap rate.
Type alert $, CS $, and overlap orders.
Filter the case state. Replace skeleton hours with this brand’s alert and RDR clocks. Train the table, not “be nice.”
| State | Action | Why |
|---|---|---|
| Unshipped, any reason | Refund / cancel now | No goods. Fighting is theater. |
| Shipped, fraud code, 3DS success | Fight | Liability may have shifted. Packet exists. |
| Shipped, not received, tracking delivered | Fight | Carrier scan is the packet. |
| Shipped, not as described, listing mismatch | Refund | You will lose. Save the fee. |
| Recurring, customer cancelled in CS | Cancel MIT + refund unused | Do not bill while you argue. |
| Mastercard, in RDR window, ticket under rule | Let RDR fire | You already bought that path. |
| Visa alert (CDRN) in window | Refund to stop the CB | Alert fee + refund beats CB + fee + ratio. |
| Threshold headroom < 5 CBs | Refund faster | The MID is the constraint. |
PDP “money-back” is not a network defense. Align CS with the listing. Distinct from the refund-window state table.
| Claim | Reality | Align | Do not |
|---|---|---|---|
| Money-back guarantee stops chargebacks | No. It is a shopper promise. Refused refunds still escalate | CS honor path with the PDP days | Tell finance the guarantee covers the ratio |
| Risk-free means we can refuse after delivery | No. Risk-free without a path feeds NAS | Written exceptions (opened, used) on the listing | Hide restocking fees until the dispute |
| Cancel anytime = keep billing until they call the bank | No. Cancel-anytime needs a real MIT stop | Cancel path in CS + subscription tool | Keep rebilling while arguing the promise |
| This is the personal guarantee on the MID app | No. Personal guarantee is owner liability. This page is marketing copy | N/A — open personal-guarantee for that fork | Confuse PG with money-back language |
| This map is the refund-window state table | No. Window is state → action. This map is promise vs dispute reason | N/A — open refund-window for CS states | Skip training CS because you fixed the PDP |
| Issuer gives 60 days because we said 30-day guarantee | No. Network / issuer clocks are not your ad window | This brand’s CS honor days vs network clocks separately | Invent issuer days from ad copy |
Type refund $, sales $, and your written threshold %. We invent none.
Type refund $, sales $, and threshold %.
Type tickets, macro-touched, and reopens. We invent no miss %.
Type tickets, macro-touched, and reopens.
Type refunds, CSAT delta, and fee $. We invent no CSAT %.
Type refunds, CSAT delta, and fee $.
Type breaches, hours late, and fee $. We invent no SLA %.
Type breaches, hours late, and fee $.
Type macro tickets, non-macro CSAT, and macro CSAT. We invent no delta.
Type macro tickets and both CSAT scores.
Type first-response hours, refunds, and tickets. We invent no refund %.
Type first-response hours, refunds, and tickets.
Type repeat contacts and total tickets. We invent no repeat %.
Type repeat contacts and total tickets.
Type CSAT delta, handle minutes, and wage $/hr. We invent no $/point.
Type CSAT delta, handle minutes, and wage.
Type first-reply hours and CSAT. We invent no hours/point.
Type first-reply hours and CSAT.
Type escalations and refunds on escalations. We invent no refund %.
Type escalations and refunds on escalations.
Type one-touch resolves and tickets. We invent no resolve %.
Type one-touch resolves and tickets.
Type partial refund $ and order $. We invent no skew %.
Type partial refund $ and order $.
Type reopens and closed tickets. We invent no reopen %.
Type reopens and closed tickets.
Agents
CalculatorLeakage by agent / provider
Type top-reason count and total refunds. We invent no mix %.
Type top-reason count and total refunds.
Type aged tickets, hours, and AOV/risk $. We invent no aging %.
Type aged tickets, hours, and AOV/risk $.
Type channel tickets, total tickets, and breaches. We invent no mix %.
Type channel, total, and breaches.
Type handoff hours and tickets. We invent no lag hours.
Type handoff hours and tickets.
Type macros that attach refunds and macros used. We invent no attach %.
Type macros that attach refunds and macros used.
RMA
CalculatorKeep-the-goods vs take-the-return $
Type ticket, landed COGS, return ship, restock, and honest resale. We do not fill sample dollars. Refund the customer if policy says so either way — this is the inventory move.
Type all five lines. CS refund policy is separate — refund if policy says so either way.
Type tickets, minutes, wage $/hr, and refund $. Warehouse keep-vs-return is a different page.
Type tickets, minutes, wage, and refund $.
Two books
Not on this page yetHelpdesk refunds vs processor refunds
No calculator on this section yet.
Amazon claims
GuideA-to-z is not a bank chargeback. FBA vs FBM who answers.
A denied A-to-z has Amazon’s appeal clock. Type the deadline from the notice. We do not invent a day count.
| Claim | Reality | Get from the notice | Do not |
|---|---|---|---|
| Appeal uses the same clock as a Visa chargeback | No. Appeal is Amazon’s second look. Bank cases have their own window | Appeal deadline on this claim | Paste a representment pack into Seller Central |
| I always have 30 days to appeal | No. The deadline is on this notice. We do not invent a day count | Calendar date in Seller Central or the email | Assume a blog’s day count |
| Who answers FBA vs FBM is the appeal question | No. That is the first-door map. Appeal is after a decision | N/A — use the who-answers table first if the claim is still open | Skip the first response and jump to appeal myths |
| Appealing stops a bank chargeback | No. Two doors. Amazon’s appeal does not close the issuer case | Whether a bank case also exists on this order | Ignore the chargeback because you appealed |
| I should refund again while I appeal | No. A second credit stacks on Amazon’s decision and any bank pull | Whether Amazon or you already refunded | Send money twice to ‘look cooperative’ |
| FBA means I never appeal | Amazon often owns the first answer. You still read whether an appeal path exists on this claim | Whether Seller Central shows an appeal action for this case | Assume FBA has no second look without reading the claim |
A grant can claw proceeds. Fulfillment fees often stay. Read this settlement. We do not invent a recovery percent.
| Claim | Reality | Read on settlement | Do not |
|---|---|---|---|
| All Amazon fees reverse when A-to-z is granted | Often no — fulfillment work already done may stay billed | Which fee lines credited on this claim | Invent a typical recovery percent |
| Product proceeds always stay with the seller | No. A grant commonly claws product proceeds for that order | Proceeds reversed / clawed for this order | Ignore the settlement and keep the cash in contribution |
| Who answers FBA vs FBM is the fee question | No. Who-answers is the door. Fees are after a grant | N/A — open who-answers if the claim is still open | Skip the claim response to argue fees |
| Appeal window decides fee recovery | No. Appeal is Amazon’s second look. Fee lines are settlement after a decision | N/A — different page | Paste fee myths into the appeal packet |
| A bank chargeback also means Amazon refunds fees | Two doors. Bank case does not rewrite Amazon’s fee rules | Whether a bank case also exists — do not credit twice | Assume one win clears both fee stacks |
| I can reuse last quarter’s fee recovery in CAC | No. Type this claim’s lines. Stale recovery invents margin | This settlement only | Blend old grants into landed or max CAC |
Amazon’s claim is not a bank chargeback. FBA vs FBM decides who answers. We do not invent an Amazon reason-code table.
| Situation | Who answers | Do | Do not |
|---|---|---|---|
| FBA A-to-z, no bank case | Amazon | Let Amazon work it. Watch for a later issuer filing. | Do not send a Visa packet into Seller Central |
| FBM A-to-z, no bank case | You | Answer in Seller Central on Amazon’s clock. | Do not wait for a Visa code that will not arrive |
| Amazon already refunded, then issuer CB | You / acquirer | Reverse the overlap. Treat it as a chargeback. | Do not send a second credit |
| Issuer CB only — they skipped Amazon | You / acquirer | Run the chargeback on the account that took the card. | Do not open an A-to-z as a reply |
| Paid on your merchant account | You / acquirer | The bank case sits on that MID even if the order is in Seller Central. | Do not assume Amazon owns the pull |
Optimisation
CalculatorRefund-to-save-MID vs keep-and-fight
Type primary CBs, approved sales, this MID’s written threshold %, open dispute $, and avg ticket. We do not fill 0.90. Refund before the CB posts — not after.
Type CBs, sales, threshold, open dispute $, and avg ticket. Refund is a tool, not a habit.
One CS ticket. Type ticket $, CB fee, and this MID’s counts. We invent no threshold.
Type ticket, CB fee, primary CBs, approved sales, and written threshold.
On Refunds: Reverse the overlapping debit. Do not refund twice. Saving a threshold is a different job.