Refund Before Chargeback

Refund before chargeback is a dispute-prevention practice in which a merchant refunds a card payment that a customer has questioned, or is likely to question, before the cardholder's bank turns the complaint into a formal chargeback. The customer gets their money back either way, but the merchant avoids the fees, administrative work and damage to its dispute statistics that a chargeback brings.

The approach is widely used in e-commerce, subscriptions and digital goods, where merchants face many low-value disputes that are expensive to fight. It is supported by card network tools and third-party services that warn merchants of incoming disputes, such as Ethoca alerts from Mastercard and Verifi alerts from Visa, and by fraud reports sent before any dispute is filed.

A chargeback costs a merchant more than the value of the sale. The acquirer charges a chargeback fee for each case, the merchant spends staff time assembling evidence, and the transaction counts towards its chargeback ratio. Card networks run monitoring programmes that impose fines and extra requirements on merchants whose dispute counts or ratios exceed set levels, and acquirers may hold reserves or close accounts for merchants with persistent problems.

A refund processed before the dispute is opened avoids all of these costs. The customer receives the same money, usually faster, and the merchant keeps control of the relationship. For many merchants the calculation is simple: where a transaction is small and the merchant is unlikely to win a dispute, refunding is cheaper than fighting.

Refunding before a chargeback depends on knowing that a dispute is coming. Merchants learn about it through several channels:

• Direct contact. The customer complains to the merchant first, by email, chat or phone, and asks for their money back.
• Dispute alerts. When a cardholder contacts their issuer, participating issuers can send a dispute alert to the merchant through an alert network. The merchant has a short window to refund or cancel the order, after which the issuer typically does not proceed with the chargeback.
• Fraud warnings. Issuers report confirmed fraud to the card networks, and services pass these reports to merchants as an early fraud warning. A refund at this stage can prevent a fraud chargeback.
• Automated resolution. Some network services let merchants set rules in advance so that disputes matching specified criteria, such as amount or reason, are refunded automatically before a chargeback is created.

The main operational risk is paying twice. If a merchant refunds after the issuer has already raised a chargeback, the cardholder may receive both the refund and the chargeback credit. Merchants can usually recover from this by responding to the chargeback with proof that a refund was processed, but the process takes time and still adds a dispute to their record. Good practice is therefore to check the status of a transaction before refunding and to link refunds clearly to the original payment so the issuer can match them.

Merchants also consider how a refund is processed. Voiding an unsettled authorisation, a partial refund and a full refund all have different effects on fees and on what the cardholder sees on their statement.

A refund-first policy has costs of its own. Refunding every complaint can encourage friendly fraud, where customers claim non-receipt or dissatisfaction to keep goods for free, and in some cases organised refund fraud. Merchants that sell physical goods may lose both the product and the payment. Alert services also charge per alert, so they make economic sense mainly where chargeback costs and risks are high.

For these reasons merchants combine refund-before-chargeback with fraud screening, clear descriptors so customers recognise charges, easy cancellation and customer service that resolves problems before customers turn to their bank. Many set thresholds, refunding automatically below a certain value and investigating above it, and review dispute reasons to address the underlying causes.

Refund before chargeback sits outside the formal chargeback lifecycle, which starts only when an issuer raises a first chargeback. It is part of wider dispute management, which also covers responding to chargebacks that do occur. Network rules increasingly encourage this early resolution, because disputes settled between merchant and cardholder are cheaper for every party in the system.