Retrieval requests and chargeback fees: reading the notices
Not everything your processor sends about a disputed transaction is a chargeback. A retrieval request is an issuer asking for documentation about a transaction, usually before any money moves. A chargeback is the money actually being taken back. They arrive looking similar, they carry different deadlines and different costs, and treating the first like junk mail is how it becomes the second.
The distinction is worth ten minutes because the early notice is the cheap one to answer.
What is a retrieval request actually asking for?
A copy of the transaction record — the receipt, the signature if there was one, and sometimes an invoice or delivery record. The cardholder has queried a charge and the issuer wants to see it before deciding anything.
Many retrieval requests end there. The cardholder sees the receipt, recognises the purchase, and the matter closes. That is the best possible outcome and it costs you nothing but a few minutes and a fee that is typically small.
What happens if you ignore it?
The issuer proceeds without your documentation, which materially raises the chance of a chargeback you would have won. An unanswered retrieval request is one of the few places in payments where doing nothing is actively worse than doing something badly.
This is also where a store's record-keeping pays off or does not. If you cannot find a receipt from six weeks ago in under ten minutes, the system is the problem rather than the request.
What fees attach to a chargeback?
A processing fee per chargeback, charged regardless of whether you eventually win. That is the part merchants find hardest to accept: a dispute you successfully defend still costs you the fee, and often a second fee if you choose to contest it.
The practical consequence is that prevention beats defence economically, even when defence works. Three chargebacks won can cost more in fees than one small sale was worth.
What is the ratio everyone talks about?
Chargebacks as a proportion of transactions, monitored by the card networks through their own programs. Exceeding the thresholds moves an account into a monitoring program with additional fees and remediation requirements, and sustained failure can end the relationship.
You do not need to memorise the thresholds. You need to know your own number, month by month, and to notice a trend before somebody else does.
Which notices can you still influence?
Retrieval requests, first chargebacks, and the representment that follows. Once a chargeback has gone through the later stages the room narrows considerably, and arbitration carries costs that rarely make sense for a small ticket.
That is the sequencing lesson: effort spent early is worth several times the same effort spent late. A well-documented response to a retrieval request is the cheapest defence available to a store.
What should your filing system look like?
Whatever it is, it must produce a specific transaction's record in minutes. For most small stores that means the processor's own portal, which keeps transaction detail searchable by date and amount, plus any delivery or order documentation kept in a way that can be matched to a sale.
Test it rather than assuming. Pick a transaction from two months ago and try to assemble the full record. The time that takes is your actual dispute-response capability, and it is usually worse than owners expect. Investopedia's explainer on the chargeback process is a reasonable primer for anyone on your staff who handles them.
Frequently asked questions
How long do I have to respond?
Response windows are set by the card networks and are short — days rather than weeks, and the clock runs from the notice rather than from when you read it. Diary the deadline the day the notice arrives, because there is no extension for a busy week.
Does responding to a retrieval request admit anything?
No. It supplies documentation about a transaction. Responding promptly with a clear receipt is the single most effective thing you can do at that stage, and it carries no concession of any kind.
Can I charge the customer the chargeback fee?
No. The fee is between you and your processor, and attempting to recover it from a cardholder in dispute is a bad idea both practically and under network rules.
Do refunds prevent chargebacks?
Often, if they happen before the customer gives up on you. A refund issued after a chargeback has been filed does not cancel it and can result in the customer being credited twice, which is why checking dispute status before refunding a complaint matters.
Are chargeback fees negotiable?
The per-item fee is usually fixed in your agreement, but it is a line worth comparing between providers, particularly if your category sees disputes. What is more negotiable is what happens as volume grows.
What if the same customer disputes repeatedly?
Document the pattern and raise it with your processor, and consider declining their future business. Repeat disputing by the same cardholder is a recognised pattern, and a store that can show it has a stronger position than one presenting each case in isolation.
Should I fight every chargeback?
No. Weigh the ticket against the representment fee and the time. Contesting a small disputed sale can cost more than conceding it, and the honest calculation sometimes says let it go. What should never be automatic is conceding a large one, or conceding a pattern.