Black Friday 2026 falls on November 27, and Cyber Monday on November 30 — but the disputes on those orders are a December-to-March story, not a November one. This guide gives sellers and merchants the dated shape of that story: when the first wave arrives, why January is the dangerous month, when the filing window actually closes, and how to staff each phase. For your own numbers, run the companion BFCM Dispute Calendar planner: it turns your BFCM order count and your own prior dispute rate into the same calendar, sized to your store. This guide is the explanation; the planner is the arithmetic.
The shape of the wave
Sales, fraud attempts and chargebacks do not peak together. Sales peak on the BFCM weekend itself. Fraud attempts and card testing peak within days of the sales spike. Chargebacks peak 30 to 90 days after purchase, with a tail that runs to the 120-day filing edge — which is why Chargeflow calls the first quarter, not November, the real chargeback season. The reason is mechanical, not mysterious: cardholders file after their statement arrives, after a promised delivery date passes, or after a return goes unrefunded, so the dispute is created weeks after the order that caused it.
What the measured data actually shows — Chargeflow's Data Lab study of 58,783 disputes on Black Friday–Cyber Monday 2025 orders, reported as a secondary source here — is a December start, a January peak, and a first-quarter tail. In both measured seasons January filed the most disputes per day (1.40 times November's daily rate in one season, 1.41 times in the other). December and February also ran above November. Note what this does not say: it does not say your store's January will be 1.4 times your November, and it does not assign a share of your disputes to any month. It says where to put the staff: December for the first wave, January for the peak, and cover kept in place until the window closes.
The scale of the weekend behind the wave is worth stating with its publisher attached, because it explains why even a small rate produces a large caseload. Adobe Analytics forecast on September 28, 2026 that Cyber Week 2026 (November 26–30) would drive $47.5 billion in US online sales, up 7.4% year over year — a forecast, not a result, and a US-market figure, not any one store's. The same season sits inside a longer trend Mastercard's research with Datos Insights puts in numbers: global chargebacks forecast to grow 37% from 2025 to 2029, reaching 359 million transactions a year. Neither figure is your dispute count. Both are reasons to plan capacity before December rather than discover the wave in January.
The dated calendar
The fixed dates, for BFCM 2026 orders. Black Friday, November 27, 2026: orders placed. Cyber Monday, November 30, 2026: orders placed. December 2026: alerts and first dispute notices arrive, and late carrier scans surface — refund first through alerts where possible, because a refunded alert never becomes a formal chargeback with a fee. January 2027: the first full month in which November disputes are measured against low sales volume — check the VAMP ratio weekly, not monthly. March 27, 2027: the 120-day window closes for Black Friday orders. March 30, 2027: the same for Cyber Monday orders.
Two cautions belong on those March dates. First, 120 days is the general window for most dispute conditions, counted from the transaction processing date; some conditions run from the expected delivery date instead, and some run to a 540-day outer cap, so a pre-order or delayed-delivery case can outlive March. Second, the cardholder's filing window is not your response window: your processor's case notice sets a far shorter response deadline (Visa's network window is 30 days at the acquirer level, and processors commonly give merchants far less — Adyen documents 9 days for US and Canadian domestic Visa disputes). A case answered late is lost on timing, whatever its merits, so the calendar above is a staffing plan, not a reason to wait.
The VAMP-month trap
The trap is the single most expensive misunderstanding in BFCM planning, and it is pure denominator arithmetic. Visa VAMP counts a month's fraud reports plus disputes against that same month's settled card-not-present transactions. The merchant Excessive line in standard regions, in force from April 1, 2026, is a ratio at or above 1.5% together with at least 1,500 fraud reports plus disputes in the month. A dispute spike that arrives in January is therefore measured against January's settled volume — the quiet month — not against November's peak volume.
Chargeflow's worked example makes the shape concrete: a merchant settling 1,000,000 transactions in November and 350,000 in January, with 6,000 reports arriving in January, sits at 1.71% for January — above the line, with the count condition met — even though the same 6,000 reports would have been a footnote against November's volume. The lesson is not that 6,000 is your number; it is that November's volume gives no protection in January. Before January, run your own January settled volume through the VAMP Threshold Checker and the Merchant Monitoring Program Checker, and know which line you are near while there is still time to spend on prevention — alerts, refunds, screening — rather than discovering the line from a program notice.
Staffing December, January and March
Staff the wave in three phases, not one. In December, staff for speed: first alerts, first notices, and refund decisions made in hours, because a refund answered in hours is dispute prevention and a refund answered in days is a chargeback with a fee attached. Keep delivery evidence — tracking, carrier scans, proof of delivery — filed per order from the day of shipment, so a December "item not received" case is answered from a file, not assembled from memory. In January, staff for volume and for the ratio check: the peak filing month, the weekly VAMP check, and the reason-code read that tells you which cluster to fix (a spike in "not as described" points at a product page, a spike in fraud at a traffic source). In February and March, staff for the tail and the close: the window narrows, late cases still arrive, and the evidence files must stay in place until the March 27 and 30 edges pass.
One staffing mistake repeats every year: standing the response team down when sales fall. Sales fall in January; disputes do not. If the planner's even-spread weekly figure fits your team comfortably, remember it is an average across 18 weeks — real arrivals cluster in December and January, so peak-week cover needs to sit above the average. Price the season honestly while you are at it: Mastercard's research with Javelin (2026) puts the average US merchant cost at $128 per chargeback in fees plus internal handling ($46 third-party plus $82 internal), excluding the disputed sale itself — a published average for context, not your processor's fee, which is on your own statement.
The late-March close-out
When the March window edges pass, run the review that December's debrief cannot: the season's dispute-adjusted result. Compare fraud losses, chargeback ratio and win rate against your pre-season baseline; identify which product, page or traffic source produced the most disputes per sale; note which evidence pack won most often; and feed those answers into next year's pre-peak fixes. The site's Golden Quarter Dispute Prep checklist covers what to fix before peak — descriptors, refund speed, evidence templates, alert enrolment. This guide and its planner cover the dated aftermath. Together they are the whole season: reduce the disputes before peak, staff the ones that arrive anyway, and set next year's peak budget on real profit, not gross sales.
Run your own numbers
Enter your BFCM order count and your prior dispute rate for a dated calendar, an expected count, and a capacity note sized to your store.
The short answers to the questions merchants ask most about the BFCM dispute wave.
First alerts and dispute notices start in December, and in Chargeflow's two measured holiday seasons January had the most disputes filed per day. The tail runs into the first quarter, because cardholders generally have up to 120 days from the transaction processing date to file most disputes.
For most dispute conditions, March 27, 2027 for Black Friday orders (November 27, 2026) and March 30, 2027 for Cyber Monday orders (November 30, 2026). Delivery-based conditions can run longer, up to a 540-day cap.
Visa VAMP counts a month's fraud reports plus disputes against that same month's settled transactions, so a January dispute spike lands in a low-sales month and produces a higher ratio than the same spike would in November. The merchant Excessive line in standard regions is a ratio at or above 1.5% with at least 1,500 events in the month.
Staff December for first alerts and fast refunds, January for the peak filing month and the VAMP check, and keep evidence files and response cover in place through the late-March window close — then run a close-out review on the season's dispute-adjusted result.
Sources (checked November 4, 2026): Adobe Analytics forecast, September 28, 2026 ("U.S. Holiday Shopping Season to Hit Record $275.1 Billion Online"): Cyber Week 2026 (November 26–30) forecast at $47.5 billion online, up 7.4% year over year — a forecast for the US market, not a result. Mastercard research with Datos Insights, 2026 update ("What is the true cost of a chargeback for businesses?"): global chargebacks forecast to grow 37% from 2025 to 2029, reaching 359 million transactions a year; Mastercard research with Javelin (2026): US merchants average $128 per chargeback in fees plus internal handling ($46 third-party + $82 internal), excluding the disputed sale. Chargeflow BFCM calendar, Chargeflow Data Lab holiday study and Chargeflow BFCM readiness coverage (secondary sources, labelled as such): Black Friday November 27, 2026, Cyber Monday November 30, 2026, December alerts and first notices, January as the peak filing month in both measured seasons (1.40x and 1.41x November's daily rate), late-March 2027 window close (March 27 and 30), 30-to-90-day peak arrival lag, study of 58,783 disputes on Black Friday–Cyber Monday 2025 orders, and the worked VAMP example (6,000 January reports against 350,000 January settled transactions = 1.71%). Visa Core Rules, April 2026 edition (as summarised by Redo and Chargeflow): cardholders generally have up to 120 calendar days from the transaction processing date to file most disputes; delivery-based conditions run from the expected delivery date, capped at 540 days. Visa VAMP merchant Excessive line (standard regions, from April 1, 2026): ratio at or above 1.5% AND at least 1,500 events in the month. Adyen dispute timeframes (via Chargeflow coverage): 9 days for Visa disputes on US and Canadian local payments opened since July 21, 2025. Every statistic in this guide is attributed to its publisher; none is presented as this site's own finding. Your processor's case notice and your merchant agreement are the final word for any live case.
General information only — not financial or legal advice. Dispute windows, fees and program thresholds vary by network, processor and merchant agreement. Check your own notices for the figures that bind you.
Chargeback Clock