Announcing our New Developer Hub
Announcing our New Developer Hub
Announcing our New Developer Hub
Announcing our New Developer Hub
/
Disputes & Chargebacks
October 14, 2026
Oct 14, 2026

Chargeback Alerts vs Representment: When to Refund or Fight

White circular logo with interlocking shapes at the center surrounded by overlapping orbit-like elliptical lines and scattered blue diamond shapes.

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.

600+ reviews
No credit card needed.
Chargeback Alerts vs Representment: When to Refund or Fight

TL;DR:

  • Alerts and Visa RDR settle a complaint before a chargeback exists, while representment only applies after one is filed.
  • Mastercard recommends submitting Ethoca outcomes within 24 hours, CDRN gives a 72-hour decision window, RDR resolves automatically on your rules, and a filed chargeback runs on your acquirer's clock.
  • Stripe blocks refunds outside the dispute process once a chargeback is open, so confirm the stage before paying anything out.
  • A won representment still counts toward Visa VAMP and Mastercard chargeback ratios, so only pre-dispute resolution keeps a case out of the count.
  • In our hypothetical model, fighting a $50 order needs about a 62% win chance to beat a refund, while a $500 order needs about 8%.
Loading the Elevenlabs Text to Speech AudioNative Player...

Chargeback alerts are pre-dispute notifications that let a merchant refund or stop an order before the issuer files a chargeback, while representment is the evidence response a merchant submits after a chargeback has been filed. The case's stage decides which one applies, and it decides whether you can still refund, must follow the dispute process, or can contest the claim.

Both routes matter because the volume keeps rising, and only one of them keeps a case out of your monitoring ratio.

Global cost forecast$36.9B

Projected global chargeback cost in 2026, rising to $46.1B in 2029

Global volume forecast286M

Chargebacks projected worldwide in 2026

2025 to 2029 forecast+37%

Expected growth in chargeback volume from 2025 to 2029

Visa VAMP · ratio criterion1.5%

Visa VAMP Excessive ratio in most regions (2.2% in CEMEA)

Forecasts describe global costs and volumes. The Visa figure is a regional monitoring ratio; event-count and other regional criteria also apply.

Sources: Mastercard, What is the true cost of a chargeback for businesses? (updated June 2026, research by Datos Insights) and Stripe's monitoring program guide.

{{cta}}

Chargeback alerts vs representment at a glance

Alerts and Visa RDR
Stage
Complaint or pre-dispute window, before any chargeback exists
Who decides
You (Ethoca, CDRN) or your pre-set rules (RDR)
Time to act
Best-practice 24 hours for Ethoca outcomes, a 72-hour decision window for CDRN, automatic for RDR
Money result
A refund or credit, up to the full amount
Cost points
Provider fee per alert or RDR resolution, plus the refund
Main risk
Duplicate refund or a missed window
Representment
Stage
A chargeback has been filed and funds are debited
Who decides
The issuer, after reviewing your evidence
Time to act
Set by your acquirer, 7 to 21 days at Stripe
Money result
Disputed funds returned only if you win
Cost points
Stripe fee example: Dispute fee kept even if you win, countered fee returned on a full win. Terms vary by processor and country.
Main risk
Weak evidence, a missed deadline or a one-shot submission

An alert does not authorize ignoring a filed dispute. Once a chargeback is open, Stripe's dispute documentation states that you cannot issue a refund outside the dispute process, so follow your payment service provider's instructions for that case.

Where each case sits in the dispute lifecycle

These are possible paths and stages. A case does not pass through every one of them, and the notification types have different rules.

  • Before a filed chargebackOrder Insight lookup
    Who decides
    Issuer, using your data
    Time to act
    Answered by your processor, per Stripe
    Money and ratio effect

    Under Visa Compelling Evidence 3.0, Stripe's Order Insight documentation says that if at least two prior transactions with complete product descriptions share a matching IP address and at least one matching email address or delivery address, the issuer must block the dispute. The dispute is never filed, so there is no received fee or rate increase, though Stripe's US price list charges $15 per block.

  • Before a filed chargebackEarly fraud warning
    Who decides
    You (optional)
    Time to act
    None required
    Money and ratio effect

    No action is required. Stripe reports that about 40% of Visa and Mastercard early fraud warnings become fraud disputes when the charge is not refunded, with the rate varying by network and amount. A refund does not clear the warning itself.

  • Before a filed chargebackEthoca alert
    Who decides
    You
    Time to act
    Best-practice 24 hours to submit the outcome, per Mastercard documentation
    Money and ratio effect

    Refund or stop fulfillment, then report the outcome so the issuer knows not to raise a chargeback.

  • Before a filed chargebackCDRN alert
    Who decides
    You
    Time to act
    72-hour decision window, per Verifi
    Money and ratio effect

    You decide how to resolve the case, including whether to credit the cardholder, before a chargeback is filed.

  • Before a filed chargebackVisa RDR
    Who decides
    Your pre-set rules
    Time to act
    Automatic
    Money and ratio effect

    The cardholder is credited automatically before a chargeback is created. Per Verifi, resolved cases do not count against Visa's dispute ratio, subject to the data-extract caveat below.

  • Before a filed chargebackInquiry
    Who decides
    You
    Time to act
    Stripe closes an unescalated inquiry after 120 days
    Money and ratio effect

    Mostly American Express and Discover. Stripe says Visa and Mastercard no longer use inquiries.

  • Filed chargebackChargeback
    Who decides
    You, then the issuer
    Time to act
    Acquirer sets the clock
    Money and ratio effect

    Funds are debited and your dispute rate rises. Accept it or submit representment once.

  • Later escalationPre-arbitration
    Who decides
    Issuer escalates, you accept or decline
    Time to act
    Visa collaboration disputes: 28 days. Mastercard: 8 to 28 days depending on reason code, per Adyen
    Money and ratio effect

    Accepting creates a second chargeback.

  • Later escalationArbitration
    Who decides
    The card network
    Time to act
    Several months, per Adyen
    Money and ratio effect

    Per Adyen, the liable party pays a filing fee: USD 600 on Visa, up to USD 600 on Mastercard.

RDR limits before you build rules
Customizable rules

Verifi says merchants can set up to ten customizable rules per BIN or CAID.

Full amount and no prior refund

Stripe notes that Verifi does not support partial resolution or disputes on refunded transactions. RDR only resolves a dispute when the cardholder disputes the full amount and the transaction has not been refunded.

Accepting liability

Adyen's Visa guidance adds that an RDR case cannot be defended, which in practice makes every rule a decision to accept liability.

Timing of the data extract

The Visa VAMP fact sheet excludes disputes resolved through pre-dispute solutions "contingent on the timing of the data extract." This qualifies the ratio benefit.

Our guides to Visa Rapid Dispute Resolution and VAMP cover both in detail.

Visa CE 3.0 · early-versus-late split

Per Adyen's CE 3.0 FAQ, the requirements include:

Eligible dispute

Applies to reason 10.4 only.

Transaction history

At least two non-disputed, non-fraud transactions with the same payment method, settled 120 to 365 days before the dispute date.

Matching data

At least two core data elements must match: customer ID, IP address, delivery address or device ID. One must be the IP address or device ID.

Effective 24 October 2026: The Visa Core Rules (18 April 2026 edition) update CE 3.0 for 10.4 so that multi-merchant transactions can count as evidence.

Mastercard's developer documentation lets you report an alert as resolved with a prior refund, so a prior refund should be reported rather than repeated. Mastercard reports, citing internal data, that Ethoca Alerts helped prevent more than 39 million chargebacks in 2025. Mastercard's GMAP replaces ACMP on 1 April 2027 and scores fraud and non-fraud chargebacks together, so confirm how your provider treats resolved cases. For provider-level differences, see CDRN vs Ethoca alerts.

Network clocks and fees once a chargeback is filed

Per Adyen · confirm the deadline on your case
Cardholder filing window
Visa
120 calendar days in general, up to 540 in some cases such as merchandise or services not received
Mastercard
120 calendar days in general, up to 540 in some cases
Your time to respond to a chargeback
Visa
9 days for payments processed locally in the US and Canada from 21 July 2025, otherwise 18
Mastercard
40 days from the notice of chargeback
Issuer pre-arbitration window after your defense
Visa
30 to 32 days from the defense upload (collaboration disputes)
Mastercard
45 days from the defense upload
Your time to accept or decline pre-arbitration
Visa
28 days (collaboration disputes)
Mastercard
8 to 28 days, depending on reason code
Scheme arbitration filing fee
Visa
USD 600 for the liable party, on top of the dispute amount
Mastercard
Up to USD 600, added to the second chargeback if Mastercard rules for the issuer

Those figures come from Adyen's dispute timeframes and its Visa and Mastercard chargeback guidelines, not from the network rulebooks, so confirm them against the current rulebook. Your acquirer sets the deadline that binds you, and it can be shorter than the network limit, so read the date on the case itself. Stripe documents a total lifecycle of 2 to 3 months. See also our guides to chargeback time limits, Visa chargeback dispute rules, Mastercard chargeback time limits and the Mastercard dispute administration fee.

First determine the case's actual stage

Confirm the stage from the case and payment record, not from the customer's wording, before any money moves. A customer who says "I disputed it" may mean a support complaint, a bank inquiry or a filed chargeback, and your systems need to tell those apart. Record the case ID, payment ID, stage and deadline, and join any support refund or replacement order to that record.

An early notification and a filed chargeback can arrive close together, and a policy built for a pre-dispute case should not be applied after the case has moved on. Assign one decision owner for ambiguous cases so payments and customer service never issue a refund and a contradictory response on the same payment.

Decide whether the customer has a valid issue

Resolve a legitimate customer claim even when fighting would be possible. Ask whether the business delivered what was promised, processed the cancellation correctly or completed an agreed refund. A successful checkout proves that a payment occurred, but it does not answer whether the goods arrived, a subscription was canceled or an advertised service was delivered.

Review the actual complaint against the transaction timeline. If a promised refund was never completed, correct that failure through the applicable process. If the customer does not recognize the descriptor, a clear explanation matters more than an accusation. Friendly fraud is one possible cause of disputes, not a description of every buyer who complains, and a won representment does not by itself prove the customer's intent.

When early resolution can make sense

Resolving early is sensible when it is the right outcome for the customer or when continuing is uneconomic. An unfulfilled order may let you avoid a shipment, but confirm that the warehouse actually stops it before counting any avoided cost, because a completed shipment cannot become an avoided shipment after the alert arrives. Chargeflow Prevent works earlier in that window by scanning orders after checkout and before fulfillment.

Early fraud warnings follow different economics because they are a probability, not a confirmed dispute. Stripe's analysis suggests refunding when the charge is roughly at or below your dispute fee, and it calls refunding charges more than 35% above that fee likely not worthwhile. See our TC40 refund guide.

Alerts are not probabilities, because the cardholder has already disputed the charge or the issuer has already confirmed fraud, the two alert types in Mastercard's documentation. Compare the refund against the full cost of letting the case continue, including the Ethoca alert fee where it applies, and weigh the ratio headroom you keep by resolving before a chargeback exists.

When representment can make sense

Representment fits when the chargeback concerns a valid transaction and you hold evidence that answers the claimed reason. A delivery claim needs order, fulfillment and delivery context, not just proof of authorization. A cancellation complaint needs the cancellation terms and timeline, not just shipment tracking. Our evidence source map shows where each record lives, and the chargeback representment guide covers the submission process.

Use your own mature case history for planning. A headline win rate from another merchant, reason code or submission population does not transfer, and a rate based only on submitted cases can look strong while many eligible cases are never answered. The issuer decides, Stripe allows one evidence submission, and a lost dispute is final.

Break-even: refund at the alert or fight the chargeback

Our simplified model · not a network rule

Fighting is cheaper than refunding when your estimated win probability exceeds:

(F + C + H) / (A + C)

A · Order amount
Hypothetical order value
F · Dispute received fee
$15 in this US Stripe example
C · Countered fee
$15, returned on a full win
H · Handling cost
Hypothetical $10

Stripe's published US fees provide the $15 received and $15 countered amounts used here.

Refunding loses the order amount. Fighting incurs the received fee and handling cost either way, plus the order amount and countered fee when you lose. This simplified model excludes alert-provider fees; those vary by contract and should be included in your actual comparison.

Hypothetical amounts · F = $15, C = $15, H = $10
$25 orderAbout 100%

Win probability needed to beat refunding.

Suggested read-out · our recommendation

Even a certain win only ties with refunding, so refund or resolve early

$50 orderAbout 62%

Win probability needed to beat refunding.

Suggested read-out · our recommendation

Refund unless the evidence is strong and reason-specific

$100 orderAbout 35%

Win probability needed to beat refunding.

Suggested read-out · our recommendation

Fight when the record is solid

$250 orderAbout 15%

Win probability needed to beat refunding.

Suggested read-out · our recommendation

Fight when you hold any relevant evidence

$500 orderAbout 8%

Win probability needed to beat refunding.

Suggested read-out · our recommendation

Fight unless the claim is valid, and build the evidence early

The formula ignores your chargeback ratio headroom, which favors resolving early when your VAMP or Mastercard monitoring position is tight, and it assumes the goods are lost in both paths. For the full screen, see our five-gate decision model and the guide on when to fight and when to forgive.

{{cta}}

How each route counts toward VAMP and Mastercard ratios

Winning representment recovers money, but it does not lower your monitoring ratio. Card network monitoring programs ignore dispute outcomes, and Mastercard counts a chargeback regardless of refund, liability shift or outcome, per Stripe's monitoring program guide. Only a case resolved before it becomes a chargeback stays out of the count.

Visa RDR resolution
Visa VAMP count
Excluded as a pre-dispute resolution, subject to the timing of Visa's data extract
Mastercard ECM and HECM count
Not applicable (RDR is a Visa program)
CDRN resolution before a chargeback
Visa VAMP count
For a Visa case resolved before filing, no dispute (TC15) is filed. Any TC40 fraud report must be assessed separately.
Mastercard ECM and HECM count
CDRN covers Visa and non-Visa disputes. For a Mastercard case resolved before filing, no chargeback is filed, so nothing enters the ECM or HECM chargeback count.
Ethoca alert refunded before a chargeback
Visa VAMP count
No dispute (TC15) is filed for the case
Mastercard ECM and HECM count
No chargeback is filed, so nothing is counted
Issuer fraud report (TC40) on the payment
Visa VAMP count
Counts even if you refund, unless it qualifies for Compelling Evidence 3.0
Mastercard ECM and HECM count
Not part of the ECM chargeback count
Chargeback won through representment
Visa VAMP count
Still counts
Mastercard ECM and HECM count
Still counts
Chargeback lost or accepted
Visa VAMP count
Counts
Mastercard ECM and HECM count
Counts
Refund issued after the chargeback
Visa VAMP count
Still counts, because programs do not consider refunds
Mastercard ECM and HECM count
Still counts

RDR is Visa-specific; CDRN is card-brand agnostic. Distinguish the absence of a filed chargeback from any separate fraud report.

Hypothetical month · ratio arithmetic

10,000 settled card-not-present Visa transactions, 100 disputes and 60 fraud reports. Forty fraud reports concern transactions already disputed; Visa counts those transactions in both TC40 and TC15.

Starting position1.6%

(100 + 60) ÷ 10,000

VAMP count: 160

Resolve 30 non-fraud cases early1.3%

(160 − 30) ÷ 10,000

VAMP count: 130

Win 30 representments1.6%

160 ÷ 10,000

VAMP count stays at 160

The starting ratio is above the 1.5% Excessive ratio criterion in most regions, but this example's 160 events are below the 1,500-event Excessive minimum outside CEMEA. A ratio alone does not establish Excessive monitoring status; regional and other applicable criteria must also be met.

Thresholds and fines by network are in our chargeback thresholds guide.

A stage-by-stage decision tree

  1. Identify the case stage and the deadline on the case itself. If a chargeback is filed, use the dispute process instead of assuming an alert refund is still available.

  2. Check prior financial actions. Resolve any gap between approved, pending and completed refunds before taking another action.

  3. Assess the customer issue. Correct a genuine service, cancellation or delivery failure through the applicable path.

  4. Review evidence quality. Ask whether the records answer the actual complaint, not whether records exist.

  5. Compare economics using the break-even formula, your own win history and your ratio headroom.

  6. Apply the permitted action and document the reason. Escalate cases where the stage, entitlement or payment record is unclear.

  7. Reconcile the financial result and keep both the action and the final outcome for later analysis.

Route unclear cases to an owner instead of forcing every exception into one dollar threshold. The pre-arbitration and arbitration guides cover the later rounds, and the inquiry vs chargeback guide covers the networks that still use inquiries.

Four cases that need different answers

Hypothetical cases
Alert for an unfulfilled order with an appropriate refund
Useful next step
Refund, confirm the shipment stop and report the outcome
Why
You can still avoid a shipment, and resolving early avoids a chargeback and its fees
Alert for a payment you already refunded
Useful next step
Report it as previously refunded, do not refund again
Why
A second credit duplicates the loss
Filed chargeback after a refund already completed
Useful next step
Respond through the processor with the refund record
Why
The completed refund is evidence the credit was given, and another payout would double the loss
Filed delivery dispute with incomplete carrier records
Useful next step
Investigate delivery context before responding, then check the Visa 13.1 evidence requirements
Why
A payment receipt does not answer non-delivery

Different stages and records make a universal "refund below this amount, fight above it" rule inadequate. If a refund and a chargeback do overlap, our guides to double refund chargebacks and chargebacks after a refund explain how to reconcile them.

Connect alerts and recovery without double counting

Use one case history across customer service, alert operations and recovery, so the recovery team sees prior resolutions and the customer timeline if a case proceeds. Measure early resolutions separately from submitted responses and final recoveries. A refund is not recovered revenue, and a won response is not a prevented dispute.

Deduplicate at the payment level without erasing genuinely distinct cases. One payment can generate several notifications or state updates, but you need one coherent record of money returned and disputed value, with provider identifiers preserved so discrepancies stay traceable. Review a sample of cases that moved between stages for missing records and handoffs that caused missed deadlines.

Where Chargeflow supports the lifecycle

Chargeflow AlertsBefore a chargeback

Covers the pre-dispute stage through Verifi (RDR and CDRN) and Ethoca.

Chargeflow AutomationAfter a chargeback

Builds and submits representment for filed chargebacks.

See how automated chargeback management works for the mechanics, and how to choose a chargeback alert provider before you commit to one.

Frequently asked questions

What is the difference between a chargeback and a representment?

A chargeback is the debit an issuer applies when a cardholder disputes a payment, and representment is the merchant's evidence response to that chargeback. The chargeback moves the funds out, and representment is the only route to get them back. Our guide to dispute vs chargeback vs refund vs representment defines all four terms.

What does representment mean in banking?

In banking, representment is the second presentment of a disputed card transaction. After the issuer charges a payment back, the merchant's acquirer presents it to the issuer again with the merchant's evidence and asks for the funds to be returned. The original sale is the first presentment, which is where the term comes from.

Is a chargeback the same thing as a dispute?

Not exactly. A dispute is the cardholder's complaint to their bank, and a chargeback is the formal reversal that can follow, which is why alerts and RDR can resolve a dispute before any chargeback exists. For the full definition, read what is a chargeback.

Are chargeback alerts a substitute for representment?

No. Chargeback alerts only act before a chargeback exists and usually end in a refund or stopped order, while representment answers a chargeback that is already filed. Some cases resolve early, and the rest need their own decision and response. See how chargeback alerts work for coverage and limits.

Can a chargeback be reversed?

Yes, but only through representment. While a dispute is active, submitting evidence is the only way to overturn it, and the issuer decides. A lost dispute is final, although a customer can still withdraw a dispute after a loss.

Can a merchant refund after a chargeback is filed?

Not outside the dispute process. Stripe states that you cannot issue a refund outside the dispute process while a dispute is open, so follow your processor or acquirer's instructions for the filed case, and accept the dispute if you agree with the customer.

What do chargeback alerts and representment cost?

Alert pricing is set by your provider contract, usually per alert or per resolution, and the refund itself is the main cost. Representment adds a dispute fee that is not returned and a countered fee that is returned on a full win, which are $15 each in the US at Stripe (see Stripe dispute fees). On processors that support arbitration, such as Adyen, a lost scheme arbitration can add a filing fee of up to USD 600, while Stripe does not support the arbitration phase. Our chargeback alert cost and ROI guide models the alert side.

Should a merchant always fight a high-value chargeback?

No, value alone does not justify a response. You also need evidence that answers the claimed reason, a sound basis for contesting the claim and a break-even win probability you can plausibly meet.

Chargeflow's Products

Resolve Disputes Before They Become Chargebacks

Chargeflow Alerts uses Verifi, Ethoca, and the Chargeflow Network to deflect card disputes before they become chargebacks.

SHARE THIS ARTICLE
White circular logo with interlocking shapes at the center surrounded by overlapping orbit-like elliptical lines and scattered blue diamond shapes.

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.

600+ reviews
No credit card needed.
subscribe

The latest chargebacks, fraud, and ecommerce content, in your inbox. Every week.

Sign up now and never miss out the latest trends!
By providing your email you're agreeing to our Terms of Service and Privacy Notice
Diagram with dashed and curved lines forming segmented arcs highlighted by three blue diamond markers on the left side.Abstract circular grid design with blue diamond markers on a half-black, half-white background.