A customer gets their money back. The refund clears, the client sees the credit, and the event closes in every system that reports on it.
The fee side does not close. The sale was priced when it was made. The refund is priced again when it is made. Both prices come from an agreement, and neither is checked against it.
Ask what a refund costs and the honest answer is that most payment businesses do not know, because the two halves of the event are never joined.
TL;DR
- At the card network a refund is a separate transaction. It does not reverse the original sale.
- Visa states that a return needs no reference to the original authorisation or clearing record. Nothing joins the two events for you.
- Refunds carry their own published interchange schedule. The Visa USA credit voucher rate is 2.05% for card-absent consumer credit and 0.00% on debit.
- The network schedule is not what you pay. Visa says merchants pay a merchant discount to their financial institution, so the cost of a refund is a contract question.
- A refund that never arrives comes back as a dispute. Dispute Condition 13.6 lets the issuer act up to 120 calendar days from the credit receipt, and up to 540 from the original transaction.
- Refund and dispute lines are the hardest fees on a provider invoice to verify, because the charge cannot be traced to the sale that caused it until you rebuild the link yourself.
Short answer
A refund and a chargeback are separately priced events that carry their own fees, and those fees are not reversals of the fees on the original sale. Visa publishes a credit voucher interchange schedule for returns, and it publishes dispute conditions and time limits for chargebacks, but neither document sets what a payment business actually pays. Visa states plainly that merchants do not pay interchange reimbursement fees, they pay a merchant discount to their financial institution. So the cost of every refund and every dispute is a term of your provider agreement, applied by a settlement engine, and reported on an invoice produced by the party receiving the money. The structural problem is traceability. Visa's own rules require no reference from a return to the original authorisation or clearing record, which means the fee event and the sale it belongs to arrive unlinked. Until they are joined, the charge cannot be recomputed from the contract, and an unverifiable charge is one you pay by default.
What happens to the fee when you refund a transaction?
Two things happen, and the second one surprises people.
The money goes back to the cardholder. That part is visible everywhere, and it is the part your client asks about.
Then the return itself is processed as a transaction in its own right. The Visa guidance to merchants on purchase return authorisation is explicit: "Merchandise return transactions are SEPARATE transaction from the original purchase request. No reference to the original authorization or clearing record is required in the purchase return authorization request." The wording is Visa's, in a bulletin dated 15 January 2019 that also set the mandate: from October 2018, US merchants with at least $10M USD in annual purchase return volume were required to authorise every return, and every other merchant from April 2019.
Read that requirement again from a finance seat. The network asks for an authorisation on the return. It does not ask for the identity of the sale being returned.
So the event that reduces your revenue and the event that priced your revenue are two records with nothing in the message joining them.
Refunds have their own price list
Returns are not free at the network layer, and they are not priced like the sale.
The Visa USA Interchange Reimbursement Fees schedule, with rates effective 18 April 2026, carries a Credit Voucher transaction type with its own table. Card-absent consumer credit sits at 2.05%. Non-passenger transport consumer credit is 1.76%, and the corporate and business card equivalent is 2.35%. Credit Voucher on debit is 0.00%. On international transactions, the schedule lists Credit Voucher at 1.00% for consumer products and 1.80% for commercial products, with a footnote stating the interchange is payable from issuer to acquirer.
Different rates, a different direction of travel, and a separate schedule from the one that priced the sale. A refund is a second priced event. It does not cancel the first one.
The schedule is not your cost
Here is the sentence in that document that decides how this has to be verified. Visa writes: "Merchants do not pay interchange reimbursement fees; merchants pay 'merchant discount' to their financial institution."
Interchange moves between financial institutions. What reaches you is whatever your agreement says reaches you, which may pass the credit voucher rate through, may absorb it, may add a fixed handling fee on top, and may do something different again for a dispute. The published schedule tells you the event has a price. Only your provider contract tells you yours.
That is why a refund line on an invoice cannot be checked against a public rate card. It has to be checked against the agreement that governs your account, on the date the return was processed.
Why is a refund not a reversal?
Because every property that makes a charge verifiable is different on the two events.
| The original sale | The refund | The dispute | |
|---|---|---|---|
| Priced by | Your provider agreement, on the sale date | Your provider agreement, on the return date | Your provider agreement, plus network dispute rules |
| Direction of money | In | Out | Out, then possibly back |
| Linked to the other event | Not applicable | No network reference required | Reason code references the sale |
| Who produces the record | The party being paid | The party being paid | The party being paid |
| Appears in | The period of the sale | The period of the return | The period of the dispute, months later |
| What you can check it against | Contracted price for that transaction | Contracted treatment of returns | Contracted dispute handling terms |
The bottom two rows are where the money hides. A sale in March and its refund in June land in different invoices, priced under whichever amendment was in force at the time, and the second one arrives with no pointer back to the first.
A discrepancy you cannot attribute is a discrepancy you cannot recover.
What does a chargeback actually cost?
Three things, and only the first is obvious.
The disputed amount leaves your balance. That is the number everyone quotes.
Then there is the handling cost your provider applies for the dispute itself. The Visa rules define dispute conditions, evidence requirements and time limits in detail. They do not set that fee. A search of the Visa USA interchange schedule returns no fee program for disputes or chargebacks at all, because it is not a network rate. It is a line in your agreement, and whether any part of it returns when you win is a term in that same agreement rather than a rule of the network.
Then there is the work. Assembling evidence, meeting a response deadline, and carrying the amount as uncollected while the case runs. Bluefyn covers the operational side of that in the dispute workflow for fintech teams.
For a payment business the arithmetic runs twice, because a dispute on a transaction you processed for a client is a cost on your provider side and a question on your client side. Whether that fee is yours to absorb or yours to bill is a contract question in both directions. Getting it wrong in the second direction produces a client invoice you cannot defend.
The refund you did not process comes back as a dispute
There is a specific dispute condition for this, and its clock is worth knowing precisely.
The Visa Core Rules and Visa Product and Service Rules, edition 18 April 2026, set out Dispute Condition 13.6, Credit Not Processed. The issuer must wait 15 calendar days from the date on the Credit Transaction Receipt before raising it, unless that receipt is undated. The dispute must then be processed no later than 120 calendar days from the date on that receipt. A footnote caps the whole thing at 540 calendar days from the transaction processing date. For disputes processed on or after 18 April 2026, an issuer raising one beyond 120 days from the transaction has to supply an explanation of why the credit was requested late.
Two things follow for a finance team.
The exposure on a promised-but-unprocessed refund runs far longer than a normal dispute window, because the clock starts at the credit receipt rather than the sale. And a refund that failed silently, which the same Visa bulletin notes happens when the original account is no longer valid, converts into a disputed transaction with its own fee attached.
The failed refund is the cheapest of these events to catch and the most expensive to miss. It arrives back as a dispute with a deadline.
Why are these the hardest fees on a provider invoice to verify?
Four properties, and they compound.
No reference to the original event. The network requires none, so the link has to be reconstructed from your own data rather than read from the settlement file.
A different pricing basis. The return is priced on its own schedule, so an expected versus actual check that applies the sale's contracted rate to a refund produces a variance that is an artefact of the method.
A different period. The refund lands in a later invoice than the sale, often under a later amendment, so version resolution matters.
A low unit value and a high count. These are small charges, repeated. That is the population sampling is worst at, which is why the discrepancy classes Bluefyn catalogues, including duplicate fees and timing violations, surface only on a full-population check.
Put together, refund and dispute lines are exactly the shape of charge that a monthly review accepts without comment. They also sit in the middle of what causes revenue leakage in payment operations, rather than at the edge of it.
How do you verify refund and chargeback fees?
You rebuild the link the network does not provide, then price both events from the contract.
- Join the reversal to its origin. Every refund, credit and dispute has to trace back to the transaction that caused it, through your own event data. This is what a canonical event ledger exists for, and it is the step that makes everything after it possible.
- Reconstruct the contracted treatment of reversals. Pull the clauses that govern returns, disputes and any handling fee, including every amendment and effective date. Contracts price conditions rather than transactions, so the clauses have to become executable logic before they can check anything.
- Compute the expected amount for the reversal event itself. Not the sale's rate applied backwards. The refund's own contracted treatment, on the date the refund was processed.
- Compare against the settlement record. Per event, across the whole population rather than a sample.
- Trace every difference to a clause and a transaction. A variance with a source is evidence. A variance without one is an opinion, and opinions do not get credited.
- Watch the failed ones. A refund that was authorised and never landed is a future dispute with a fee attached, and the window on it is measured in hundreds of days.
The calculation stays arithmetic. The core verification logic is deterministic and fully auditable, because a number that cannot be reproduced cannot be defended to a provider or an auditor. Agents assist with workflows and decisions, not core calculations. Humans remain the system of judgment.
Bluefyn never moves, holds, or custodies funds. It analyses transaction and provider data, reconstructs contract pricing, and identifies money lost to incorrect fees, pricing errors, or hidden spreads.
The bottom line
The industry treats a refund as an undoing. The card network does not. It treats the return as a transaction, prices it on a separate schedule, and asks for no reference to the sale it reverses. A dispute goes further and adds a handling fee that no public schedule contains, because it lives in your agreement.
Every one of those events is a priced instruction executed by a system that never read your contract, and reported by the party receiving the money. That is the same exposure as any other provider charge. It is simply harder to see, because the sale it belongs to was verified in a different month.
Money going out is priced as deliberately as money coming in. Only one direction usually gets checked.
Frequently asked questions
Do you get processing fees back when you refund a transaction?
Not automatically, and not as a rule of the card network. The Visa schedule prices a return as its own transaction type rather than as a reversal of the original, and Visa states that merchants pay a merchant discount to their financial institution rather than interchange itself. So whether any part of the original fee comes back, and whether the refund carries a fee of its own, is set by your provider agreement. The only reliable answer is the one in your contract, checked against what the invoice actually charged.
Is a refund the same as a chargeback?
No. A refund is initiated by you and processed as a credit to the cardholder. A chargeback is initiated by the cardholder's bank, pulls the disputed amount from you, and runs through the card network's dispute rules with evidence requirements and deadlines. They also fail differently. A refund that never reaches the cardholder can itself become a chargeback under Dispute Condition 13.6, Credit Not Processed.
Do you get the chargeback fee back if you win the dispute?
That depends on your agreement rather than on the network. The Visa rules govern who decides a dispute and by when. They do not set what your provider charges you to handle one, and the Visa USA interchange schedule contains no dispute or chargeback fee program at all. Read the dispute clause in your contract, then check whether the invoice behaves the way the clause says it should.
How long can a cardholder dispute a refund that was never processed?
Under Dispute Condition 13.6, the issuer must wait 15 calendar days from the date on the Credit Transaction Receipt, then has until 120 calendar days from that receipt date to process the dispute, capped at 540 calendar days from the original transaction processing date. Because the clock runs from the credit rather than the sale, a promised refund that silently failed stays open far longer than a standard dispute window.
Why is it hard to match a refund to the original sale?
Because nothing in the payment message requires it. The Visa purchase return guidance states that return transactions are separate transactions and that no reference to the original authorisation or clearing record is required. The link therefore has to be rebuilt from your own transaction data. Without it, a refund fee cannot be attributed to the revenue it reduced, and an unattributable charge cannot be checked against the contract that priced it.
Can refund and chargeback fees be verified across every transaction?
Yes, and the whole population is the only sample worth running. These charges are individually small and structurally repeated, which is the pattern a periodic review is least likely to notice. The requirement is a system that joins each reversal to its origin, resolves the contract version in force on the date of the reversal, computes the expected amount from the clause rather than from the sale, and outputs a variance traceable to both.
