Dispute Operations Glossary
Fifty operational terms used inside mature issuer-side dispute programs - the vocabulary analysts, dispute leads, fraud and risk ops, and fintech operations teams use every day. Each entry explains what the term means, why it matters operationally, and how it connects to the rest of the dispute lifecycle.
Scope note: This is not legal advice. Your institution's policies, tooling, and letter requirements vary. The goal is consistent classification, defensible evidence gathering, and correct routing.
#
60-day concept (Reg E)
A timing-context anchor often referenced in Reg E disputes: the window during which a customer is expected to notify the institution of an error tied to statement availability. The operational implication for analysts is that statement dates must be documented carefully on every Reg E claim, and any claim that may fall outside the standard window should be escalated per institution policy rather than handled by individual judgment. The specifics of how the window applies, what triggers it, and what exceptions exist sit in the regulation and your institution's policies.
A
Account takeover (ATO)
A fraud scenario in which someone gains unauthorized access to a customer's account credentials and conducts transactions using that access. Operationally, ATO claims fall into the unauthorized category - the customer did not authorize and did not benefit - but the investigation pattern differs from a stolen-card scenario because the compromise vector is credential-based rather than physical. Analysts should look for indicators of credential compromise (unfamiliar device, location, behavior pattern) and document the access vector separately from the transaction-level evidence.
Acquirer
The merchant's bank - the institution that receives the original transaction from the merchant and is the party on the other side of any chargeback or recovery action initiated by the issuer. The acquirer typically responds on the merchant's behalf in representment, supplying the merchant's evidence package. In the dispute lifecycle, the acquirer is the counterparty in the recovery path; the customer's direct relationship is with the issuer, not the acquirer.
Adjustment
A system or account correction that may change balances without being a merchant-initiated refund. Operationally, adjustments need to be documented distinctly from refunds because the source and nature of the credit affect how scope is calculated and whether duplicate-credit risk exists. Analysts running triage should treat an adjustment as one possible explanation for an unexpected credit on the account — and confirm before assuming it's a merchant refund.
Audit Readiness
The operational state in which any case file pulled at random can be defended on its merits without requiring the analyst who decided it to explain the reasoning. Audit readiness is a function of decision-time documentation discipline and QA calibrated to the defensibility standard - not a periodic clean-up effort before a known audit.
See: What Is a Defensible Dispute Decision?
Authorization
The initial approval-or-decline step of a transaction, where the merchant asks the issuer "can I charge this?" before the transaction is settled. Authorization is not the same as a posted transaction - it creates a pending status that may eventually settle, reverse, or drop entirely. Operationally, the distinction matters because disputes generally apply to settled (posted) transactions, while pending transactions may resolve on their own without action.
B
Business minimum
A small-dollar threshold above which an institution will pursue a recovery action and below which it will resolve the claim internally without recovery, on the basis that processing cost would exceed the value being recovered. Sometimes called a de minimis threshold in operational contexts. Setting and respecting this threshold consistently is what distinguishes a mature operation from one that wastes operational capacity on low-value recovery work.
C
Canceled recurring
A claim type in which a customer canceled a recurring subscription or service but continued to be charged after the cancellation date. Operationally, the decisive facts are the cancel date and the charge date — and which scope of charges fall on which side of that line. Investigation centers on the cancellation evidence (confirmation message, support ticket, account flag) and the timing relationship to the disputed charges.
Case notes
The written record of what an analyst reviewed, what they considered, and why they decided as they did. Case notes are the single most important defensibility asset in any dispute program: they are what an auditor, regulator, escalation reviewer, or QA team will use to reconstruct the decision months after the analyst has moved on. Strong case notes capture allegation, classification, scope, timing anchors, evidence reviewed, decision rationale, and the next step.
Chargeback
The recovery mechanism by which an issuer challenges a settled transaction with the merchant or acquirer, attempting to recover funds on behalf of the customer through the card network's rules. A chargeback is not the same as a customer dispute - it is one possible recovery tool applied within the dispute lifecycle, and only when classification, timing, evidence, and scope all qualify. Treating chargeback as the default response to every dispute is one of the most common operational mistakes in dispute programs.
Chargeback rights
The conditions under which a recovery submission is permitted: classification must fit an eligible category, timing gates must be met, evidence must be sufficient, and scope must be clean. Chargeback rights are not automatic - they exist only when the case meets the relevant network's reason-code criteria. The operational discipline is to confirm chargeback rights exist before pursuing recovery, not to file first and discover the rights are insufficient at representment.
D
De minimis
A small-dollar threshold below which a claim is auto-resolved (credited and closed) without further investigation or recovery action, because the operational cost of working the case exceeds its value. De minimis decisions still require minimum documentation, eligibility checks, and red-flag screening - they are not "no work" decisions, they are "no recovery" decisions. Programs that build de minimis triggers into intake workflow free up senior judgment for the cases that actually need it.
Decision rationale
The articulated reasoning behind a dispute decision: why a claim was approved, denied, held, or closed; what evidence drove the decision; and what alternatives were considered before settling on the outcome. Decision rationale is what makes a case file survive scrutiny months later. Capturing what was reviewed is straightforward; capturing why one interpretation was chosen over another is the operational judgment layer that defines defensibility.
Descriptor
The merchant name or label a customer sees on their statement, which can differ - sometimes significantly - from the brand name the customer used at point of purchase. Descriptor confusion is one of the most common drivers of disputes that turn out to be recognized transactions: a customer doesn't recognize the descriptor, files a fraud claim, and the analyst's job at triage is to test whether the descriptor matches a recognized merchant relationship. Resolving descriptor confusion is often the difference between a misclassified fraud claim and a closed-with-explanation case.
Defensible Decision
A dispute decision that is correct, explainable, and survivable: the disposition the facts support, the reasoning a later reviewer can reconstruct from the case file alone, and the conclusion that holds up when an auditor or external examiner pulls the case months after closure. Defensibility is the operational standard issuer dispute programs are actually held to - distinct from closure speed or volume metrics.
See: What Is a Defensible Dispute Decision?
Dispute
A claim in which 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, billing error, or other reason). A dispute is the customer-facing claim to the issuer; a chargeback is one possible downstream action within the dispute. The dispute is the system; the chargeback is a tool the system may or may not deploy.
Dispute intake
The point at which a customer's claim is captured and the minimum required facts are recorded to classify and route the case. Effective intake captures the customer's allegation in their own words, the transaction details, and any indicators that affect routing - not every available piece of information, just enough to drive classification. Strong intake makes everything downstream easier; weak intake creates rework that compounds across the entire lifecycle.
Duplicate charge
A processing error in which the same purchase is processed more than once. Operationally, duplicate charges require careful scope work: confirming which transactions are actually duplicates versus separate authorized transactions that happen to look similar, and identifying whether one of the charges has already been reversed or refunded. Scope errors at this layer create either under-recovery or duplicate credits that have to be reversed later.
E
EFT (Electronic Fund Transfer)
Money movement initiated electronically — including debit card transactions, ATM withdrawals, peer-to-peer transfers, and many ACH and online transfers. EFTs are the transaction class typically covered by Reg E in error-claim contexts. Operationally, identifying whether a transaction is an EFT on a deposit or prepaid account (vs. a credit transaction) is the first routing question because it determines which posture applies.
Evidence package
The collection of documents, records, and data submitted to support a dispute decision or recovery action: customer-facing inputs (claim filing, communications), transaction record, merchant or counterparty evidence, and internal reasoning notes. Effective evidence packages are relevant, labeled, and consistent with the case narrative - not exhaustive. The discipline is to assemble what supports the decision, not everything that exists.
G
Goods not received
A dispute category in which the customer authorized a purchase but did not receive the goods or services after the merchant's promised delivery window. Operationally, the decisive facts are the delivery promise (what was promised, by when), the current status (delivered, in transit, lost, returned), and any merchant-side resolution attempt. Goods-not-received cases sit in the merchant-dispute-only category and follow a different investigation path than unauthorized transactions.
H
Hold (recheck)
A triage decision in which a case is set aside with a specific recheck date — not closed, not investigated yet — because the status of the underlying transaction or refund is expected to change soon. Hold-with-recheck is the operational tool that prevents premature decisioning on pending transactions, in-flight refunds, and adjustments that haven't settled. Programs that don't use hold-with-recheck systematically force every case toward immediate investigation, which produces avoidable rework and reopens.
I
Investigation
Evidence-based review and decisioning on a dispute claim, especially for regulated claims where standards apply. Investigation is the work of weighing the customer's narrative against the transaction record and available evidence, then producing a documented decision with rationale. Not every claim needs investigation at full depth — some triage outcomes (de minimis, merchant credit detected, customer cancellation) resolve the case without entering the investigation path at all.
Issuer
The customer's bank — or, in fintech programs, the sponsor bank that holds the issuer-of-record relationship with the cardholder. The issuer is the party responsible for dispute decisioning: classifying the customer's claim, applying the right investigation posture, deciding the outcome, and managing the documentation that makes the decision defensible later. In fintech models, the program team typically runs day-to-day operations while the sponsor bank carries the regulatory accountability.
M
Merchant credit detected
A triage outcome in which the analyst confirms that a merchant credit, refund, or reversal has already posted to the account (or is clearly in-flight), making further recovery action unnecessary. Detecting merchant credits at triage is one of the highest-leverage operational disciplines: it prevents duplicate credits, avoids unnecessary chargeback submissions, and closes cases cleanly without burning investigation capacity. Programs that skip this check at triage routinely process recovery on cases that are already resolved.
N
Need More Information (NMI)
A targeted request to the customer for decision-driving documents or details, paired with a deadline and clear next-step rules if the customer does or does not respond. NMI is not a generic "tell us more" — it is a specific request for items that, if provided, would change the operational decision. The discipline is to request only what changes the decision, not everything that might be helpful.
Not as described (NAD)
A dispute category in which the customer authorized a purchase but received goods or services that materially differ from what was represented at purchase. The operational distinction from goods-not-received is that the customer received something — it just isn't what they were promised. NAD cases require evidence on both sides: what was represented (the listing, the advertisement, the description) and what was actually delivered.
P
Paid by other means
A dispute category in which the customer paid for the same purchase using a different payment method (cash, another card, etc.), meaning the disputed charge should not have been processed. Operationally, the decisive evidence is the alternate payment record and the timing relationship between the two payments. Paid-by-other-means cases overlap with duplicate charges but are distinct: duplicates are the same payment processed twice; paid-by-other-means is two different payments for the same purchase.
Partial refund
A refund in which only part of the disputed amount has been credited back, leaving a remaining scope that may still be in dispute. Operationally, partial refunds require scope work: confirming what was refunded, what remains in dispute, and whether the customer accepts the partial resolution or wants to continue pursuing the remainder. Programs that skip the scope confirmation often misfile recovery on the wrong amounts.
Pending
A transaction that has been authorized but not yet finalized — it may post (settle), reverse, or drop. Pending transactions generally cannot be disputed at the formal level because the transaction isn't yet settled, but they can be flagged, monitored, and held for recheck. The operational discipline is to identify pending status at triage and route to hold rather than forcing the case forward prematurely.
Preliminary investigation
The pre-decision work that combines intake, triage, and basic checks before the case enters a defined outcome path - close, hold, NMI, full investigation, or recovery readiness. Preliminary investigation is the operational stage where the analyst decides which path applies, not what the outcome will be. The strength of preliminary investigation directly determines how clean the rest of the lifecycle runs.
Provisional credit (PC)
A temporary credit applied to a customer's account while a regulated dispute is under review, restoring the disputed funds during the investigation period. Provisional credit is reversible: it can be adjusted or removed based on the outcome of the investigation. The operational discipline around provisional credit is timing - applying it within the required window rather than waiting for the investigation to conclude.
Q
Quality dispute
A claim in which a customer is dissatisfied with goods or services after an authorized purchase, but the dissatisfaction is not a billing error or processing error. Quality disputes sit in the merchant-dispute-only category and require investigation of the customer's expectations, the merchant's representations, and what was actually delivered. They are distinct from unauthorized claims (no participation issue) and processing errors (no system issue).
R
Reasonable investigation
An evidence-based, documented review meeting the applicable operational standard. Reasonable investigation is not "investigate everything" - it is investigation appropriate to the claim type, the evidence available, and the level of scrutiny the decision is likely to face. The operational discipline is to avoid both under-investigating (skipping evidence that would change the decision) and over-requesting (asking for documents that don't change anything).
Reasoning Bridge
The portion of a case note that connects the evidence to the disposition: why this evidence supported this outcome and not the plausible alternative. The reasoning bridge is the documentation element AI tools most reliably miss when generating case notes, even when the surrounding summary reads fluent and complete.
See: What Is a Defensible Dispute Decision?
Recovery tool
A rule-based mechanism for attempting to recover funds - most commonly the chargeback, but also network-specific pre-arbitration, arbitration, and other recovery actions depending on the case. Recovery tools are not automatic - they are deployed only when the case meets the rules of the relevant tool: classification fit, timing, evidence, and scope. Treating recovery tools as defaults rather than conditional actions is one of the most common operational errors in dispute programs.
Refund (Credit)
Money returned to the customer after a transaction has settled, distinct from an authorization reversal (which cancels a transaction before it posts). Refunds may be initiated by the merchant, processed via the issuer, or applied as adjustments. The operational discipline is to verify the source and timing of any credit on the disputed account before assuming it has resolved the dispute.
Refund not received (RNR)
A dispute category in which the merchant has promised a refund but it has not posted to the customer's account within a reasonable window. Operationally, RNR cases require scope work to identify which portion of the refund was promised, whether any partial credit has posted, and whether the merchant's promise was conditional. Investigation centers on the refund promise, the timing window, and the partial-credit status.
Reg E
A federal rule set that governs many debit card and electronic-fund-transfer error claims, with associated timing standards and investigation expectations. Operationally, Reg E creates a "regulated" posture for claims that fall under its scope — meaning the analyst applies specific timing discipline and investigation standards, and documents key dates carefully. The specifics of which transactions fall under Reg E, what timelines apply, and what exceptions exist sit in the regulation and your institution's policies.
Reg Z
A federal rule set that governs many credit card billing-error disputes, with associated statement and notice posture and specific billing categories. Operationally, Reg Z applies to credit-account disputes (as distinct from debit/EFT disputes under Reg E) and creates its own regulated investigation posture. The analyst's job is to identify which posture applies and follow the corresponding operational discipline — not to interpret the regulation itself.
Regulated
A dispute posture in which the claim is covered by an applicable regulation (such as Reg E or Reg Z), meaning specific timing standards and investigation expectations apply. Operationally, regulated claims require careful date documentation, defined investigation steps, and consistent decision standards. The operational distinction from unregulated claims is procedural: regulated claims follow a defined posture, unregulated claims follow merchant-dispute-only patterns.
Reopen
The re-activation of a closed dispute claim, typically because new information has surfaced or a prior decision is being corrected. Reopens are a quality signal: a high reopen rate indicates that initial classification, evidence review, or documentation was weak. Programs that focus on reducing reopens — through better triage, stronger evidence discipline, and clearer documentation — see compounding improvements in both customer experience and operational capacity.
Representment
The merchant or acquirer response that contests an issuer's chargeback submission, typically by providing evidence intended to defend the merchant's position. Operationally, representment review is evidence matching against timeline logic: does the merchant's evidence support a defensible position, and does the timing align with the case facts? Representment is the moment where recovery is either confirmed or unwound — and it tests the original case file's strength.
Returned
A dispute scenario in which a customer has returned goods to the merchant per the merchant's return policy and expects a refund that has not posted. Operationally, the decisive facts are the return evidence (return label, tracking, merchant confirmation), the return date, and the merchant's stated refund timeline. Returned cases overlap with refund-not-received but center on the customer's return action rather than a standalone refund promise.
Reversal
The cancellation of an authorization before the transaction has settled — distinct from a refund, which returns money after settlement. Operationally, reversals are most relevant at triage: a pending transaction that reverses is not a posted transaction and typically does not enter the dispute path. Misidentifying a reversal as a refund (or vice versa) creates scope errors that propagate through the case.
S
Scam / social engineering
A claim category in which the customer made or authorized the disputed transaction, but did so under deception or pressure — the participation was real, but obtained through misrepresentation. Scam and social engineering are often miscalled "fraud" by customers, but the participation distinction is operationally critical: scams are not unauthorized transactions, and labeling them as such creates inconsistent outcomes. Investigation centers on the deception pattern, the customer's role, and the recovery analysis specific to the scam category.
Scope
The exact set of transaction IDs, amounts, and partial credits in scope of the dispute after accounting for any partial refunds, adjustments, or merchant credits already applied. Scope discipline is what separates clean recovery cases from messy ones — without confirmed scope, recovery actions get filed on wrong amounts and representment review surfaces inconsistencies that weren't documented earlier.
Settlement (Posted)
The finalization step of a transaction, where the authorization is converted into a posted transaction on the account. Settlement is the point at which the transaction becomes actionable for most dispute workflows — pending transactions generally aren't actionable until they post (or drop). The operational distinction between pending and posted is one of the most common triage failure points.
Statement cycle
The billing or statement period during which a transaction first appears on the customer's account. Statement cycle is critical for timing posture on regulated claims — particularly for Reg E and Reg Z error windows — because the timeline anchors to statement availability rather than the transaction date. Documenting the statement cycle accurately at intake prevents timing errors downstream.
T
Triage
The fast checks performed in the first two minutes of working a dispute claim — typically posted status, merchant credit detection, de minimis eligibility, NMI readiness — to choose the correct outcome path and prevent rework. Triage is not investigation; it is the routing decision that determines whether investigation is even necessary. Programs that triage well move volume cleanly without sacrificing decision quality.
U
Unauthorized transaction
A claim category in which the customer did not authorize the transaction, did not benefit from it, and gave no permission for it. Unauthorized is distinct from scam (which involves participation under deception) — the participation check is the diagnostic that distinguishes the two categories. Investigation of unauthorized claims centers on access, identity, and pattern: did the cardholder make the transaction, or didn't they?
Unregulated
A dispute posture in which the claim is not covered by Reg E or Reg Z and is handled as a merchant-dispute-only case under institutional policy and network rules. Unregulated does not mean the case is less important — it means the operational discipline shifts from regulatory timing standards to policy-based eligibility windows and evidence-alignment standards. Investigation still requires consistent decisioning and defensible documentation.
W
Wrong amount
A dispute category in which the posted transaction amount differs from what the customer agreed to at purchase — sometimes involving tips, deposits, or travel-and-entertainment-related charges that have specific handling patterns. Operationally, wrong-amount cases require evidence on both sides: what the customer agreed to (receipt, terminal display, merchant disclosure) and what posted. Scope work is critical because the disputed amount is often only a portion of the total transaction.
This is the public reference version.
The full Dispute Operations Terminology Cheat Sheet (printable, working-desk format with module cross-references) is included inside Dispute Analyst Toolkit and Tier 1 Foundations. Built for analysts who need the vocabulary at their fingertips while working tickets, not just while learning the field.
Explore the Toolkit
Compiled by Haykanush Shahbazyan, founder of Dispute Academy and a fintech dispute operations leader with more than a decade of experience building issuer-side programs.
