Chargeback Pre-Compliance: What It Is and How to Respond

What Triggers a Pre-Compliance Request

Pre-compliance requests are triggered by violations of card network operating rules. Common triggers include: processing transactions after an authorization has been declined or expired, failing to properly identify the type of transaction being processed (for example, not applying the correct merchant category code), using incorrect transaction data in submissions, exceeding allowed timeframes for processing or settling transactions, and failing to comply with data security standards (PCI DSS violations).

Pre-compliance is different from a chargeback because it is a network-level compliance action rather than a consumer dispute. A single consumer dispute is a chargeback; a compliance failure on how you process or handle transactions is a pre-compliance matter. The distinction is important because the resolution path is also different — you're not disputing a customer's claim, you're demonstrating that you've corrected a processing practice.

Both Visa and Mastercard have pre-compliance processes, though they use slightly different terminology. Visa's pre-compliance process operates under the Visa Operating Regulations. Mastercard uses a similar framework.

The Pre-Compliance Response Process

When you receive a pre-compliance notice, you typically have 30 days to respond. Your response must acknowledge the compliance issue identified, document the corrective actions you've taken (or plan to take), and provide evidence that the violation was isolated or has been resolved.

The response format for pre-compliance is more structured than a chargeback representment. You're not arguing that you didn't violate the rule — in most cases, the violation is documented. You're demonstrating that: the violation was inadvertent, you've taken corrective action, and you've implemented measures to prevent recurrence.

Work with your acquiring bank when responding to pre-compliance notices. Your acquirer is the primary interface between your business and the card network, and they receive the pre-compliance notice on your behalf. They may be able to advise on the correct response format and can submit your response to the network. Bypassing your acquirer in compliance matters is generally not an option.

Financial Consequences of Non-Compliance

Pre-compliance is called "pre" compliance because it precedes a formal compliance case. If you do not respond to a pre-compliance notice, or if your response is insufficient, the matter escalates to a compliance case. Compliance cases come with financial penalties.

Visa and Mastercard can impose compliance fees of $5,000 to $100,000+ depending on the nature and severity of the violation. Repeated violations or failure to respond can result in even higher penalties. In extreme cases, processors who experience systematic non-compliance can lose their ability to accept certain card types.

This financial exposure makes prompt and substantive pre-compliance responses essential. The cost of responding correctly (some internal legal or compliance time) is almost always far less than the cost of a formal compliance case.

Common Pre-Compliance Scenarios

Authorization expiry violations: in some jurisdictions and networks, authorizations expire after a set period (7 days for Visa in many regions). Processing a transaction against an expired authorization can trigger a pre-compliance. The fix: ensure your authorization and settlement timing are within network rules, and re-authorize before processing if there is a delay.

Transaction misclassification: using the wrong merchant category code (MCC) or failing to properly identify transaction types (for example, marking a cash advance as a purchase) can trigger compliance action. The fix: verify your MCC with your acquirer and ensure it accurately reflects your primary business activity.

Excessive chargebacks leading to compliance monitoring: if your chargeback rate exceeds Visa or Mastercard monitoring program thresholds (VAMP, HMCP), you may receive compliance notices alongside program enrollment. This is a chargeback-rate compliance issue rather than a processing compliance issue.

PCI DSS non-compliance: failing to maintain PCI DSS certification or reporting a data breach while non-compliant triggers compliance action. This is one of the most serious pre-compliance scenarios.

Preventing Future Pre-Compliance Issues

Most pre-compliance issues can be prevented through systematic attention to card network operating rules and your processing practices.

Conduct a periodic review of your processing configurations with your acquirer to ensure your transaction types, MCC, and settlement practices are correct. Card network rules change annually, and a practice that was compliant last year may require adjustment.

Maintain your PCI DSS compliance certification without lapse. Your acquirer typically manages the annual assessment process, but ensuring this is tracked and completed is your responsibility.

For chargeback-rate compliance issues, proactive dispute management is the best prevention. Keeping your chargeback rate below 0.9% (Visa's threshold for most programs) keeps you out of monitoring program compliance actions.

For merchants who receive a pre-compliance notice and need assistance understanding the issue or drafting a response, ChargeMate can provide guidance on the compliance aspects of chargeback-related pre-compliance matters.