On this page

Network escalation

  1. Rule issue is raised A client alleges a network-rule violation and a direct financial loss.
  2. Pre-compliance The filing client gives the opposing party an opportunity to resolve it.
  3. Accept or respond The receiving party uses the processor or network case process to accept, reject, or provide documentation.
  4. Compliance review If unresolved and valid, the case may escalate for a network decision under that scheme's rules.
Pre-compliance is a chance to resolve a rule issue before a formal compliance review.

How it differs from an ordinary chargeback

Case typeCore questionMerchant action
Ordinary chargebackDoes the cardholder's claim fit the dispute reason and can the merchant challenge it?Submit reason-matched evidence through the processor before the case deadline.
Pre-complianceDid a client violate network rules and cause a direct financial loss outside ordinary dispute rights?Read the scheme-specific case, gather rule-focused records, and respond through the acquirer if the case permits it.
ComplianceShould the network assign responsibility for the rule violation?Follow the acquirer/network escalation process; a normal packet builder is not a substitute for the case filing.

Visa and Mastercard are not interchangeable here

Visa

Visa describes compliance as an option for certain Visa Core Rules violations where ordinary dispute or pre-arbitration rights do not apply and a direct financial loss exists.

Mastercard

Mastercard's guide describes pre-compliance case filings, response options, timeframes, and distinct MATCH-related compliance cases.

Stripe

Stripe documents Visa and Mastercard compliance disputes as separate from ordinary disputes and says the API is used for some compliance responses.

Read the notice before assembling anything

Case facts to save

  • Network and processor or acquirer
  • Whether the notice says pre-compliance, compliance, pre-arbitration, or chargeback
  • Rule or condition alleged and the direct financial loss claimed
  • Case identifier, filing date, response deadline, and escalation date
  • Documents the filing client supplied
  • The exact response option the portal or acquirer offers

What a useful response should contain

  1. 01
    Identify the alleged rule violation

    Answer the rule claim, not only the underlying customer complaint.

  2. 02
    Show the transaction and responsibility chain

    Use processor references, dates, amounts, authorization or fulfillment records, and the parties involved.

  3. 03
    Address the claimed loss

    Connect the documents to the direct financial impact instead of attaching a general chargeback packet.

  4. 04
    Use the instructed channel

    Ask the processor or acquirer where the response belongs and preserve the submission confirmation.

For a second review after an ordinary dispute, see pre-arbitration chargeback. For a normal merchant evidence response, use how to respond to a chargeback.