Merchants should treat pre-arbitration as a formal chance to reestablish the facts, not as a casual extension of the original dispute. The first step is to review the new reason code, gather the evidence already used in chargeback, and confirm whether the issuer has introduced any new information. Strong records, clear policies, and chronological documentation improve the response.
What pre-arbitration changes for the merchant
Pre-arbitration is not just a second look, it is a narrower, more formal dispute checkpoint where the merchant needs to answer the issuer’s updated case, not simply repeat the original chargeback response. The practical shift is that the merchant should now validate whether the dispute still stands after any new issuer evidence, then decide quickly whether the claim is worth contesting further.
The first task is to compare the pre-arbitration notice against the earlier dispute packet. Look for a new reason code, a revised claim narrative, or a different transaction theory. If the issuer has only reasserted the same position, the merchant’s strongest move is usually to anchor the response in the original evidence set, especially any proof of authorization, delivery, service completion, or policy disclosure that was already assembled.
Strong pre-arbitration responses are built on chronology. That means the merchant should line up order intake, authentication or checkout events, shipment or fulfillment records, customer communications, refund history, and prior dispute correspondence in a single timeline. The more the evidence shows a consistent sequence, the easier it is to show that the issuer has not added a materially stronger argument.
Evidence that actually matters at this stage
Pre-arbitration is evidence-driven, but not every document helps equally. The most persuasive material is anything that ties the transaction to the buyer, shows what was disclosed at the point of sale, and proves what happened after purchase. That usually includes receipts, AVS or other checkout signals, tracking or delivery confirmation, login or session records where relevant, and policy terms that the customer agreed to before paying.
Merchants should also test whether their evidence is complete enough to survive a renewed review. If the original packet relied on screenshots without timestamps, unclear policy language, or disconnected system records, pre-arbitration exposes those gaps quickly. A compact but well-organized file often performs better than a larger bundle that is hard to follow.
For payment disputes, the cleanest response often comes from treating evidence as a chain of custody problem: can you show who acted, when they acted, what they were shown, and what happened next? If any link in that chain is missing, the merchant should assume the issuer will press that weakness.
Risk and Threat Considerations
Pre-arbitration raises the financial stakes because the dispute is now closer to a final loss, and weak case preparation can make a recoverable claim look unsupported. The main risk is procedural, merchants who respond with the same material used in the chargeback stage without checking for new issuer evidence or a changed reason code may miss the one point that actually decides the case.
Failure mechanism: The issuer introduces a revised narrative, while the merchant reuses an outdated packet, omits the new allegation, or cannot show a coherent transaction timeline. That creates an evidence gap that is hard to repair later, especially when records are scattered across checkout, fulfillment, support, and finance systems.
Impact: The merchant can lose the dispute even when the underlying transaction was defensible, and repeated weak responses also consume time, fees, and analyst attention that could be focused on preventing the same dispute pattern from recurring.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS 8 — Audit Log Management | Chronological evidence and dispute tracing depend on reliable logs and records. |
| CIS 3 — Data Protection | Dispute packets often include customer and payment records that need controlled handling. | |
| Recommendation — Retain transaction and dispute logs with timestamps to support evidence-based chargeback responses. Protect dispute evidence and customer records with access controls and secure retention. | ||
| NIST CSF 2.0 | PR.AA — Asset Identification, Management, and Control | Merchants need controlled, traceable records to reconstruct the transaction timeline. |
| RS.CO — Communications | Pre-arbitration depends on responding precisely to the issuer’s updated claim and evidence. | |
| Recommendation — Maintain complete transaction and dispute records so evidence can be quickly assembled and verified. Coordinate a clear response that directly addresses the issuer’s revised dispute narrative. | ||
Practitioner Guidance
What to verify: Check the new pre-arbitration reason code against the original chargeback reason and confirm whether the issuer has added fresh facts, not just a restated complaint. If there is no meaningful new allegation, do not overbuild the response, focus on the clearest proof points that directly answer the issuer’s claim.
What to prioritise: Build the response around the few records that establish the transaction story end to end, then remove anything that is redundant, hard to interpret, or not date-aligned. A strong chronology usually matters more than volume, especially when the merchant needs to show consistency across systems.
Practitioner takeaway: The first decision in pre-arbitration is whether the dispute has genuinely changed, because the best merchant response is the one that directly answers the new allegation with the smallest set of well-timed, well-supported facts.
Related resources from NHI Mgmt Group
- What do merchants get wrong about chargeback automation?
- How should merchants connect fraud signals to chargeback handling?
- What breaks when chargeback handling treats first-party fraud as a one-off payment issue?
- Who is accountable when first-party fraud escalates across payments, identity, and customer support?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
