Chargebacks Explained for Small Businesses

A chargeback can turn a finished sale into lost money, a lost product and an extra fee, all from one email you did not expect. The good news is that most chargebacks follow a predictable pattern, and a little preparation goes a long way. Here is how chargebacks work for small businesses, how to respond with the right evidence and how to stop many of them before they start.

Smartphone held in a hand with an app open on the screen, the kind of device customers use to dispute a payment — For a customer, disputing a charge can take a few taps. Your response takes more planning.

Key takeaways

A chargeback happens when a cardholder asks their bank to reverse a payment. The money is pulled back from you while the dispute is reviewed.
Card network rules apply. Your processor sets the deadline for your response and often charges a fee for each chargeback, win or lose.
You win disputes with clear evidence, such as proof of delivery and records of customer communication, sent before the deadline.
Prevention is cheaper than fighting: clear billing names, easy refunds, honest product pages and fast replies stop many disputes.

Every business that accepts cards will see a chargeback eventually. Some are genuine fraud, where a stolen card was used. Some are honest confusion, like a customer who does not recognize your business name on their statement. Some are customers who would rather call their bank than ask you for a refund. All of them cost you time and money.

Understanding the process takes away a lot of the stress. Once you know what happens, what the bank looks for and where your evidence lives, a chargeback becomes a task on your list rather than a crisis.

What a chargeback actually is

A chargeback is a forced reversal of a card payment. The customer, called the cardholder, contacts the bank that issued their card and disputes a transaction. The bank pulls the funds back through the card network, and your processor takes the amount from your balance, usually along with a dispute fee.

It is different from a refund. A refund is something you choose to give. A chargeback is decided by the customer's bank under the card network's rules, and you have to make your case to get the money back.

Who is involved

The cardholder: your customer, who starts the dispute.
The issuing bank: the customer's card provider, which reviews the claim and makes the decision.
The card network: sets the rules, reason codes and timeframes that everyone follows.
Your processor or acquirer: the company that handles your card payments, such as Stripe, Square, PayPal or Adyen. It notifies you, passes your evidence along and applies its own deadlines and fees.
You, the merchant: responsible for responding with evidence or accepting the dispute.

Deadlines and fees Card network rules govern chargebacks; processors set response deadlines and often charge a fee per chargeback Card network and processor rules

How the chargeback process works

The exact steps vary by network and processor, but the broad lifecycle looks like this:

The customer disputes the charge with their card issuer, giving a reason.
The issuer reviews the claim and, if it goes ahead, sends the chargeback through the card network with a reason code.
Your processor notifies you and debits the disputed amount, plus any dispute fee, from your balance.
You decide: accept or respond. If you respond, you submit evidence through your processor before its deadline.
The issuer reviews your evidence and decides. If you win, the funds come back. If you lose, the reversal stands.
Further stages may follow in some cases, depending on network rules. Your processor will tell you what is possible.

The deadline is the part that catches people out. Miss it, and you usually lose by default, no matter how strong your case was.

Common mistake

Letting dispute notices land in an inbox nobody checks. Make sure your processor's alerts go to an address someone reads every working day, and add a second person as backup during holidays.

Why customers file chargebacks

Each chargeback carries a reason code. The codes differ by network, but most fall into a few familiar groups:

Fraud or unauthorized use: the cardholder says they did not make the purchase.
Item not received: the order never arrived, or arrived very late.
Not as described or defective: the product or service did not match what was promised.
Cancelled subscription: the customer says they cancelled but were charged again.
Duplicate or incorrect charge: charged twice, or charged the wrong amount.
Credit not processed: a promised refund never showed up.
Unrecognized charge: the customer does not recognize your business on their statement.

Some disputes are what the industry calls friendly fraud: the purchase was real, but the customer disputes it anyway, sometimes by mistake and sometimes not. Good records are your best defense.

Example

Jordan runs a small online store selling coffee equipment. A customer disputes a $180 order (made-up figure) as "item not received." Jordan checks the order: the parcel was shipped with tracking, marked delivered to the customer's address, and the customer emailed two days later asking how to descale the machine. Jordan submits the tracking record, the delivery confirmation, the order details and that email thread through the processor, with a short cover note explaining the timeline. The evidence shows the customer received and used the product.

Person holding a tablet in both hands, reviewing order details and records on the screen — Strong responses come from records you keep every day, not ones you rush to find.

How to respond to a chargeback

When a dispute arrives, take a breath and work through it calmly. A clear, well-organized response beats a long, angry one every time.

First, decide whether to fight

Not every chargeback is worth contesting. If the customer has a fair point, for example the item really was faulty or you forgot to process a refund, accepting the dispute can be the honest and efficient choice. Contest disputes where you have solid evidence that the charge was valid and the customer got what they paid for.

Then, gather the right evidence

Match your evidence to the reason code. Useful items include:

Proof of delivery: tracking numbers, delivery confirmations, signatures or photos where available.
Customer communication: emails, chat logs or messages showing the customer received, used or acknowledged the purchase.
Order details: invoice, receipt, billing and shipping addresses, and what was bought.
Your policies: refund, cancellation and terms of service, plus proof the customer agreed to them at checkout.
Service records: for services, booking confirmations, attendance logs or delivered work.
Subscription records: sign-up date, renewal reminders sent and cancellation history.

Finally, write a short cover note

Summarize the case in a few plain sentences: what was bought, when, how it was delivered and why the charge is valid. Point to each attached document. Keep it factual and polite, because a person at the bank will read it.

Pro tip

Build a reusable evidence pack for each common reason code. When a dispute comes in, you fill in the blanks rather than starting from scratch, and you are far more likely to beat the deadline.

Chargeback evidence log template

Keep one row per dispute. It helps you hit deadlines and spot patterns over time. The amounts are made-up examples.

Date received	Order ID	Amount	Reason given	Response deadline	Evidence sent	Decision	Outcome	Lesson
3 Sep	#4821	$180	Item not received	Per processor notice	Tracking, delivery confirmation, customer email	Respond	Pending	Add delivery photo where possible
9 Sep	#4877	$45	Cancelled subscription	Per processor notice	None	Accept	Lost	Make cancel button easier to find
14 Sep	#4902	$260	Unrecognized charge	Per processor notice	Receipt, order details, IP and address match	Respond	Won	Update statement descriptor

Review the "Lesson" column every month. It turns individual losses into fixes for your business.

How to prevent chargebacks

The cheapest chargeback is the one that never happens. Most prevention comes down to clarity and good service.

Use a recognizable billing name. Make sure your statement descriptor matches the name customers know, and add a website or phone number if your processor allows it.
Make refunds easy. A customer who can get a quick refund from you rarely calls their bank.
Describe products honestly. Clear photos, sizes and limits reduce "not as described" claims.
Send confirmations and tracking. Order and shipping emails remind customers what they bought and when it will arrive.
Remind before subscription renewals. A short reminder email and an easy cancel option prevent many disputes.
Respond fast. Answer customer messages quickly, especially complaints.
Use fraud screening. Tools such as Stripe Radar, Chargeflow and Chargebacks911 offer fraud screening or dispute help. Check current features, pricing and privacy policies before signing up.

Common mistake

Refunding a customer after they have already filed a chargeback. You can end up paying twice: once through the refund and once through the chargeback. If a dispute is open, handle it through the dispute process and ask your processor how to proceed.

Getting ready for the autumn rush

As September arrives and the holiday season starts to build, order volumes climb and so can disputes, especially "item not received" claims when carriers are busy. Use the quieter end of summer to tidy your policies, check your billing name, set up evidence packs and confirm who handles dispute alerts.

A brief note: this article is general information, not legal or financial advice. Chargeback rules differ by card network, processor and country, so read your processor's current dispute documentation and ask a qualified professional if a large or complex dispute comes up.

Your chargeback action checklist

Send processor dispute alerts to an inbox someone checks daily
Check that your billing name is easy to recognize
Make your refund and cancellation policies clear and easy to find
Keep proof of delivery and customer messages for every order
Prepare evidence packs for your most common reason codes
Start a chargeback log and review it monthly
Never refund an order that already has an open dispute

Frequently asked questions

How long do I have to respond to a chargeback?

Your processor sets the deadline, based on card network rules, and it is usually shown in the dispute notice and your dashboard. Treat it as firm and aim to respond well before it.

Do I get the dispute fee back if I win?

It depends on your processor. Some keep the fee regardless of the outcome. Check your processor's current dispute terms.

Can too many chargebacks cause problems?

Yes. A high dispute rate can lead processors to hold funds, add reserves, raise costs or close an account. Watching your chargeback rate and acting on patterns early helps keep your account in good standing.

Should I contact the customer directly?

A polite message can clear up confusion, for example if they did not recognize your business name. Keep the conversation on record, and follow your processor's guidance on whether the customer needs to withdraw the dispute with their bank.

The bottom line

Chargebacks are part of taking card payments, but they do not have to be a mystery. Know the process, watch the deadline, and answer with clear evidence such as delivery proof and customer messages. When a dispute is fair, accept it and fix the cause.

Most of all, prevent what you can: a recognizable billing name, easy refunds and honest product pages stop many disputes before they begin. Set up your log and evidence packs now, and the busy season will feel a lot calmer.