Disputes & Chargebacks

Why this topic matters

Disputes and chargebacks protect customers and the bank when a transaction is challenged. A consumer may say a card transaction was unauthorized, a merchant did not deliver goods, an ATM did not dispense cash, a duplicate debit appeared, or a refund never arrived. A business may dispute a corporate card charge, supplier payment, direct debit, merchant settlement, payroll item, or account adjustment. The bank must determine eligibility, gather evidence, meet timing obligations, post provisional or final credits correctly, communicate clearly, and reconcile loss or recovery.

A dispute is not simply a complaint. It is a structured financial investigation with rules, evidence, statuses, accounting, and customer rights. A chargeback is a specific dispute process through card-scheme rules, usually involving issuer, acquirer, merchant, evidence cycles, reason codes, representment, and potential arbitration. Payment disputes outside card rails may follow recall, return, investigation, indemnity, or legal processes. The bank must avoid mixing these concepts because wrong language can create wrong expectations.

Shared servicing controls

The Operations and Servicing chapter covers shared intake, queue ownership, approvals, communication and quality review. This chapter applies them to the specific financial process below.

Choose the right dispute process and clock

Intake should record the alleged error, amount/currency, account/product, transaction reference, customer authority, date of transaction, date of notice, relevant statement and claimed remedy. Classify unauthorised use, processing error, merchant-service dispute, authorised scam and complaint separately. Block a compromised credential where appropriate without assuming that blocking proves liability or completes reimbursement.

Under US Regulation E §1005.11, the ordinary investigation period is ten business days; qualifying extended investigation generally involves provisional credit and up to 45 calendar days. The regulation specifies exceptions, including 20 business days for certain new-account transfers and 90 calendar days for specified cases. Record applicable conditions and notices rather than hard-coding one global chargeback deadline. Consumer credit-card billing errors have a separate source: Regulation Z §1026.13.

For a fictional disputed debit of 300, an approved provisional credit increases the customer's deposit liability by 300 against the bank's approved dispute receivable or expense/control account. It does not erase the original transaction or establish recovery from the acquirer. Track provisional customer credit, scheme recovery, merchant refund, final outcome and any lawful removal of credit separately. If a merchant refund later arrives, match it before giving another final credit; duplicate reimbursement is a financial-control defect.

Issuer operations assembles evidence and determines the customer outcome under law/policy; the acquirer obtains merchant evidence and handles its scheme obligations; finance reconciles credits, recoveries and loss. Log reason codes, presentment date, evidence deadlines, submission, response, representment and escalation, using current scheme rules. Do not call a debit 'authorised' merely because an OTP or familiar device appears in the log. Examine the actual allegation and transaction evidence.

For a business-card case, verify the claimant's role and company/cardholder relationships, permitted provisional treatment, employee-data access and contract. A disputed purchase should not automatically wipe out unrelated obligations or freeze every company payment. Closure requires the explained decision, customer notice, journal reconciliation and documented remaining recovery work.

Separate customer protection from merchant recovery

The customer reports what they experienced: an unknown transaction, a duplicated charge, cash not received, merchandise not delivered, or a cancelled subscription still billed. Intake captures that allegation without prematurely deciding which legal or scheme category applies. Verify the relevant account/product, transaction references, amount, dates, merchant description and customer authority. Explain the next step and applicable expectations in plain language. Preserve a reporting timestamp even when the first contact used a branch or an assisted channel.

Investigators obtain authorisation and clearing records, authentication evidence, device/channel information where permitted, merchant/acquirer responses and other relevant evidence. An authenticated event is evidence, not automatic proof that the customer lawfully authorised every disputed economic outcome. Merchant-service disputes and unauthorised transfers can have different rights, evidence and processing paths. Likewise, an authorised scam payment is distinct from an unauthorised instruction; apply the actual local protection rules rather than assigning both the same fraud reason code.

A fictional debit customer disputes 300. If a provisional credit is required or permitted, preserve a separate provisional-credit event with its authority, dates, notices and accounting policy. It does not prove that the merchant reimbursed the bank. Track the customer-credit position separately from the scheme claim and recovery position. Finance determines whether the corresponding bank-side entry is an appropriate receivable, expense or another approved account; a contingent possible recovery is not automatically a collectible asset.

Suppose a merchant later refunds that same 300 while the provisional credit remains. Link the refund, disputed clearing and provisional event before making a further customer adjustment. The customer must not lose an unrelated refund, and the bank must not collect twice. Where applicable rules allow withdrawal of provisional credit after a finding, follow the required notice and account-handling conditions. A case decision must explain the customer outcome and its evidence; a successful chargeback alone does not close every related complaint.

Operate scheme submissions as versioned cases: reason, permitted window, required evidence, submission acknowledgement, representment, escalation and final outcome. The issuer, acquirer and merchant have distinct responsibilities. Scheme deadlines, legal investigation clocks and bank service targets run in separate calendars. Do not reset a legal clock when a case changes queue, is reassigned or requires more internal review. Keep business-account disputes separate from automatic assumptions about consumer protections.

Close only after the customer receives the required decision, ledger adjustments reconcile, recovery positions are resolved or owned, and any recurring root cause has a remediation owner. Report gross disputed amount, credits, realised recoveries and losses distinctly. Test a merchant refund arriving first, a partial refund, disputed FX and fees, an expired scheme window with a continuing legal duty, and repeated customer contact through different channels.