How a Chargeback Actually Works

Whose rules are these, actually

A chargeback is a mechanism inside the card networks — Visa, Mastercard and the rest. It exists so that a bank which paid out on a transaction can reclaim the money from the bank that received it, under conditions the network defines.

The parties to it are your issuer (your bank) and the merchant's acquirer (their bank). You are not a party. Neither, technically, is the merchant. You ask your issuer to raise a claim; they decide whether the network's rules cover it; the two banks then argue under those rules.

This has three consequences that explain most of what feels arbitrary about the process:

• "That's not fair" isn't an argument. The question is whether your situation matches a defined reason code. A genuine grievance that fits no code goes nowhere.
• Your issuer is your only route in. You cannot file with the network directly, and the merchant cannot stop you asking.
• The rules change. Networks revise them periodically, so what was arguable two years ago may not be now.

A chargeback is not a refund

This distinction is worth being precise about, because getting it wrong costs people money and time.

Several reason codes explicitly require that you attempted to resolve it with the merchant, and a claim can be rejected for skipping that step. It isn't the bank being unhelpful; it's a condition written into the rules. Keeping the email or chat transcript from that attempt is the single most useful thing you can do at the start.

The stages, in order

The process is a sequence, and each stage has its own deadline and its own escalating cost to the parties.

That provisional credit deserves emphasis. Money reappearing in your account means the claim was accepted for processing, not that it succeeded. If the merchant represents successfully, it is debited again — sometimes weeks later, often to someone who has already spent it.

What the grounds actually are

Reason codes vary by network and change over time, but they cluster into four recognisable families:

• Fraud. You didn't authorise the transaction. This is the strongest family and generally the one with the clearest rules — it's what the whole system was built for.
• Authorisation and processing errors. Charged twice, charged the wrong amount, charged after you cancelled, currency converted incorrectly, a transaction processed without proper authorisation. These are the easiest to evidence because they're mechanical — a statement usually proves them.
• Goods or services not received. You paid, nothing arrived. Note that a delivery confirmation on the merchant's side is strong evidence against you here.
• Not as described, or defective. What arrived materially differs from what was sold. This is the most contested family, because "materially" is a judgement and the merchant's product page is evidence too.

What is generally not a ground: changing your mind, a merchant's refund policy you didn't read, a subscription you forgot to cancel where the terms were shown, or dissatisfaction that doesn't rise to "not as described". Some of those may have other remedies — they simply aren't chargeback remedies.

The clock, and where it starts

Every reason code has a time limit, and the limits are real — an out-of-time claim is rejected without being considered on its merits.

The part people miss is where the clock starts, which isn't always the transaction date:

• For a delivery that never arrived, it commonly runs from the expected delivery date, not the purchase date.
• For a service booked far ahead, it may run from the date the service should have been provided.
• For a subscription, it commonly runs from each individual charge, which is why old charges can be out of time while recent ones aren't.
• There is typically also an outer backstop measured from the transaction date, beyond which nothing can be raised.

Practical implication: for a delayed delivery, waiting indefinitely for the seller can push you past the window. The limits are published by the networks and your issuer can tell you which applies.

Why merchants fight them

Understanding the merchant's position explains why some disputes resolve instantly and others turn adversarial.

A chargeback costs the merchant more than the transaction. They lose the sale, typically pay a fee whether or not they win, and the case counts toward a chargeback ratio the networks monitor. Cross a threshold and a merchant enters a remediation programme with penalties; stay there and they can lose card acceptance entirely — an existential outcome for an online business.

Two things follow, and both are useful to you:

• Many merchants will refund immediately rather than face a chargeback, because the refund is cheaper. This is a large part of why contacting them first often works.
• Merchants defend vigorously when they have evidence, because ratio matters as much as money. A merchant with delivery confirmation and matching device data will represent, and often win.

Chargeback versus statutory protection

This is the most valuable distinction in the whole subject, and it's routinely missed.

A chargeback is a network scheme rule — a private arrangement between banks. In a number of countries there is also a statutory protection giving card users a legal claim against the card provider for certain purchases, typically credit card purchases above some threshold. Where such a law exists it is generally stronger than chargeback: it can be a legal right rather than a scheme courtesy, may cover more than the amount paid, and can have far longer time limits.

These are separate routes and can sometimes be pursued in sequence. The names, thresholds and even the existence of such protection differ entirely by country — which is exactly why the right question to your issuer is not "can I do a chargeback?" but "what routes do I have for this purchase, and what are the time limits on each?"

And if the underlying problem is that someone else used your card, that isn't really a chargeback question at all — it's a fraud report, it moves faster, and the card should be blocked. See which charges are worth worrying about and how to check whether a site is genuine.

What sinks a claim

• Not contacting the merchant first. Required by several codes; easy to do; keep the transcript.
• Missing the window. Especially on delayed deliveries, where waiting politely runs the clock down.
• Spending the provisional credit. It is reversible, and reversals arrive without ceremony.
• Describing the wrong grievance. "It's not as described" and "it never arrived" are different codes with different evidence. Pick the one that's actually true.
• No evidence. Order confirmation, listing screenshot, tracking, correspondence. The merchant will supply theirs.
• Raising it against the wrong transaction. Descriptors are often a parent company or processor rather than the trading name.
• Assuming chargeback is the only route. Statutory protection, where it exists, is frequently the better one.