Chargeback

If a card payment went through and the goods never arrived, the only move a customer had was to contact the seller. If the seller stopped answering the phone or shut down, that was the end of it. The money had already moved, and getting it back meant suing. Nobody sues over a $23 charge, so in practice there was no route at all.

That makes cards less attractive to use. Cash at least changes hands once you've seen the goods; a card approval goes out first. For the card networks, a world where people don't trust cards is a world without much of a business.

Chargebacks exist because the card issuer takes on that trust instead. The customer talks to the issuer rather than fighting the seller, and the issuer hears both sides and decides whether to reverse the payment. Customers get somewhere to turn no matter who they bought from, and in exchange merchants get a burden of proof and an opening for abuse.

The process starts when a customer calls their card issuer or taps a dispute button in an app. Nothing reaches the merchant first — that's the sharpest difference from a refund.

There are five steps.

1. The customer files the dispute. The reason gets sorted into a category such as goods never received, I didn't authorize this, or what arrived wasn't what was described.
2. The issuer claws the money back up front. It comes out through the payment gateway, the service that relays card payments, and a per-case fee is deducted alongside it. That fee usually stays gone even if the company later wins.
3. The company submits evidence. Login records, proof the service was actually used, the timestamp on the terms agreement, email exchanges with the customer — collected and filed before a deadline that typically runs from one week to one month after notification.
4. The issuer rules. It reads both sides and decides whether the money goes to the customer or back to the company.
5. A losing side can escalate once more, but costs stack at that stage, so unless the amount is large most companies stop there.

Step 3 is the only place a company actually gets to argue. A company that wasn't already recording the IP address, device, and terms-acceptance timestamp at the moment of payment has nothing to file and simply loses.

The number to manage is the chargeback rate: disputed cases as a share of total transactions. Gateways generally treat 1 percent as the line. For a company processing 1,000 payments a month, that's 10 cases. Cross it and the fee rate goes up; stay above it and the contract gets terminated. Losing the ability to take cards is closer to an outage than a cost — revenue stops entirely.

It surfaces first in the monthly reconciliation. Revenue booked last month has to be reduced by anything clawed back this month, and for a subscription product the customer also comes out of monthly recurring revenue (MRR), the revenue that repeats every cycle. Leave the books showing money that has already left the account and the ledger drifts from the balance.

It shows up in product and support work too, because sorting disputes by reason usually reveals product problems rather than fraud. A free trial rolled into a paid plan without the customer noticing. Someone thought they had canceled and got billed anyway. The name printed on the card statement didn't match the product name, so nobody recognized the charge. Cases like these shrink with one reminder email three days before renewal, or by fixing the statement descriptor.

It comes up in contract discussions as well. When picking a gateway, teams look past the headline fee rate at what evidence has to be submitted in what format, and whether the provider automates any of it. Once volume rises, the staff time spent responding outgrows the fees.

"Three chargebacks came in last month. That's 0.4 percent, so we're still inside the line."

The team tracks the rate rather than the raw count, and the gateway contract isn't at risk yet.

"Let's not fight this one. Our evidence is thin and the odds are bad."

The time spent contesting it is worth more than the chance of winning.

"Getting ahead of it with a refund is far cheaper than a chargeback."

Refunding before the customer goes to the issuer avoids both the fee and the rate.

At Pagedeck the cases cluster about a month after a free team converts to a paid plan. Grace found two of them in a monthly reconciliation, both filed as unauthorized charges, and the login records showed both accounts had been used every day since the payment. The statement carried the legal entity name, which nobody at those companies recognized.

Grace contested both with access logs and terms-acceptance timestamps attached, and at the same time asked Theo to change the statement descriptor to the product name. One case was won, one was lost, and the fee stayed on the winning one too. After the descriptor change, disputes of that type dropped noticeably.

The most common view is that chargebacks are something difficult customers do. The picture that comes to mind is someone lying to an issuer to claw money back, which makes it an easy assumption. Open the reasons one at a time and most of them turn out to be people who didn't remember or weren't told. Pin the cause on the customer and there's nothing left to fix, so the same type arrives in the same quantity every month. Counted by reason, two or three categories usually account for most of the volume, and those categories shrink when the product or the notification changes.

The other common mistake is thinking the amount is the whole cost. Small charge, not worth fighting, let it go — that logic is easy to reach. But two things ride along with the money. The per-case fee survives a win, and the rate rises whether you win or lose. A $23 charge turns into a loss above $40 once the fee is counted, and enough of those push the rate past 1 percent, at which point the gateway raises the fee rate. From then on, every transaction costs more, including the ones nobody disputed.