How to appeal a reserve increase in 48 hours

A reserve increase notification is an acquirer risk decision, not a policy. That means it's appealable — but only if you move within the window and present the case the way their risk team reads cases. Most operators lose the appeal because they send an emotional email instead of a quantitative package. Here's the 48-hour procedure that actually works.

1. Hour zero: read the notification verbatim

The notification is not boilerplate. It tells you which metric triggered the change — chargeback ratio, dispute velocity, refund rate, first-party fraud signal, or volume swing. That's the metric your appeal has to address. If the letter cites a 1.2% chargeback ratio trailing 60 days, your appeal needs chargeback data for the same window.

2. Hour 1-4: pull the data they're looking at

Download raw dispute data, chargeback reason codes, and refund logs for the same window cited in the notification. Do not trust the processor's aggregate metric — run your own number. We routinely see aggregate ratios miscounted because partial refunds got coded as disputes, or because a dispute cycle was double-counted across reversed/final states.

3. Hour 4-8: segment the disputes

Cluster disputes by reason code (fraud, product not received, product not as described, subscription cancel dispute, authorization issue). Each cluster has a distinct remediation story. A chargeback ratio driven 80% by subscription cancel disputes is fixable with dunning policy; a ratio driven 80% by fraud is fixable with step-up auth. The appeal needs to show you know which is which.

4. Hour 8-16: build the remediation plan

For each reason-code cluster, write one paragraph: what you've already changed, what you're changing in the next 30 days, and the measurable metric that proves the change works. Example: "Subscription cancel disputes reduced from 38 to 11 in the last 14 days after moving cancellation CTA above the fold on the account page. Measurement: dispute count per 1,000 active subscribers, target <8 by day 60."

5. Hour 16-24: pull the positive offset signals

Reserve decisions weigh the negatives heavier than the positives by default. You have to present the offsets: approval rate trend, return customer percentage, average order value, 3DS authentication coverage, PCI attestation, any fraud tool deployment (Radar, Signifyd, Kount). Numbers only. No adjectives.

6. Hour 24-32: draft the appeal document

Structure: one-page cover letter, one-page executive summary of the data, 2-3 pages of reason-code data, one page of remediation plan with timelines, one page of offset metrics, appendix of raw CSV. The total package is 8-12 pages. Anything shorter looks unprepared; anything longer doesn't get read.

7. Hour 32-36: route to the right contact

Do not reply to the automated notification email. Identify your account manager or relationship manager (or the underwriting contact if you're direct with the acquirer) and send the package directly with a subject line that references the reserve decision number and your merchant ID.

8. Hour 36-40: schedule a verbal review

Written appeal + a request for a 15-minute call with the risk analyst. The call is where the decision actually gets made. Prepare three questions to ask: what specific threshold is your appeal solving for, what data cadence they want to see during the review period, and what reserve level they'd consider as a post-appeal compromise.

9. Hour 40-48: follow-up cadence

If no response by hour 40, send a one-paragraph follow-up with a new data point — most recent 7-day chargeback trend if favorable, or a specific fraud tool installation confirmation. Give them a reason to reopen the file, not a reason to close it.

10. What to do if the appeal fails

Failed appeals sometimes still move the number. A 15% reserve request can come down to 10% even on a "denied" appeal if your data package is strong. You have the right to ask for the reserve to be reviewed at 90 days with specific metric targets — get that review commitment in writing. See reserve math.

11. Structural alternative: move the book

If the reserve is large enough that appeal won't make it workable, the real decision is whether to move processing to a different acquirer. This is the switching playbook. Moving volume often drops reserve faster than appealing.

12. What multi-brand operators do differently

Multi-brand operators on parent-account structures appeal differently — the reserve decision applies to the parent, but the remediation data is per-brand. The appeal package needs to show which brand drove the ratio and what's changing at that brand specifically. Parent-account operators also have the option of isolating a problem brand to a separate MID rather than shouldering portfolio-wide reserve. See multi-brand playbook and our processor comparisons.

Appeal package checklist

• Cover letter with merchant ID, decision number, appeal date
• Executive summary (1 page): ratio, target, 30-day trajectory
• Reason-code breakdown for the cited window
• Remediation plan with measurable targets
• Offset metrics (approval rate, 3DS coverage, PCI status, fraud tools)
• Raw dispute CSV as appendix
• Named contact and verbal review request

Next steps

If you're facing a reserve increase right now, the 48-hour window is already running. Start with the data pull. If you're operating 5+ brands and your reserve is eating enough working capital to threaten operations, look at pricing or submit an application.