Braintree Pre-Arbitration: When a Won Chargeback Comes Back

Recover the complete earlier case

Pull the original chargeback notice, merchant response, every exhibit, submission timestamp, and the prior outcome. The pre-arbitration reviewer should know exactly what the merchant already represented, not what the team wishes it had submitted.

Keep the earlier narrative unchanged in the archive. Editing the old file to improve wording destroys the audit trail and makes it harder to detect contradictions with the new response.

Read what is new in pre-arbitration

Identify the issuer's new statement, new evidence, or reason the earlier response was not accepted. Write the new proposition in one sentence. If the case does not expose enough detail, use Braintree support or the acquiring channel rather than guessing.

A useful question is: what fact must now be proven that the first packet did not establish? That becomes the scope for additional evidence.

Do not change the transaction story

Reconcile all new material against the original dates, amounts, cancellation/refund events, and fulfillment facts. If the merchant's position changes because new internal evidence was discovered, document why it was missing before.

Avoid introducing a second explanation that conflicts with the first simply because it sounds stronger. Consistency matters more at a later dispute stage because the previous packet is already part of the case history.

Add evidence only when it closes a real gap

New evidence may include a fuller carrier trace, refund completion record, account-usage export, purchase-time terms, or customer message that directly answers the new issue. Label what each addition changes relative to the first response.

Do not repackage the same screenshots with more annotations and call them new evidence. If the first packet lacked transaction-level proof, focus on obtaining that proof or reassessing whether the case should proceed.

Recalculate the economics before continuing

Later dispute stages consume more staff time and may involve additional risk or cost depending on the acquiring arrangement. Compare disputed amount, expected recovery, internal handling cost, and strength of the new record before choosing the available action.

The article cannot determine a universal break-even point. Use the fees, case options, and consequences shown by Braintree/acquirer for the live merchant account.

Prepare a delta-based response

A clear pre-arbitration file can begin with a short summary of the prior response, then a section titled by the new issuer point, followed by the new or clarified evidence. This keeps the reviewer focused on what changed.

Reference prior exhibits consistently if the platform permits. Avoid rewriting the whole original case unless the new stage explicitly requires a full resubmission.

Audit why the first response did not end the case

After closure, categorize the reason: missing evidence, ambiguous narrative, issuer counter-evidence, procedural issue, weak original facts, or a dispute type that the merchant should not have contested. This is more useful than recording only win/loss.

Feed the lesson back into first-stage intake. A repeated pre-arbitration pattern usually means the initial packet is failing to answer a predictable second question.

Example: pre-arbitration raises one new contradiction

The merchant's first Braintree packet showed delivery, but pre-arbitration includes a customer message saying the package arrived empty. Re-uploading the original tracking evidence does not answer the new fact.

The second-stage review should focus on packing/weight, warehouse records, customer complaint, replacement/refund, and any carrier investigation. The response should explain what is new relative to the first packet.

Respond to pre-arbitration by analyzing the delta from the earlier case

Pre-arbitration should begin with the complete earlier record. Recover the original dispute notice, merchant submission, exhibits, issuer or processor outcome, and internal notes. Then place the new pre-arbitration material beside it and identify what changed. A new cardholder statement, contradiction, amount issue, or rule argument is the delta. Rewriting the whole transaction story from scratch can create inconsistencies with evidence the merchant already submitted.

Create a delta table with three columns: new assertion, prior merchant evidence, and new evidence or explanation required. If the new assertion is already answered by the original packet, cite the existing exhibit accurately rather than generating a second version. If it exposes a real gap, add only the record that closes that gap. If it reveals that the merchant's first position was wrong, reconsider the economics and escalation rather than doubling down on a weak case.

Recalculate expected value at this stage. Pre-arbitration can involve more time, potential fees, and procedural risk than the first response. The disputed amount, margin, evidence strength, and processor options should be reviewed again. The fact that the merchant previously won or invested staff time does not justify continuing automatically. Use current Braintree, network, and acquirer guidance for the live procedural choices.

After closure, audit why the first resolution did not stick. Was decisive evidence missing, was the narrative ambiguous, did a new fact emerge, or was the case simply contested again despite a strong record? Tag the cause. If similar pre-arbitrations repeatedly expose the same gap—refund timing, address changes, missing service logs—change the first-response evidence standard so the business learns from escalation rather than treating it as random rework.

Freeze the original narrative so pre-arbitration does not create version drift

Store the exact first-response narrative as immutable text. At pre-arbitration, write a separate addendum addressing only new facts. Do not edit the old narrative in place, because staff may unintentionally change dates or explanations and lose track of what the issuer previously saw.

Use a version comparison during review. If a new statement contradicts the original, resolve the contradiction with source records before submitting. Consistency across stages is an evidence-quality control in its own right.

Identify whether the new pre-arbitration evidence was available during the first response

When a new fact appears at pre-arbitration, ask whether the merchant already possessed it but failed to include it, whether the customer introduced it later, or whether it was generated only after the first decision. These categories matter for process improvement. Missing an available decisive record points to first-response QA; genuinely new information may be unavoidable. Store the classification so pre-arbitration review improves the initial evidence standard instead of merely adding more attachments at the second stage.

Pre-arbitration should trigger a deliberate comparison with the first case, not a second copy of it. Put the original allegation, original response, decision, new allegation or evidence, and newly available merchant records side by side. Identify what materially changed and whether the merchant can answer that change with evidence that existed at the relevant time. If nothing new exists, repeating the first packet with more screenshots may add volume without improving the answer. Also check whether a refund, return, replacement, or customer contact occurred after the first decision; those later events can change the economic state of the case. This delta-based review keeps the response focused and makes it easier to decide whether further contesting is operationally justified.