What to do when pre-chargeback alerts arrive

An alert lands at 6:12 on a Friday evening. One order, $180, shipped Wednesday, tracking says out for delivery.

Your window is measured in hours, and most of those hours are the weekend.

What the alert is telling you, and what it is not

A pre-chargeback alert is not a risk score and it is not fraud monitoring. Nobody is predicting anything. A real cardholder has already called their issuing bank about a specific transaction, and the network is telling you before the chargeback is formally filed.

That makes it inbound, order-specific, and time-boxed. Vendor documentation generally quotes 24 to 72 hours depending on the network and the issuer's own configuration, with Ethoca at the shorter end and Verifi's CDRN at the longer. Confirm the exact window with your provider, because it varies and it is the one number you cannot afford to guess.

PayPal's version is a separate thing with separate rules. PayPal's own help page describes a pre-chargeback alert as "a type of case notification sent to merchants to help identify transactions possibly receiving a chargeback," and gives you "a 20-hour window to issue refunds for transactions without fulfilling orders and avoiding any applicable fees." Miss it and you still have ten days to respond, but you may no longer avoid the chargeback or its fee.

Do not run a PayPal alert through your network-alert playbook. The clocks are different.

The first ten minutes

Work in this order. It is short on purpose.

1. Match the alert to the order. Use the acquirer reference number or authorisation code where the alert carries one, and fall back to amount plus date plus the last four digits. Do not act on a partial match.
2. Check whether you already refunded it. A refund issued yesterday means you decline the alert rather than pay a fee to refund the same money twice. This is the single most common expensive mistake.
3. Stop fulfillment. If it has not picked, cancel it. If it is in the carrier's hands, request an intercept now rather than after you have decided about the refund. Recovering the goods changes the arithmetic.
4. Decide refund or decline. Covered below.
5. Respond inside the window with a final outcome, for the full amount. A partial refund usually does not resolve the alert, and a response left in an interim state can time out.
6. Write it down. Alert ID, order ID, outcome, timestamp, who acted. If the chargeback arrives anyway you will need that record, and it is the only way to tell later whether your alert program is working.

How to decide refund or decline

Refund when the dispute is going to succeed anyway or when the goods are still yours. Unshipped orders, cancelled subscriptions, forgotten rebills, deliveries already running late, and anything low enough in value that thirty minutes of evidence work costs more than the order.

Decline when you have delivery confirmation to an address that matched at authorisation, the order value justifies representment, and the reason on the alert looks like a customer who has forgotten rather than one who never received. Declining is a real option. Alert programs that treat every alert as an automatic refund are optimising for a deflection rate rather than for money.

At volume this becomes a rules problem, not a judgement problem. Refund automatically under a value threshold, hold anything above it for a human, and route by reason code. That is how pre-chargeback deflection works when we connect it to a Shopify store: the alert arrives, the rule decides, and the refund posts inside the window without waiting for Monday morning.

The honest part

Acting inside the window is not a guarantee. Alerts stop most of what they touch and not all of it, and if the issuer has already filed by the time you refund, you have paid the alert fee, refunded the order, and got the chargeback regardless.

Refunding on alerts means refunding some customers who would never have escalated. That cost is real and you cannot measure it, because you never find out which ones they were.

Coverage is partial. Alerts only reach you for networks you are enrolled in, and a dispute that goes straight to a chargeback never generates one.

The ratio benefit also deserves more caution than it usually gets. Vendor guidance disagrees on whether a fraud-coded dispute resolved through RDR or CDRN stays out of the VAMP numerator, and Forter's analysis adds a condition that the dispute and its resolution fall in the same calendar month. Ask your acquirer how they see your deflected disputes, because a dispute counts toward your ratio whether or not you win the representment, and deflection is only worth the fee if it genuinely keeps the dispute off the count.

The measurement to start this week

Record two timestamps on every alert: when it arrived and when you posted a final outcome. Then check how many of the last twenty you closed inside the window, and how many of those still turned into a chargeback.

If a meaningful share of your alerts are timing out overnight or over a weekend, your problem is not which vendor you use. It is that a human is standing between the alert and the refund.