A Practical Guide to Acquirer Chargeback Management

For acquirers, chargebacks are not just a compliance obligation. They are a direct financial exposure that sits on the acquirer's balance sheet when merchants cannot cover disputed amounts. This guide walks through how acquirer-side chargeback management actually works: the responsibilities that come with the role, how to build a dispute workflow around scheme deadlines, how to keep merchant portfolios below monitoring program thresholds, and how to decide which liability model fits your operation.

What acquirers are actually responsible for in the chargeback process

Acquirer dispute management starts where most payment guides stop: with the party that absorbs the loss. When a cardholder successfully files a chargeback, and the issuing bank reverses the funds, the acquirer is the one liable if the merchant cannot cover it.

Where acquirers differ from issuers and processors is that the acquirer holds direct financial liability for its merchants. They are not simply a technical step in the transaction process.

The practical consequence is that the acquirer owns the dispute workflow end-to-end. Specific responsibilities include:

Chargeback reason codes and why they determine your strategy

Reason codes categorise the types of chargebacks filed against merchants. Each carries its own evidence requirements, dispute windows, and liability logic. Treating every chargeback the same, regardless of code, produces a chargeback dispute management strategy that wins cases it should lose and abandons cases it could win.

The table below maps each category to what triggers it, what evidence is typically required to contest it, and how liability is distributed.

The fraud row deserves particular attention for acquirers evaluating their technical stack. DECTA's acquirer processing includes full 3D Secure v2 compliance and PSD2/SCA support, which means fraud chargebacks on transactions authenticated through the platform carry the liability shift to the issuer by default. For acquirers whose merchants process significant card-not-present volume, this is one of the more direct ways the choice of processor affects acquirer dispute resolution outcomes rather than just dispute routing.

Building the dispute workflow: stages and timelines

The chargeback lifecycle moves through defined stages, each with a scheme-mandated deadline. Missing one is not a procedural inconvenience. It forfeits the acquirer's right to contest the dispute, regardless of how strong the underlying case might be. Scheme rules do not distinguish between an acquirer that had no evidence and one that had strong evidence but filed a day late.

Scheme-mandated deadlines and SLA ownership

Both Mastercard and Visa impose strict timeframes at every stage of the chargeback cycle. The window to submit a representment after receiving a chargeback notification is finite, typically measured in calendar days from receipt. Pre-arbitration and arbitration stages carry their own deadlines on top of that, often shorter than the initial window.

Surviving this process reliably requires that internal SLA ownership is mapped before disputes arrive, not improvised when they do. Each stage needs a named owner and a defined turnaround: initial triage, merchant notification, evidence request and receipt, representment preparation, and submission. Any gap in that chain creates a delay that compounds against the scheme clock.

Representment: when and how to fight a chargeback

Representment is the acquirer's formal submission of evidence to challenge a chargeback on the merchant's behalf. The decision of whether to submit one comes down to a straightforward question: does the available evidence match what the specific reason code requires?

Filing representments on cases where the evidence does not fit the reason code drains operational capacity and gradually signals to scheme monitoring systems that the acquirer's chargeback handling quality is low. Evidence requirements vary by reason code category. Consumer dispute codes typically require delivery confirmation, proof of cardholder interaction, or documentation that the merchant's refund policy was disclosed at checkout. Fraud codes require authentication data, device fingerprinting, or IP records that demonstrate the legitimate cardholder initiated the transaction. Processing error codes are resolved through transaction records showing the correct amount was billed and settled.

Assembling the right evidence package for the right code is the core competency of an effective in-house dispute team.

Pre-arbitration and arbitration decisions

When an acquirer submits a representment and the issuer disagrees, the case escalates to pre-arbitration. This is the issuer's formal notice that they intend to pursue the dispute further, and the acquirer must then decide whether to accept the loss or escalate to full arbitration at the scheme level.

Arbitration is expensive. Both Visa and Mastercard charge filing fees, and the losing party faces additional penalties on top of the original disputed amount. The acquirer that arrives at this decision point without a prepared framework, one that weights case value, estimated win probability by reason code, and fee exposure, tends to make inconsistent calls under time pressure. That framework should exist before the first pre-arbitration notice arrives, not be constructed in response to one.

Merchant monitoring and chargeback ratio management

Card schemes hold acquirers accountable for the aggregate chargeback performance of their entire merchant portfolio. An individual merchant running high dispute rates does not just expose itself. It moves the acquirer's portfolio-level ratios toward scheme monitoring thresholds, and one high-volume merchant can be enough to trigger a formal scheme program even if the rest of the portfolio is clean.

Effective managing chargebacks as an acquirer therefore requires tracking chargeback-to-transaction ratios and fraud-to-sales ratios at the individual merchant level, frequently enough to catch deterioration before it compounds. Monthly reporting is generally too slow. By the time a problem appears in a monthly summary, the ratio may already be at a threshold that draws scheme attention.

Visa Acquirer Monitoring Program and Mastercard Excessive Chargeback Program

Visa's Acquirer Monitoring Program (VAMP) and Mastercard's Excessive Chargeback Program are the enforcement mechanisms schemes use when an acquirer's portfolio ratios breach defined limits. Both programs impose fines and require a formal remediation plan. What is less commonly understood is that they operate on different metrics and different escalation timelines, which means a single monitoring approach cannot satisfy both simultaneously.

When a remediation plan is required, schemes expect documented evidence of merchant-level controls: what thresholds were in place, what action was taken when a merchant breached them, and what the outcome was. Acquirers without granular per-merchant dispute data find themselves unable to produce this documentation on the timeline schemes demand, extending the remediation period and increasing cumulative fine exposure.

Best practices for reducing merchant chargeback ratios

Reducing merchant chargeback ratios requires controls at two levels: pre-emptive measures that reduce the number of disputes initiated, and reactive measures that catch deterioration early before it reaches scheme thresholds.

On the pre-emptive side, mandating 3D Secure on eligible transactions is the most direct lever available, since authenticated transactions shift fraud liability away entirely. Standardising merchant descriptor formats reduces the volume of consumer disputes that arise simply because cardholders do not recognise a transaction on their statement. Requiring merchants to display refund and cancellation policies at checkout addresses the subset of consumer disputes that stem from unmet expectations rather than actual fraud.

Reactive controls operate at the monitoring layer. Per-merchant chargeback threshold alerts, set below scheme limits to allow time to intervene, let the acquirer act before a problem becomes a scheme notification. Contractual chargeback liability clauses in merchant agreements create a documented basis for recovering losses and give the acquirer a mechanism to pressure non-compliant merchants into corrective action. Suspension protocols for merchants consistently approaching scheme limits protect the rest of the portfolio from collateral exposure.

For acquirers using DECTA's processing platform, the fraud management layer includes a rule editor, case management tooling, and external lists, which can be configured to flag per-merchant patterns before they compound into scheme-level exposure.

Chargeback liability models: holding the risk versus transferring it

Acquirers have more than one option for how they carry chargeback financial exposure. The right model depends on portfolio size, dispute mix, and internal operational capacity.

Full in-house retention

The default model is full in-house retention: losses from chargebacks that cannot be recovered from the merchant are absorbed against merchant security deposits or reserves, with the acquirer's own capital covering any shortfall. This gives maximum control over the acquirer chargeback process and keeps all representment decisions internal. The tradeoff is that financial risk concentrates entirely within the acquirer's balance sheet, and operational costs scale directly with dispute volume.

Chargeback insurance

Chargeback insurance products transfer a portion of the financial exposure to a specialist insurer. Coverage typically applies to confirmed fraud chargebacks on transactions that passed defined authentication thresholds, including 3D Secure-authenticated transactions.

What these policies do not cover matters equally. Friendly fraud (where a cardholder disputes a legitimate purchase they made), merchant error disputes, and chargebacks arising from processing failures generally fall outside standard policy scope. The coverage perimeter needs to be mapped carefully against the acquirer's actual dispute mix before a policy is purchased. An insurer covering only authenticated fraud chargebacks provides limited value to an acquirer whose dispute volume is driven primarily by consumer complaints.

Managed service providers

Managed service providers offer a different kind of transfer. Rather than insuring against financial loss, they take over the operational dispute management for acquirers: representment preparation, evidence assembly, submission, and monitoring. This reduces the acquirer's internal headcount requirement. The tradeoff is dependency on a third party's evidence standards, SLA performance, and familiarity with the acquirer's specific merchant categories. A managed provider optimised for ecommerce disputes may perform poorly on travel or subscription billing chargebacks.

Many acquirers land on a hybrid model. Routine disputes are handled in-house, where the process is well understood and the per-case cost is manageable. High-volume or structurally complex categories, such as friendly fraud or card-not-present fraud at scale, are routed to specialist providers better equipped to handle them efficiently. The boundary between in-house and outsourced handling is a deliberate design decision, not a default.

How acquirer processing infrastructure affects dispute handling

The processing infrastructure an acquirer sits on shapes how chargebacks flow through the organisation, often in ways that only become visible under operational pressure. If a processing system lacks certain integrations or automation, the acquirer and their merchants may have to manually handle chargeback notifications and submissions to scheme systems. Against scheme-mandated deadlines, those manual steps accumulate into timeline risk quickly.

Chargeback management for card acquirers is easier to scale when scheme portal access is built into the processing layer from the start. DECTA's acquirer processing covers authorisation processing, clearing file handling, and chargeback processing as named capabilities, with direct Mastercom API and Visa ROL connectivity integrated into the platform. Acquirers building their acquirer dispute resolution workflow on DECTA's infrastructure work with scheme portal access already inside the processing layer, rather than maintaining separate connectivity to each scheme's dispute system. The practical effect is that dispute notifications and submissions move through a single, connected interface, reducing the operational overhead that tends to grow when scheme access is patched together from separate components.