A payment dispute is an event, not a diagnosis. A decline is a decision, not proof the buyer was bad. Ecommerce teams have to protect the checkout while keeping legitimate customers moving—and preserve enough evidence to answer the issuer when a dispute arrives. This page follows the path from a disputed card payment through prevention, authentication, risk review and response. It separates cardholder disputes from refunds and product returns, and treats signals such as address matches or risk scores as evidence to weigh rather than verdicts. The examples are illustrative; card-network rules, issuer responses, processor labels and legal requirements vary by market and change over time.
🧭 Jump to a term
Start with the event: Chargeback · Friendly fraud · Account takeover (ATO) · Return fraud
Check the payment: Address Verification Service (AVS) · Card verification value (CVV) · 3-D Secure · Strong Customer Authentication (SCA) · Liability shift
Make and monitor decisions: Card testing · Fraud risk score · False decline · Velocity check · Chargeback ratio
Respond with evidence: Dispute reason code · Representment
⭐ Know these first
Start with Chargeback, Friendly fraud, Account takeover (ATO), Strong Customer Authentication (SCA), False decline. Then follow the grouped learning order below.
📎 How to read this page
What it means gives the precise meaning. Operator translation gives the version you might hear in a real ecommerce meeting. In real life shows an illustrative example. Watch out and the confusion boxes show where a familiar term can mislead.
📈 Read the relationships first
These combinations are diagnostic hypotheses, not proof of causality. Compare the same period and scope, then investigate the mechanism.
Disputes ↑ + authorization rate ↓
Usually means: loss controls or unclear billing may be affecting both outcomes. Check next: issuer and processor decline reasons, descriptor clarity, and dispute cohorts before changing a rule.
CVV / AVS mismatches ↑ + good-customer complaints ↑
Usually means: a verification rule may be catching legitimate variation. Check next: issuer coverage, market mix, address normalization, and the share of orders later confirmed as genuine.
Representment win rate ↓ + evidence missing ↑
Usually means: the team may be responding late or with evidence that does not match the dispute reason. Check next: reason-code workflows, deadlines, delivery records, and packet completeness.
Start with the event
01 · 🟢 Core
Chargeback = card-payment dispute
🧠 What it means
A cardholder disputes a card transaction through the issuer. If upheld under the network process, funds can be reversed from the merchant; the dispute is separate from a merchant-initiated refund.
💬 OPERATOR TRANSLATION
“The customer-service inbox just acquired a bank, a deadline and a tracking number.”
🛍️ In real life
A buyer says a $68 parcel never arrived. The merchant checks delivery evidence and the dispute deadline before deciding whether to respond.
⚠️ Watch out
A dispute is an allegation to assess, not proof that the customer acted dishonestly.
🔗 Related: Friendly fraud · Account takeover (ATO) · Return fraud · ↑ all terms
02 · 🟢 Core
Friendly fraud = first-party misuse
🧠 What it means
A cardholder disputes a purchase they or someone in their household made, sometimes because they do not recognize the descriptor, forgot the order, or misuse the dispute process. The label does not establish intent by itself.
💬 OPERATOR TRANSLATION
“Someone in the house placed the order; now the whole house is interviewing the bank.”
🛍️ In real life
A family sees an unfamiliar store descriptor for a delivery they recognize, so support sends the order details before assuming malice.
⚠️ Watch out
Treat the dispute evidence and customer explanation on their merits; do not label every mistaken claim fraud.
🔗 Related: Chargeback · Account takeover (ATO) · Return fraud · ↑ all terms
03 · 🟢 Core
Account takeover (ATO) = unauthorized account access
🧠 What it means
An attacker gains control of a customer’s online account, for example by using compromised credentials, and may change details or place orders. It is distinct from a customer disputing their own purchase.
💬 OPERATOR TRANSLATION
“The account changed its locks, and the actual customer is still outside.”
🛍️ In real life
A customer reports an unfamiliar address on their store profile; support secures access and checks recent account activity.
💡 Why it matters
Review account changes, login signals and payment activity together; one signal alone is not a verdict.
🔗 Related: Chargeback · Friendly fraud · Return fraud · ↑ all terms
04 · 🔵 Operations
Return fraud = deliberate abuse of a merchant return process
🧠 What it means
Return fraud describes intentional misuse of return rules, such as returning a different or empty item or making a false claim. A mismatch or late return is a review signal, not conclusive evidence of intent.
💬 OPERATOR TRANSLATION
“The return arrived. The product appears to have taken a different exit.”
🛍️ In real life
A returns team records parcel weight and item condition when a claimed product is missing, then follows its documented review and appeal process.
⚠️ Watch out
Separate documented evidence from suspicion, and apply a consistent, fair returns process.
🔗 Related: Chargeback · Friendly fraud · Account takeover (ATO) · ↑ all terms
Check the payment
05 · 🔵 Operations
Address Verification Service (AVS) = billing-address match check
🧠 What it means
Where supported, AVS compares address elements supplied with a card-not-present authorization against issuer records. Results are a signal for a decision rule; they do not verify the delivery address or prove identity.
💬 OPERATOR TRANSLATION
“The billing address got a vote. It did not get promoted to detective.”
🛍️ In real life
A cross-border order returns a partial address match; the team reviews it alongside other signals and the issuer’s AVS coverage.
⚠️ Watch out
AVS availability and match responses vary by issuer, card type and market.
🔗 Related: Card verification value (CVV) · 3-D Secure · Strong Customer Authentication (SCA) · ↑ all terms
06 · 🔵 Operations
Card verification value (CVV) = card security code
🧠 What it means
CVV, CVC and similar names refer to a short card verification code used in card-not-present flows to help check possession of card data. PCI DSS treats it as sensitive authentication data and prohibits storing it after authorization.
💬 OPERATOR TRANSLATION
“The three little digits have a short shift and no permission to stay overnight.”
🛍️ In real life
A checkout requests the code for authorization, then the merchant system does not retain it after the transaction is authorized.
⚠️ Watch out
Never retain the verification code after authorization, even in encrypted form; follow PCI DSS and provider requirements.
🔗 Related: Address Verification Service (AVS) · 3-D Secure · Strong Customer Authentication (SCA) · ↑ all terms
07 · 🔵 Operations
3-D Secure = card-payment authentication protocol
🧠 What it means
3-D Secure exchanges transaction and device context among merchant, issuer and card network. The issuer may authenticate in the background or request a challenge; the flow is not a guarantee against every dispute.
💬 OPERATOR TRANSLATION
“Sometimes the bank nods quietly. Sometimes it asks the customer to prove they are awake.”
🛍️ In real life
A shopper completes an issuer challenge on a higher-risk online payment; the checkout records the authentication result.
⚠️ Watch out
An authentication result does not erase every fraud type, dispute reason or merchant obligation.
🔗 Related: Address Verification Service (AVS) · Card verification value (CVV) · Strong Customer Authentication (SCA) · ↑ all terms
08 · 🟢 Core
Strong Customer Authentication (SCA) = at least two independent factors
🧠 What it means
Under PSD2, SCA generally uses at least two independent elements from knowledge, possession and inherence categories when the requirement applies. Scope, exemptions and liability depend on the transaction and applicable rules.
💬 OPERATOR TRANSLATION
“Password plus phone is a better pair than password plus another password in a hat.”
🛍️ In real life
For an in-scope EU remote card payment, a shopper confirms through two qualifying independent elements unless an applicable exemption is used.
⚠️ Watch out
SCA is a jurisdiction- and transaction-scoped regulatory requirement; check current rules and exemptions.
🔗 Related: Address Verification Service (AVS) · Card verification value (CVV) · 3-D Secure · ↑ all terms
09 · 🔵 Operations
Liability shift = conditional transfer of dispute responsibility
🧠 What it means
In some card-scheme and authentication circumstances, liability for specified unauthorized-payment disputes may shift between issuer, acquirer and merchant. The outcome depends on scheme rules, authentication data, transaction and reason code.
💬 OPERATOR TRANSLATION
“The risk bill moved desks. It did not vanish.”
🛍️ In real life
A qualifying authenticated transaction may receive a different liability treatment for certain fraud disputes, while other dispute types still require review.
⚠️ Watch out
Liability shift is conditional and reason-specific; it is neither universal nor a fraud shield.
🔗 Related: Address Verification Service (AVS) · Card verification value (CVV) · 3-D Secure · ↑ all terms
Make and monitor decisions
10 · 🔵 Operations
Card testing = checking whether payment credentials work
🧠 What it means
A pattern of low-value or repeated authorization attempts can be used to test payment credentials. Merchants monitor unusual attempt volume and coordinate controls with their payment provider without treating every burst as malicious.
💬 OPERATOR TRANSLATION
“One tiny order can be a typo. A hundred tiny orders are a meeting.”
🛍️ In real life
A small shop pauses repeated rapid authorization attempts and asks its processor to review the pattern.
⚠️ Watch out
Do not rely on low transaction value alone; check timing, repetition and legitimate traffic patterns.
🔗 Related: Fraud risk score · False decline · Velocity check · ↑ all terms
11 · 🔵 Operations
Fraud risk score = estimate used in a payment decision
🧠 What it means
A provider or merchant model combines available transaction signals into an estimate used to approve, review or decline a payment. Scores are model outputs, not proof that a person or order is fraudulent.
💬 OPERATOR TRANSLATION
“The score is a weather forecast for payments. Pack judgment, not an umbrella.”
🛍️ In real life
An order score prompts manual review; the analyst checks the order, account history and payment signals before acting.
⚠️ Watch out
Calibrate for false declines and changing customer mix; monitor outcomes by market and payment method.
🔗 Related: Card testing · False decline · Velocity check · ↑ all terms
12 · 🟢 Core
False decline = valid payment incorrectly rejected
🧠 What it means
A false decline occurs when a legitimate payment is rejected by an issuer or merchant risk control. It is hard to measure because the rejected purchase often leaves no completed transaction to label as genuine.
💬 OPERATOR TRANSLATION
“The customer had money, intent and a basket. The checkout had doubts.”
🛍️ In real life
A returning customer’s valid card is rejected by an overly strict rule, and the merchant loses the sale and possibly the next visit.
💡 Why it matters
Pair fraud loss metrics with approval and customer-experience measures; preventing every risky-looking payment can reject real buyers.
🔗 Related: Card testing · Fraud risk score · Velocity check · ↑ all terms
13 · 🔵 Operations
Velocity check = attempt-rate control over a time window
🧠 What it means
A velocity rule counts attempts or related signals within a defined interval, such as repeated authorizations tied to an account or device. The window and threshold are merchant or provider choices, not a universal standard.
💬 OPERATOR TRANSLATION
“A checkout may forgive one tap. It notices the fiftieth.”
🛍️ In real life
A merchant reviews a sudden run of repeated payment attempts from the same signal and applies a provider-supported rate control.
⚠️ Watch out
Set thresholds against normal retry behavior and monitor lockouts; an aggressive rule can block legitimate shoppers.
🔗 Related: Card testing · Fraud risk score · False decline · ↑ all terms
14 · 🔵 Operations
Chargeback ratio = network-defined disputes measure
🧠 What it means
A chargeback or dispute ratio compares a defined set of disputes with a scheme-defined transaction count or sales base over a specified period. Networks and monitoring programs can use different formulas and eligibility windows.
💬 OPERATOR TRANSLATION
“A ratio is only useful after someone tells Finance what went in the bottom half.”
🛍️ In real life
A payments lead compares the provider’s reported monthly ratio with its denominator, date window and programme definition before reacting.
⚠️ Watch out
Never compare ratios across providers until numerator, denominator, period and dispute stage match.
🔗 Related: Card testing · Fraud risk score · False decline · ↑ all terms
Respond with evidence
15 · 🔵 Operations
Dispute reason code = category assigned to a card dispute
🧠 What it means
A network or processor reason code classifies the basis of a dispute and helps determine what evidence or process applies. Labels and code sets vary by scheme and can change.
💬 OPERATOR TRANSLATION
“The bank has filed the complaint under a heading. Read the heading first.”
🛍️ In real life
A delivery dispute and a duplicate-charge dispute require different transaction records, even when both appear as chargebacks.
⚠️ Watch out
Do not treat a processor’s display label as interchangeable with every network’s code list.
🔗 Related: Representment · ↑ all terms
16 · 🔵 Operations
Representment = merchant response to a card dispute
🧠 What it means
Representment is the process of submitting relevant evidence through the acquirer or processor to contest a chargeback. Evidence and deadlines depend on the dispute reason and network rules; submitting evidence does not assure a win.
💬 OPERATOR TRANSLATION
“The merchant gets one organized chance to tell the timeline with receipts.”
🛍️ In real life
For a non-receipt dispute, a merchant submits the order, shipping and delivery records requested for that case before its deadline.
⚠️ Watch out
Tailor evidence to the reason code and submit by the displayed deadline; keep the packet factual and relevant.
🔗 Related: Dispute reason code · ↑ all terms
🔀 Return vs refund vs chargeback
A return moves a product back; a refund is a merchant-initiated money return; a chargeback is a cardholder dispute routed through the payment network. A return can lead to a refund without a dispute.
🔀 Retailer chargeback vs card chargeback
A retailer chargeback is a commercial deduction under a retailer agreement. This page uses card chargeback for a cardholder dispute; the processes, evidence and counterparties differ.
🔀 Fraud signal vs proof of fraud
An AVS result, score, velocity rule or customer complaint can inform review. None establishes intent alone; use relevant evidence and a documented decision process.
🔀 SCA vs 3-D Secure
SCA is a legal authentication requirement in applicable PSD2 situations; 3-D Secure is a card-payment protocol that can carry authentication. They are related, but not interchangeable.
🤔 Still confused?
Follow this thread: Chargeback → Address Verification Service (AVS) → Card testing → Dispute reason code. That sequence moves from the basic object or relationship to the decisions and checks it supports.
Sources and scope
Primary documentation checked on 27 September 2026. Platform features and eligibility can change; examples and cartoon situations are illustrative.
