Dispute Operations Glossary 

0-9

60-day concept (Reg E) 

In Reg E contexts, customer error-notice windows are commonly anchored to statement availability - typically a 60-day reference point that operations teams document carefully. The operational discipline is to record the relevant dates at intake and escalate per policy if the notification timing may be late. The specific regulatory rules sit in Reg E itself and your institution's interpretation; the operational layer is consistent date documentation and timely escalation.

Related: Reg E · Regulated · Statement cycle · Investigation

 

A

Account takeover (ATO)

Account takeover refers to fraud where someone gains access to a customer's account through compromised credentials and conducts transactions without the customer's authorization. The cardholder did not participate, but the transactions occurred through their own account rather than card-not-present misuse of stolen card data. Operationally, ATO claims trigger an unauthorized investigation path with particular attention to access patterns, device fingerprints, and login history.

Related: Unauthorized transaction · Scam / social engineering · Investigation · Evidence package

 

Acquirer

The merchant's bank - the institution that receives transactions on behalf of the merchant and that handles incoming disputes and chargebacks from issuers. The acquirer sits on the opposite side of the dispute relationship from the issuer: where the issuer represents the customer, the acquirer represents the merchant. Understanding the acquirer's role matters operationally because chargeback rules and representment flows route through this counterparty.

Related: Issuer · Chargeback · Representment

 

Adjustment

A system or account correction that changes a balance without being a merchant-initiated refund. Adjustments can come from many sources (internal system corrections, fee reversals, error fixes) and they look similar to merchant refunds on the surface but operate through different mechanics. Operationally, distinguishing an adjustment from a refund matters because a true merchant credit may resolve a dispute on its own, while an adjustment may not.

Related: Refund (Credit) · Reversal · Merchant credit detected

 

Authorization

The initial approval-or-decline step at the moment a merchant attempts to charge a card: the merchant asks "can I charge this?" and the issuer responds. Authorization is not the same as settlement - an authorized transaction can still reverse, drop, or change amount before posting. Operationally, the gap between authorization and settlement is where some claims, especially pending-transaction confusion, need to be triaged carefully.

Related: Settlement (Posted) · Pending · Reversal

 

B

Business minimum

A small-dollar threshold below which the institution may resolve a customer claim without filing for recovery, on the basis that the operational cost of pursuing the chargeback exceeds the disputed amount. The threshold is set by policy and may differ by claim type. Operationally, business minimum auto-resolution requires the same documentation discipline as any other outcome path — eligibility check, red-flag review, and a clean closing note.

Related: De minimis · Recovery tool · Decision rationale

 

C

Canceled recurring

A claim category where the customer canceled a recurring or subscription relationship with the merchant, but charges continued after the cancel date. The operationally decisive facts are the cancellation date, the charge dates that followed, and whether the merchant's cancellation policy permitted the post-cancel charges. 

Related: Refund not received (RNR) · Quality dispute · Goods not received

 

Case notes

The written record of what an analyst reviewed and why a decision was reached. Strong case notes capture the allegation, the classification choice, the evidence reviewed, the reasoning behind the outcome, and the next step - enough that a different reviewer six months later could understand exactly how the decision was made. Case notes are the foundation of defensibility under audit, regulator review, escalation, and litigation hold.

Related: Decision rationale · Investigation · Evidence package

 

Chargeback

An issuer-initiated mechanism for challenging a merchant transaction through the card network's rules in order to recover funds. A chargeback is a tool, not a default action - it applies only when the dispute meets a recoverable category, timing requirements, scope discipline, and minimum evidence standards. Not every dispute becomes a chargeback; many claims resolve internally without ever entering the network recovery process.

Related: Recovery tool · Chargeback rights · Representment · Issuer · Acquirer

 

Chargeback rights

The set of conditions under which a chargeback submission is permitted by the applicable network rules: the claim fits an eligible category, timing gates are met, scope is clean, and minimum evidence exists. Programs that file chargebacks without confirming rights produce procedural denials and inflate operational waste. The discipline is to verify chargeback rights before submission, not after.

Related: Chargeback · Recovery tool · Evidence package · Representment

 

D

De minimis

A small-dollar auto-resolution threshold defined by policy, below which the operational cost of investigating and pursuing recovery exceeds the disputed amount. Programs use de minimis to credit clean low-dollar, low-risk claims at intake while routing higher-dollar or higher-risk claims into standard workflow. The discipline is to apply de minimis through clear eligibility rules and red-flag checks, not as a default for any small claim.

Related: Business minimum · Triage · Decision rationale

 

Decision rationale

The articulated "why" behind any outcome - approve, deny, close, hold, and the next step that follows. Decision rationale is what distinguishes a defensible decision from a procedurally-correct one: the analyst can point to the evidence, the framework, and the reasoning that bridged them. Without explicit rationale, even correct decisions look arbitrary under audit or escalation review.

Related: Case notes · Investigation · Reasonable investigation

 

Descriptor

The merchant name or label the customer sees on their statement, which can differ materially from the merchant's actual brand or trade name. A common source of customer confusion: the customer sees an unfamiliar descriptor and assumes the charge is fraudulent when it's actually a recognized purchase routed through a parent company or processor. Operationally, descriptor mismatch is a frequent root cause of "I didn't make this" claims that turn out to be authorized after triage.

Related: Authorization · Unauthorized transaction · Triage · Dispute intake

 

Dispute

A claim where a customer does not agree with a posted transaction - either because they did not authorize it or because they are challenging the outcome (non-receipt, cancellation, refund expected, processing error, or other). Dispute is the parent category; it covers everything from unauthorized fraud to merchant-dispute-only quality issues. Not every dispute becomes a chargeback, and not every customer complaint is a dispute - classification at intake decides which is which.

Related: Chargeback · Dispute intake · Triage · Issuer

 

Dispute intake

The point at which a dispute is reported and the minimum required facts are captured to create a workable claim record. Intake is not investigation, its purpose is to capture enough information to classify and route, not to decide. Strong intake discipline records the allegation in the customer's own words, captures key dates, and identifies the underlying transaction(s) without trying to resolve the claim at this stage.

Related: Triage · Investigation · Case notes

 

Duplicate charge

A processing-error claim category where the same purchase appears to have been processed more than once. The operational reality is that not every apparent duplicate is actually a duplicate - pending-and-posted pairs, authorization holds, and tip adjustments can create the visual pattern without a true duplicate. Scope discipline matters: confirm which transaction IDs and amounts are actually in scope before pursuing recovery.

Related: Wrong amount · Scope · Authorization · Pending