Black Friday Fraud: How Merchants Can Prevent Chargebacks During BFCM

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.

TL;DR:
- Fraud on Stripe's network started rising on November 8, 2025, so BFCM fraud rules need to be live by early November.
- During the four BFCM days, fraud volume was 1.7x the volume in a typical four-day period across a Stripe retail cohort.
- Most BFCM chargebacks land in December and January, when lower transaction volume inflates VAMP and ECM ratios.
- Outside CEMEA, Visa’s excessive-merchant VAMP threshold is at least 1.5% and 1,500 monthly reports; CEMEA has separate thresholds. Mastercard ECM starts at 100 chargebacks and 1.5%.
- Pre-dispute alerts (CDRN, RDR, Ethoca) resolve eligible disputes before they become formal chargebacks.
Black Friday fraud is the surge in card testing, stolen-card orders, friendly fraud, and return and promo abuse that hits ecommerce merchants during Black Friday and Cyber Monday (BFCM). For merchants, the real cost arrives weeks later as chargebacks that can push a Visa or Mastercard dispute ratio over a monitoring threshold in December or January, long after the sales are counted.
2026 forecast · Adobe
$47.5BForecast US online spend, Cyber Week 2026, up 7.4% YoY (Adobe)
2025 retail cohort · Stripe
1.7xFraud volume in the 4-day BFCM 2025 window versus a typical 4-day period (Stripe retail cohort)
BFCM 2025 · Stripe Radar
24.6MFraudulent transaction attempts Stripe Radar blocked over BFCM 2025
2025 retail returns · NRF
9%Share of retail returns reported as fraudulent (NRF 2025 Retail Returns Landscape)
Why BFCM Order Spikes Turn Into Chargeback Spikes
More orders mean more chances for fraud and disputes, and fraudsters time their attacks to the weeks when review teams are busiest. Stripe's 2026 peak-season guide found that fraud activity started climbing on November 8, 2025, almost three weeks before Black Friday, and kept spiking through the rest of the year. Across the merchant cohort it studied, fraud reached about 1.4% of total payment volume during the four BFCM days, and daily payment volume in the week before Black Friday hit 2.4x the annual daily average.
Volume keeps growing too. Adobe measured $11.8 billion in US online Black Friday 2025 sales and $14.25 billion on Cyber Monday, and its September 2026 holiday forecast expects both days to set new records in 2026.
US online sales · Adobe · Forecasts are not actual results
Black Friday
- 2025 actual
- $11.8B
- 2026 forecast
- $12.9B (Nov 27, +9.2%)
Cyber Monday
- 2025 actual
- $14.25B
- 2026 forecast
- $15.1B (Nov 30, +6.2%)
Cyber Week (Thanksgiving to Cyber Monday)
- 2025 actual
- $44.2B
- 2026 forecast
- $47.5B (+7.4%)
Full season (Nov 1 to Dec 31)
- 2026 forecast
- $275.1B (+6.7%)
- Period
- November 1–December 31, 2026
The sales land in November, but the disputes do not. Cardholders file after their statement arrives, after a delivery date passes, or after a return goes unrefunded, so BFCM chargebacks show up in December and January. That timing gap is what turns a strong sales weekend into a chargeback ratio problem, as the worked example further down shows. Summer sellers see the same lag: a September chargeback problem started in July.
The Fraud and Dispute Types That Spike During BFCM
For a refresher on what is a chargeback before the categories below, five types of risk compound during the holiday surge:
Card testing
fraudsters validate stolen card lists against small-ticket holiday promotions, then reuse working numbers for larger orders. See card testing fraud for the warning signs.
Stolen-card (card-not-present) orders
high-value, easy-to-resell items ship fast during BFCM, which is exactly what card-not-present fraud rings look for. Supply is up too: Visa's Fall 2025 Biannual Threats Report found a 173% increase in Compromised Account Management System account distribution in January–June 2025 versus the same period in 2024, so more stolen card numbers are circulating going into the holidays.
Friendly fraud
a cardholder makes a legitimate purchase, then disputes it as unauthorized or "not as described" once the statement arrives, often to skip your return process. See friendly fraud for how issuers classify these disputes.
Return and refund abuse
Wardrobing, empty-box returns, and serial returning put pressure on generous holiday return windows. NRF's 2025 Retail Returns Landscape reports that retailers expected 17% of holiday sales to be returned in 2025 and that 9% of all returns were fraudulent.
Hypothetical planning example · Assumed order-based rates
- 20,000 orders × assumed 17% return rate
- 3,400 returns
- 3,400 returns × assumed 9% fraudulent share
- 306 potentially fraudulent returns, or roughly 300
These assumed order-based rates illustrate workload; they are not an NRF forecast for an individual store.
Slow refunds can trigger credit-not-processed disputes, while fraudulent returns create direct losses.
Promo and account abuse
discount-code stacking, referral farming, and account takeover fraud using credentials leaked earlier in the year, all timed to hit while support teams are stretched. Promo abuse fraud covers the detection rules.
When Each BFCM Fraud Type Turns Into a Dispute
Each risk surfaces at a different point after the sale, under a different reason code, so each needs its own control and its own evidence.
Typical patterns · Case timing and reason codes vary
Card testing
- When it shows up
- During the event, as bursts of small authorizations and declines
- Typical reason code · Visa / Mastercard
- 10.4 / 4837 if test charges settle and cardholders dispute them
- First control
- Velocity limits, bot checks, CAPTCHA on checkout
Stolen-card orders
- When it shows up
- Once the real cardholder reviews the statement, often December
- Typical reason code · Visa / Mastercard
- 10.4 / 4837 (plus a Visa TC40 fraud report)
- First control
- Order screening before fulfillment, 3D Secure on high-risk orders
Friendly fraud
- When it shows up
- After the statement cycle, December into January
- Typical reason code · Visa / Mastercard
- 10.4 or 13.3 / 4837 or 4853
- First control
- Clear billing descriptor, delivery proof, pre-dispute alerts
Item not received
- When it shows up
- After the promised delivery date passes, peaking in late December
- Typical reason code · Visa / Mastercard
- 13.1 / 4853 (4855 is a legacy Mastercard code)
- First control
- Carrier tracking with signature on high-value orders, proactive delay emails
Return and refund disputes
- When it shows up
- January, as extended return windows close
- Typical reason code · Visa / Mastercard
- 13.6 / 4853
- First control
- Fast refund processing, return-condition photos, visible policy
Reason codes vary by allegation and network, so check the actual code on each case before choosing evidence.
How Visa and Mastercard Treat a BFCM Chargeback Spike
Card networks do not pause their monitoring programs for the holidays. A ratio spike caused by BFCM volume is scored the same way as one caused by weak fraud controls.
Visa VAMP (Excessive merchant)
- Merchant trigger
- Ratio of at least 1.5% AND at least 1,500 monthly fraud and dispute reports in the US, Canada, EU, Asia Pacific, and Latin America from April 1, 2026. CEMEA uses separate thresholds: at least 2.2%, 150 reports, and USD 75,000 in monthly fraud and dispute volume.
- How the ratio is measured
- TC40 fraud reports plus TC15 disputes, divided by settled card-not-present transactions in the same month
- Consequence
- Assessments and required remediation passed through by your acquirer
Mastercard ECM
- Merchant trigger
- 100 to 299 chargebacks in the month AND a ratio of 1.5% to 2.99% (higher tiers apply above that)
- How the ratio is measured
- Current-month chargebacks divided by the previous month's transactions
- Consequence
- Required remediation; no fine in the first program month, fines from month two
Sources: Visa's VAMP fact sheet and Stripe's monitoring-program guide. Acquirers can set stricter internal limits, so read your own processor agreement too. For the full threshold detail, see Visa Acquirer Monitoring Program (VAMP) and the Mastercard Excessive Chargeback Program guide.
Worked Example: Why January Is the Danger Month
Hypothetical example · Visa excessive merchant trigger outside CEMEA
The merchant normally settles 400,000 card-not-present Visa transactions a month. In this scenario, it settles 1,000,000 in November and 350,000 in January.
If 6,000 reports arrive in November
0.60%6,000 ÷ 1,000,000 × 100
Below the 1.5% ratio threshold.
If the same 6,000 reports arrive in January
1.71%6,000 ÷ 350,000 × 100
Above 1.5%, with a count above 1,500: both conditions are met.
Use the correct month. November’s large sales volume does not enter the January VAMP calculation.
Hypothetical example · Mastercard ECM
1.50%120 January chargebacks ÷ 8,000 December transactions × 100
The count of 120 falls inside the 100–299 band. Both ECM conditions are met. November’s volume does not enter this January calculation either.
A ratio that looked healthy in November does not establish what the acquirer will see in the February report for January’s data.
Fraud Prevention Tactics to Run Before the Surge Hits
Stripe saw fraud start rising on November 8 last year, so your BFCM rules need to be live by early November, not the week of Thanksgiving:
Control 1
Tighten velocity and enumeration rules
for the exact promotion windows and price points your BFCM deals will use, since that is where card testing concentrates.
Control 2
Calibrate 3D Secure and AVS/CVV settings
for higher volume. Stripe saw BFCM spending nearly quadruple versus a typical day, so thresholds tuned for a normal week will either block good customers or wave through fraud.
Control 3
Screen orders before fulfillment.
Holding and reviewing high-risk orders after checkout but before shipping stops stolen-card losses while the goods are still in your warehouse.
Control 4
Sharpen your billing descriptor and confirmation emails
so a cardholder recognizes the charge instantly, since unrecognized descriptors are a leading trigger for accidental friendly fraud.
Control 5
Publish a clear return policy
before BFCM traffic arrives; a policy that is easy to find and follow lowers the odds a customer disputes instead of returning.
Control 6
Enroll in chargeback alerts
so eligible complaints reach you before they become formal chargebacks, and check for earlier or pending refunds before acting on each alert.
BFCM Order Review Matrix: Approve, Hold, or Block
Manual review does not scale to peak volume, so decide in advance which signal combinations get approved automatically, held for review before fulfillment, or blocked outright:
Default action · Approve
Returning customer, same card and address as past orders
Order history can support evidence if a dispute comes later
Default action · Hold before fulfillment
First-time customer, high-value resale item, billing and shipping addresses differ
Classic stolen-card profile; shipping is the point of no return
Default action · Hold before fulfillment
Shipping to a freight forwarder or reshipper address
Common exit route for card-not-present fraud; confirm the buyer first
Default action · Block and rate-limit
Several cards tried from one device, IP, or email in minutes
Card testing pattern; approving the last card that works rewards the attacker
Default action · Block and add bot checks
Burst of very small authorizations on a promo SKU
Enumeration traffic that later turns into fraud disputes and processor scrutiny
Default action · Hold or cap the discount
Stacked promo codes on a brand-new account
Promo abuse and account farming peak during BFCM offers
Default action · Hold before fulfillment
Expedited shipping on a first order with a new email address
Fraud rings pay for speed so goods ship before the cardholder notices
Tune the thresholds behind each row to your own catalog and last year's disputes, and track how many held orders turn out to be good customers, since false declines cost revenue too.
A general ecommerce fraud prevention program is the baseline. A short list of fraud detection rules, stress-tested against last year's BFCM orders, is what holds up under peak traffic. For a dated, owner-by-owner plan, use the BFCM payments, fraud and disputes checklist.
Pre-Dispute Alerts: How CDRN, RDR, and Ethoca Cut BFCM Chargebacks Before They Post
Chargeback alerts are card network infrastructure, not a single vendor feature. Visa's Verifi network and Mastercard's Ethoca network both let an issuer tell a merchant that a cardholder is questioning a charge before that question becomes a formal chargeback.
CDRN
- Owner
- Verifi (Visa)
- Coverage
- Visa and non-Visa transactions through participating issuers
- How it resolves the dispute
- Issuer alert lets the merchant refund the cardholder directly instead of letting the dispute proceed
- Merchant action window
- Up to 72 hours to initiate the cardholder credit
RDR
- Owner
- Verifi (Visa)
- Coverage
- Visa transactions through participating issuers
- How it resolves the dispute
- Merchant-defined rules credit the cardholder automatically when a qualifying dispute arrives, with no manual review
- Merchant action window
- Automatic when qualifying rules are configured in advance
Ethoca Alerts
- Owner
- Ethoca (Mastercard)
- Coverage
- Participating issuers on the Ethoca network
- How it resolves the dispute
- Issuer data reaches the merchant in near real time so fulfillment can be stopped when possible and a refund can be issued before a chargeback is filed
- Merchant action window
- Act promptly on receipt; confirm the response deadline with your alert provider
Not every resolved alert disappears from the ratio. Visa excludes disputes resolved through its pre-dispute products from the VAMP count, but a TC40 fraud report on the same transaction can still count unless it qualifies under Compelling Evidence 3.0. A Mastercard dispute stopped before filing adds nothing to the ECM count, while one already filed counts regardless of outcome. Configure enrollment, refund checks, and ownership before the peak, because December is too late to start onboarding.
Preparing Dispute-Response Capacity Before You Need It
BFCM disputes do not arrive evenly. They cluster in December and January, right when support teams are recovering and staffing thins out for the new year. A merchant who wins disputes reliably in October can lose by default in January simply because response capacity did not scale with order volume. Our guide on how fast-growing brands stop post-holiday chargebacks covers the staffing side in detail.
2026 BFCM Dispute Calendar
Use these dates to staff dispute response and to know when each month's ratio is decided:
Planning timeline · Typical dispute patterns, not guaranteed dates
Stage 1
Early November
- Expected activity
- Fraud attempts start climbing (Stripe saw the rise begin November 8 in 2025)
- What to do
- Have velocity rules, holds, and alert enrollment live
Stage 2
Nov 27 to Nov 30, 2026
- Expected activity
- Black Friday through Cyber Monday; peak orders and card testing
- What to do
- Watch decline rates and hold queues daily
Stage 3
December
- Expected activity
- Stolen-card disputes and fraud reports arrive as cardholders read statements; item-not-received claims follow missed delivery dates
- What to do
- Respond inside each processor deadline; send delay notices before customers file
Stage 4
January 2027
- Expected activity
- Returns-related and friendly-fraud disputes peak while order volume falls back to normal
- What to do
- Model the January VAMP and ECM ratios against January and December volume
Stage 5
February 2027
- Expected activity
- Acquirers review January program reports
- What to do
- Have a remediation plan ready if the applicable program’s count and ratio thresholds were met
Stage 6
Late March 2027
- Expected activity
- Illustrative 120-day counts: November 27, 2026 plus 120 days is March 27, 2027; November 30 plus 120 days is March 30. These are not universal case deadlines.
- What to do
- Keep evidence through the applicable filing and response windows, including longer windows for eligible reason codes
Response deadlines vary by network, reason code, dispute stage, and processor, so read each notice. Adyen's dispute timeframe guidance shows how much they differ. Use the chargeback time limit guide to separate the cardholder's filing window from your response deadline, then match compelling evidence to the specific allegation.
Whatever payment stack runs your BFCM, from your payment service provider to any checkout-agent integrations, evidence capture should not depend on someone remembering to save order data during your busiest week. Adobe expects AI-referred traffic to US retail sites to grow 130% this season, which makes AI agent chargeback liability and agentic commerce chargebacks part of the same planning, since a disputed agent-placed order counts against your ratio like any other.
After filing
Automated recovery
Build and submit evidence for chargebacks that still get filed.
The Real Cost of Getting BFCM Fraud Wrong
US retail and ecommerce · 2026 study
$5.13 per $1Total cost per dollar of direct fraud loss, according to LexisNexis Risk Solutions' 2026 True Cost of Fraud study, including associated operational costs. This is a fraud-cost benchmark, not a fixed cost for every chargeback.
Visa · Share of fraudulent disputes
Around 20%Visa estimates that friendly fraud accounts for this share of fraudulent disputes globally, rising to up to 30% for high-volume online merchants.
Global chargeback cost projections
$36.9B → $46.1BProjected growth from 2026 to 2029, according to Mastercard research by Datos Insights (updated June 2026).
See chargeback statistics for the wider trend data.
Build Your BFCM Chargeback Plan in October, Not January
Before peak traffic
Tune fraud rules before the surge
Match controls to the actual promotions and have them live by early November.
After the sales
Staff for the delayed dispute workload
Prepare response capacity for December and January as part of the sales plan.
January monitoring
Model each ratio with the right denominator
January VAMP uses January volume; January ECM uses December volume. Plan for the acquirer’s February review of January data.
Frequently Asked Questions
Do merchants ever win chargebacks?
Yes. Merchants win chargebacks when they submit reason-specific evidence, such as delivery confirmation, usage logs, or a signed return policy, before the processor's deadline and the issuer accepts it. A timely response alone does not guarantee a win, and IP or device data by itself does not prove the cardholder authorized the order.
Do merchants get penalized for chargebacks?
Yes. Each chargeback usually carries a processor fee, and merchants with too many chargebacks can be placed in a card network monitoring program. Outside CEMEA, Visa’s excessive-merchant VAMP threshold is a ratio of at least 1.5% with at least 1,500 monthly fraud and dispute reports. CEMEA uses separate thresholds of at least 2.2%, 150 reports, and USD 75,000 in monthly fraud and dispute volume. Mastercard ECM starts at 100 chargebacks and a 1.5% ratio. Program fines are passed through by the acquirer, and sustained excess can lead to account termination.
How can ecommerce merchants prevent fraud during Black Friday and Cyber Monday?
Ecommerce merchants prevent Black Friday and Cyber Monday fraud by tuning velocity and card-testing rules to their promotion windows, screening high-risk orders before fulfillment, using 3D Secure selectively, writing a recognizable billing descriptor, and enrolling in pre-dispute alerts. Those controls should be live by early November, when fraud attempts start rising, and should be monitored for false declines.
How do I prevent fraud orders on Shopify during BFCM?
To prevent fraud orders on Shopify during BFCM, review Shopify's order risk analysis before you fulfill, cancel and refund high-risk orders before they ship, and add a post-checkout screening layer that flags stolen-card and friendly-fraud patterns. Shopify merchants should also confirm their chargeback alert coverage and response workflow before Black Friday, since most holiday disputes arrive in December and January.
What is the 540-day rule for chargebacks?
The 540-day rule refers to the longest chargeback filing window under some Visa and Mastercard reason codes, which can extend to 540 calendar days from the transaction for certain delayed-delivery or service cases. It is not a universal extension; most disputes must be filed within 120 days, so check the network rule for the specific reason code.
Do pre-dispute alerts like CDRN or Ethoca help avoid a VAMP or ECM violation?
Pre-dispute alerts like CDRN, RDR, and Ethoca help merchants avoid VAMP and ECM violations by resolving eligible disputes before they become formal chargebacks. Visa excludes disputes resolved through its pre-dispute products from VAMP counts, though a related TC40 fraud report can still count, and a Mastercard dispute stopped before filing never enters the ECM count. Check for duplicate refunds before acting on each alert.

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.













.png)


