A chargeback happens when a customer disputes a transaction directly with their bank or card issuer, and the funds are forcibly returned to the customer. Unlike a refund, which the merchant agrees to, a chargeback is initiated by the financial institution against the merchant.
Chargebacks generally fall into three categories. Third-party fraud happens when someone uses a stolen card or stolen identity to make a purchase. First-party fraud, sometimes called friendly fraud, happens when a customer disputes a purchase they actually made, whether by mistake, buyer's remorse, or intentional misuse of the dispute process. Operational errors happen when a merchant mistake, like an unclear billing descriptor or a failed cancellation, leads a dissatisfied customer to dispute the charge instead of contacting support.
Once a customer files a dispute with their bank, the merchant usually has a chance to accept or contest it through their payment gateway. If the dispute ends in the customer's favor, the transaction is reversed and the merchant loses both the payment and, often, an added dispute fee.
Why it matters
Chargebacks cost more than the disputed transaction itself. A subscription business also loses the product or service it already delivered, may owe a dispute fee to its gateway or acquiring bank, and risks account-level consequences if disputes become too frequent. Card networks and merchant banks track chargeback ratios, and a business that stays above the acceptable threshold for too long risks having its ability to accept card payments restricted or revoked. Visa monitors this through its Visa Acquirer Monitoring Program (VAMP), which as of 2025 treats a merchant as excessive at 150 basis points, or 1.5%. Mastercard's Excessive Chargeback Program (ECP) applies when a merchant reaches between 100 and 299 chargebacks and a ratio of 1.5% to 2.99% over a two-month period.
Because those consequences grow with volume, keeping the chargeback lifecycle organized matters as much as winning any single dispute. When a business ties each refund invoice and subscription update to the dispute that caused it, its billing records stay accurate and it can watch its ratio before it drifts toward a network threshold.
How to handle chargebacks
A subscription business generally handles chargebacks through a few connected steps:
Watch for chargeback notifications from your payment gateway as they arrive.
Decide, case by case or through a set policy, whether to accept or contest each dispute.
Reconcile the outcome by issuing a refund invoice, adjusting billing records, and updating the customer's subscription status.
Track chargeback trends over time so you can catch a spike early, whether it comes from fraud, a confusing billing descriptor, or a support gap.
Recurly handles this reconciliation directly. It creates the invoice for the chargeback and cancels subscriptions that meet service-related or fraud-related chargeback codes.
Benefits and examples
Reducing chargebacks starts with reducing the confusion and friction that lead to disputes in the first place. A subscription business that uses a clear, recognizable statement descriptor, one that names its business and product, gives customers an easy way to place a charge before they think to dispute it. A business that makes cancellation and support easy to find cuts the operational-error category of chargebacks, since customers who can solve a problem directly have less reason to go to their bank first.
Recurly automates much of the chargeback lifecycle for card transactions. When a customer disputes a charge, the gateway eventually sends Recurly a Chargeback Completed or Lost event once the dispute reaches a final state. Recurly then creates a refund invoice and a matching chargeback transaction on the account, and where the gateway supports it, expires the subscription for fraud or service-related chargebacks. Recurly does not process chargeback reversals.
For credit cards and direct debit payment methods, Recurly gives merchants a choice between two chargeback handling modes. The default mode automates the full process, creating a refund transaction and updating the invoice on its own. The manual mode sends a webhook notification only and leaves invoice adjustments and downstream handling to the merchant's own systems, which suits businesses that manage disputes through an outside financial or CRM system.
Recurly also integrates with Justt. AI, a partner that builds evidence-backed dispute responses from a merchant's own subscription data, such as billing history and usage patterns, to contest chargebacks automatically.
Frequently asked questions
What's the difference between a chargeback and a refund? A refund is something the merchant agrees to and initiates. A chargeback is initiated by the customer's bank or card issuer, forcibly reversing the transaction, and the merchant may or may not have a chance to contest it depending on the dispute's status.
Can a subscription business prevent all chargebacks? No. Some chargebacks come from stolen-card fraud that has nothing to do with the merchant's practices. But a business can reduce the ones caused by confusion or friction, such as unclear billing descriptors or hard-to-find cancellation options, which tend to be the more controllable category.
What happens to a subscription after a chargeback? It depends on the payment method and the merchant's configuration. For card payments, Recurly can automatically expire the subscription when the gateway reports a fraud or service-related chargeback. For direct debit, the merchant chooses whether Recurly automates that step or handles it manually.
Do chargebacks affect a merchant's ability to keep accepting card payments? Yes, if they happen often enough. Card networks and merchant banks monitor chargeback ratios, and sustained high ratios can lead to more scrutiny or restrictions. Visa's VAMP treats a merchant as excessive at a 1.5% ratio (150 basis points), and Mastercard's ECP applies at a 1.5% to 2.99% ratio paired with 100 to 299 chargebacks over a two-month period.
