Chargeback pre-arbitration: review the next decision

How do representment, pre-arbitration, and arbitration differ?

Representment is the merchant-side challenge to a chargeback through the acquiring provider. Pre-arbitration concerns a further review of disputed liability in supported flows. Scheme arbitration is a separate escalation where the card network determines liability under its process. They are not three interchangeable names for submitting evidence.

Adyen's general flow describes issuer-initiated pre-arbitration after a defense is declined, with merchant action subject to configuration and approval. Its Visa allocation flow describes pre-arbitration being created as part of the acquirer's defense route. The practical consequence is to verify who initiated the current stage and who can act, rather than infer that from the word “pre-arbitration.”

For a B2C SaaS renewal or a B2B SaaS workspace dispute, reopen the underlying payment investigation as well as the procedural notice. A further stage does not repair an unsupported statement in the original response.

Establish the case you are being asked to review

Start with the provider's current notice. Capture the payment identifier, original dispute identifier, any linked escalation identifier, network, reason, requesting party, and action required. Save the notice and the provider's instructions with their retrieval time.

Do not reuse an earlier deadline. Confirm the current deadline, timezone, responsible person, and permitted submission channel. Record an explicit “no merchant action requested” state when that is what the notice says; do not turn an empty deadline field into an invented date.

J.P. Morgan documents linked pre-arbitration records and populates a response due date when its team requests more information. API availability is limited by region and transaction type. A field or operation shown in one provider's documentation does not establish that the same operation exists in another SaaS merchant account.

Review the objection to the original defense

Compare the issuer's explanation with the exact response that was filed. Keep the submitted version intact. Work in a separate review note so a later reader can distinguish what the issuer actually saw from what your team knows now.

A new record matters only if it changes a relevant finding and the provider can use it. A longer description of the product or another month of unrelated logins does not necessarily address the reason the defense was rejected.

A subscription example where the position should change

Fictional case. A SaaS team defended a €96 renewal with an invoice and account activity. During the next review it finds an earlier support promise: the customer was told the subscription would end before that renewal. The original packet did not include the conversation.

Preserve the missing conversation and explain how it changes the finding. Do not rewrite the support promise as a generic cancellation request or present later product use as renewed consent. Have the case owner review the appropriate provider action, including accepting the valid complaint where supported.

For a company subscription, check whether the promise concerned the entire workspace, a seat reduction, or another subscription under the same billing contact. The scope of the promise matters just as much as its timestamp.

The accept-or-contest guide covers that factual decision. It remains necessary at a later stage; the work already spent defending a payment is not evidence that it should still be defended.

Compare additional exposure before escalation

Ask the acquiring provider to state which actions are available and what additional fees or liability each can create under your terms. Distinguish costs already incurred from the cost of the next action. Do not use a fixed arbitration fee from a general article as your account's price.

If further review is available, the approving person needs the disputed principal, relevant contrary facts, unresolved money movements, provider explanation, additional cost, and remaining uncertainty. Record why the team chose the action, not just which button it pressed.

A process outcome and a funds outcome need separate checks. A case marked reviewed or closed should not cause the team to assume that a balance entry is final or that a customer has received money. Use the cost and reconciliation guide to keep those records separate.

Preserve the handoff

Leave one review note that identifies the original packet, current stage, new information, provider contact or case channel, decision owner, action, and confirmation still needed. Include the rejected argument as well as the revised finding.

Evidenz is being built to bring payment, account, support, and product history together before a reviewed chargeback draft is prepared. In an escalation investigation, the intended benefit is the ability to understand why the earlier account of events needs to change. It does not establish access to a network arbitration process or permission to act on the merchant's behalf.

Can every lost chargeback be escalated?

No. The route depends on the payment flow, case stage, provider support, and applicable instructions. A lost status is not a general entitlement to another evidence upload. Confirm the available route with the provider before creating work for a channel that cannot accept it.