Skip to content
Blogs
Tapaya

Payments Explained · 03

Chargebacks explained: what happens when a customer disputes a card payment

A refund is the merchant's decision. A chargeback is the cardholder's. How disputes work, who decides, how long each side has and what actually prevents them.

The short version

A refund is the merchant giving money back. A chargeback is the cardholder's bank taking it back, after the cardholder disputes the payment.

The dispute follows the card scheme's rules and deadlines, not the shop's returns policy. The merchant can accept it or answer with evidence, and the cardholder's bank decides.

Most chargebacks can be avoided. A name customers recognise on their statement, a clear receipt and a quick refund prevent more disputes than any dispute team wins.

1. Refund or chargeback?

 RefundChargeback
Who starts itThe merchantThe cardholder, through the bank that issued the card
Whose rulesThe merchant's own policy and consumer lawThe card scheme's rules (Visa, Mastercard)
Cost to the merchantThe amount refundedThe amount, a chargeback fee and the time spent on it
Effect on the merchantNone beyond the saleCounts towards the merchant's dispute ratio, which acquirers and schemes monitor
Can the merchant say no?It's their decisionOnly by answering with evidence

Chargebacks protect cardholders when a card is stolen, when goods never arrive, or when a merchant won't fix a genuine mistake. They are one reason people trust cards in the first place. But a chargeback is a forced reversal, so the schemes limit when it can be used and expect merchants to keep them rare.

2. How a dispute travels

Part 02 of this series introduced the roles. In a dispute, they act in this order:

  1. The cardholder complains to their bank, these days usually in the banking app.
  2. The issuer checks the claim. If it fits one of the scheme's reason codes, the issuer raises a chargeback through Visa or Mastercard. The cardholder often gets the money back provisionally.
  3. The acquirer receives it and takes the amount from the merchant's balance or next payout, usually with a fee. The merchant, or the PSP or platform in between, gets a notice with the reason and a deadline.
  4. The merchant decides: accept the chargeback, or answer with evidence. The answer is called a representment.
  5. The issuer reviews the evidence. If it is convincing, the money goes back to the merchant. If not, the chargeback stands.
  6. Pre-arbitration and arbitration. If both sides still disagree, the case can go to the card scheme, which rules on it. The losing side pays the scheme's fee, which can run to several hundred euros, so few cases get this far.

Visa calls the whole process a dispute, Mastercard a chargeback. The steps are the same.

3. Reason codes: what the cardholder says went wrong

Every chargeback carries a reason code. Visa groups its codes into four categories, and Mastercard's codes map onto similar groups.

CategoryTypical situationExample codes
FraudThe cardholder says they didn't make the payment.Visa 10.4 (fraud, card not present); Mastercard 4837 (no cardholder authorisation)
AuthorisationThe payment wasn't properly approved, for example it went through after a decline.Visa 11.x; Mastercard 4808
Processing errorsCharged twice, wrong amount, wrong currency, already paid another way.Visa 12.x; Mastercard 4834
Consumer disputesNot received, not as described, subscription cancelled, promised refund never arrived.Visa 13.x; Mastercard 4853

The reason code decides which evidence can win. A receipt proves the customer paid. It doesn't prove the goods arrived.

4. Deadlines on both sides

120 days
Cardholder: to raise a dispute

Generally counted from the payment, or from the date the goods or service were due. Some cases allow longer, up to 540 days.

30 / 45 days
Acquirer: to answer the issuer

About 30 days at Visa and 45 days at Mastercard.

14–21 days
Merchant: to send evidence

Usually what a merchant has to submit evidence. With Tapaya, the merchant simply replies to the dispute email.

0.9 %
Dispute ratio to stay below

Above this share of transactions, card networks can place a merchant in a monitoring programme, with higher dispute fees. More in section 7.

Two practical consequences: keep receipts, delivery records and customer messages for at least 18 months, and make sure dispute notices go to someone who reads them.

5. In person or online: who carries the fraud risk

The schemes move fraud liability to whoever had the better chance to stop it. This is called the liability shift.

  • In person, chip or contactless. When a card is read by chip or contactless and the payment is properly authorised, fraud with counterfeit, lost or stolen cards is in most cases the issuer's loss, not the merchant's. SoftPOS payments are contactless EMV payments, so the same logic applies. Above the contactless limit, the cardholder confirms with a PIN or by unlocking their phone or watch.
  • Online, with 3-D Secure. When the cardholder is authenticated with 3-D Secure, the strong customer authentication that EU rules require for most online payments, fraud chargebacks generally move to the issuer. When a payment goes through without it, under an exemption, the merchant usually keeps the risk.
  • What the liability shift doesn't cover. Consumer disputes. If the goods didn't arrive or weren't as described, how the card was read makes no difference.

That is why disputes at a shop counter are mostly processing errors (a double charge, a wrong amount) and consumer disputes about deposits, pre-orders or cancellations. Online, fraud and "not received" claims are far more common.

6. Answering a chargeback

ReasonEvidence that helps
Fraud (online)The 3-D Secure result, matching delivery and billing details, the customer's earlier undisputed orders, device and IP data
Processing errorRecords showing a single charge, the correct amount, or a refund already made
Not receivedProof of delivery or collection, a signed delivery note, tracking to the customer's address, photos of a completed service
Not as describedThe product description at the time of sale, the terms the customer accepted, your messages with the customer
Cancelled, or refund not processedThe cancellation terms the customer agreed to, and proof of when the refund was issued

A few rules hold for every case. Answer the reason code, not the whole story. Keep it short and factual. Send it before the deadline. And if the customer is right, accept and refund: a case you can't win only adds fees and time.

7. Keeping chargebacks rare

  • A name customers recognise. "I don't know this company" is one of the most common reasons people dispute a payment. The name on the bank statement should match the shop the customer remembers. With Tapaya, the statement descriptor is set for each merchant during onboarding.
  • A receipt every time. By email or text, with the shop's name, date, amount and a way to get in touch.
  • Easy refunds. A customer who can get a refund from you doesn't need to ask their bank.
  • Clear terms for deposits, pre-orders and subscriptions. Say what happens on cancellation before the customer pays.
  • No retrying declined payments. Pushing a payment through after a decline, or splitting it into smaller ones, invites authorisation chargebacks.
  • Watch your ratio. Card networks monitor dispute rates through programmes such as Visa's Acquirer Monitoring Program and Mastercard's Excessive Chargeback Program. Tapaya's documentation puts the line at 0.9 % of transactions: above it, a merchant may be placed in a monitoring programme, pays higher dispute fees, and can be suspended if the rate doesn't improve.

8. For platforms and payment providers

If your merchants take payments inside your software, their disputes reach them through you. A few things make that manageable:

  • Show disputes in your product. Which payment, how much, the reason in plain words and the deadline. A dispute nobody sees is a dispute lost.
  • Decide who answers. The merchant knows what happened, but you may hold the data that wins the case: order logs, delivery confirmations, timestamps.
  • Know who pays if a merchant can't. As part 02 explains, the payment facilitator pays first and the acquirer next. That is why reserves exist.
  • Track each merchant's ratio. A handful of risky merchants can put your whole portfolio under review with the acquirer.

9. Where Tapaya fits

How disputes run depends on how you work with Tapaya:

  • Software platforms and integrators using Tapaya end to end. Refunds and chargebacks run on the same platform as payments. Tapaya notifies you of a dispute by email and takes the amount plus a dispute fee from the merchant's balance. The merchant answers by replying with evidence, usually within 14 to 21 days, and disputes can also be managed in the dashboard or through the API. The issuer's review can take 60 to 75 days. If the merchant wins, the amount comes back; the dispute fee does not. Contactless wallet payments (Apple Pay, Google Pay) taken with the Accept SDK carry the liability shift, so fraud disputes on them are the issuer's loss.
  • Payment providers using Tapaya as white-label SoftPOS. Chargebacks, risk and settlement stay with you as the acquirer or PSP. Tapaya provides the acceptance technology and the transaction data your team needs as evidence.

If you'd like to see how disputes would flow for your merchants, talk to us. Developers can find refunds and the rest of the payments API in the Tapaya documentation.

Glossary

TermMeaning
ChargebackA reversal of a card payment, started by the cardholder through the bank that issued the card.
RefundMoney the merchant returns to the customer by choice.
Reason codeThe scheme's code for why the payment is disputed. It decides which evidence counts.
RepresentmentThe merchant's answer to a chargeback, with evidence.
ArbitrationThe final stage, where the card scheme decides a dispute and the losing side pays a fee.
Liability shiftThe rule that moves fraud losses to the issuer when the payment was properly secured, for example by chip, contactless or 3-D Secure.
Dispute ratioDisputes as a share of a merchant's payments, watched by acquirers and card schemes.