Pre-Chargeback: How to Resolve the Dispute Before It Turns Into a Chargeback

What is a pre-chargeback?

A pre-chargeback is an alert issued by the banking system before a chargeback becomes formal. When the buyer contacts the bank to dispute a charge, that dispute does not become a reversal right away. Before that, the system triggers a warning, and that warning is what we call a pre-chargeback.

The difference in stage changes everything. In a chargeback, the reversal has already happened: the amount has gone back to the buyer without passing through the seller. In a pre-chargeback, the dispute is still open, and both the seller and the gateway can act to close it before it becomes final.

At Mundpay, each pre-chargeback alert costs R$ 80.00, and approximately 90% of them are resolved before turning into a formal chargeback. In other words, in the vast majority of cases, the dispute never reaches the expensive stage. The alert is, in practice, a second chance the banking system offers.

Why is it your best window?

Once the chargeback is formalized, your options shrink. The money has already left, the operation has already recorded the reversal, and you enter a dispute process that rarely turns in the seller's favor for digital products. The pre-chargeback exists precisely in the moment before that, when there is still something you can do.

Three things make this window valuable:

• The value has not come back yet. Resolving the alert in time can avoid the return of the gross amount that a formal chargeback requires.
• The rate has not been touched yet. It is the consolidated chargeback that feeds the 0,90% limit tolerated by acquirers. Closing the dispute before that keeps this percentage intact.
• The relationship with the customer still exists. Many disputes come from a simple non-recognition on the statement. At this stage, a contact resolves what would later become a loss.

That is why treating the pre-chargeback as a routine task, not a scare, is what separates those who control their dispute rate from those who just live with it. The window is short, but it is the cheapest one you are going to get.

How do you resolve a pre-chargeback within the deadline?

When the alert arrives, the clock starts running. There are two main paths, and the choice depends on the nature of the disputed sale:

• Refund. This is the fastest and most definitive path. By returning the value of the disputed sale, you close the dispute before it turns into a chargeback. It makes sense when the buyer clearly wants their money back or when the cost of disputing exceeds the value of the sale.
• Contact with the buyer. When the purchase is legitimate, it is worth clarifying the charge directly with the customer. A good part of disputes start because the person did not recognize the name that appeared on the invoice. A well-handled contact makes the buyer cancel the dispute on their own, and you keep the sale.

The right decision comes from looking at the sale: ticket, customer history, and fraud signals. A low-value purchase with no clear defense calls for an immediate refund. A legitimate sale, with an identifiable customer, calls for contact before any refund. The common mistake is ignoring the alert and letting it expire, because then the dispute follows its course and turns into the chargeback you wanted to avoid. For international operations, this reasoning connects to the guide to chargeback prevention in international sales, which addresses the dispute from the source.

What role does the proactive risk team play?

Resolving alerts one by one, in a panic, does not scale. This is where the difference of having a risk team that acts before, not after, comes in. At Mundpay, the risk team contacts the seller before any restriction, instead of blocking the account without warning the way platforms that treat risk only as defense do.

In the context of the pre-chargeback, this means the seller is not alone in the resolution window. The team works alongside them, helping identify which alerts call for a refund, which call for contact, and which point to a fraud pattern that needs to be cut off at the source. This joint work is what sustains the number that matters: around 90% of alerts resolved before turning into a formal chargeback.

A proactive risk team also sees what an isolated dispute hides. If the same product or the same traffic source starts generating alerts in a row, the problem is not the alert, it is the operation behind it. Anticipating that reading prevents the dispute rate from rising to the point of threatening the account. This is the same principle behind the Mundpay proactive risk team and antifraud for international digital products.

Pre-Chargeback vs Chargeback: Cost and Effect

At first glance, the pre-chargeback looks more expensive: R$ 80.00 per alert against a fixed R$ 60.00 for the chargeback. But comparing just the cost of the alert ignores what each stage really charges you. Look at the two side by side:

• Formal chargeback: a fixed R$ 60.00 plus the return of the gross sale amount plus a point on the 0,90% chargeback rate tolerated by acquirers. The real damage is the sum of the three, not just the fee.
• Resolved pre-chargeback: R$ 80.00 for the alert, and the dispute closes right there. When resolved in time, it avoids the return of the gross amount and does not pressure the chargeback rate.

The math changes shape on mid- to high-ticket sales. If the gross value of the sale is R$ 300, the R$ 80.00 alert preserves that R$ 300 and still protects the account's percentage. The chargeback, in the same case, would cost the fixed R$ 60.00 plus the R$ 300 returned, on top of the impact on the rate. The more expensive alert is, in the end, the cheaper option. Full figures are on the payments and fees page.

How do you keep a pre-chargeback from turning into a chargeback?

Resolving within the deadline is the remedy, but the best operation is the one that generates fewer alerts to handle. A few habits reduce both the volume and the conversion rate of alerts into reversals:

• Clear invoice descriptor. A good part of disputes come from the customer not recognizing the name on the statement. An identifiable descriptor kills non-recognition at the root.
• Quick response to the alert. The pre-chargeback has a deadline. Handling each alert as soon as it arrives, not at the end of the week, is what guarantees the window does not expire.
• Accessible support. A buyer who can reach you disputes less with the bank. A visible support channel reduces disputes before the alert is even born.
• Reading patterns. Alerts in a row on the same product or traffic are a symptom, not chance. Cutting off the source prevents the next dozen disputes.

None of these habits is sophisticated, and that is why they work. The pre-chargeback already gives you the time; what is left is to use it with method instead of letting the alert turn into the reversal you could have avoided.