A chargeback is not just a reversed sale. The merchant can lose the transaction value, the product or service already supplied, fulfilment cost and a chargeback fee. Every dispute also creates a negative signal against the processing account. rising dispute levels can trigger monitoring, reserves, payout restrictions or account termination.
Vellis supports merchants through Vellis card processing, working with underlying acquiring and banking partners while remaining the merchant’s authorized provider and direct point of contact. You work with Vellis from setup through dispute escalation rather than being left in a generic support queue.
The Chargeback Economics That Most Merchants Ignore
The visible cost of a chargeback is rarely the full cost.
The direct loss can include the transaction value, product cost, shipping, fulfilment, sales commission, marketing spend, support time and a chargeback fee. Digital merchants may lose the payment after the customer has already consumed the service.
Administration adds more cost. Staff must identify the transaction, interpret the reason code, gather evidence, prepare the response and track the outcome. A successful representment may recover the sale, but it does not always remove every fee or operating cost.
The largest cost appears when disputes affect account status. A rising ratio can lead to document requests, reserve changes, slower settlement, transaction limits and eventually closure. Replacing a processing account under pressure can interrupt revenue and make future underwriting harder.
That compounding effect is why a chargeback should be measured in two ways:
- Financial loss per dispute, including transaction value and operating cost
- Account impact, including count, ratio, reason code, card network, market and traffic source
Finance teams should track chargebacks against settled transactions by card network and merchant account. A blended company-wide percentage can hide a problem concentrated in one MID, region, product line or subscription cohort.
Network Thresholds and What They Trigger
Network thresholds are compliance events, not informal benchmarks. Once the relevant criteria are met, the acquirer and processor cannot simply ignore the program requirements. They may still choose how to manage the commercial relationship, and many will act before a network threshold is reached.
Visa: VAMP replaced the old VDMP model
Merchants should not manage their risk using old Visa Dispute Monitoring Program shorthand. Visa consolidated its former dispute and fraud monitoring programs into the Visa Acquirer Monitoring Program, or VAMP.
VAMP uses a combined count of qualifying fraud reports and disputes divided by settled card-not-present Visa transactions. This matters because a merchant can be affected by both fraud reporting and disputes even where the two categories were previously reviewed separately.
For merchants in Asia-Pacific, Canada, the EU and the US, the excessive-merchant VAMP ratio is 1.5% from 1 April 2026, with a minimum monthly count of 1,500 fraud reports plus disputes. Latin America uses a 1.5% ratio and a 1,500 minimum count. CEMEA uses different criteria, including a 2.2% ratio, at least 150 events and at least USD 75,000 in amount.
The minimum-count requirement does not create a safe zone for smaller merchants. Processors can set lower operating limits and act before network-level classification. Manage to the limit agreed with your provider, not the highest number in a network document.
Mastercard: ECP, ECM and HECM
Mastercard’s Excessive Chargeback Program monitors chargebacks at merchant level. The ratio is calculated using chargebacks received in the current calendar month divided by Mastercard transactions acquired in the preceding month, multiplied by 10,000 to produce basis points.
The program uses Excessive Chargeback Merchant and High Excessive Chargeback Merchant classifications. Mastercard’s public merchant rules direct acquirers to a separate Data Integrity Monitoring Program manual for current numeric thresholds. The familiar planning markers are 100 chargebacks with a 1.5% ratio for ECM and 300 chargebacks with a 3.0% ratio for HECM, but merchants should confirm the current criteria and counting logic with their provider.
A threshold breach can trigger monitoring, corrective-action requirements, assessments and tighter oversight. Continued non-compliance can create pressure for reserve increases or termination. Where the applicable reporting conditions are met, excessive chargebacks can also support a MATCH listing, which can make future merchant-account approval substantially harder.
The operational rule is simple: set internal warning levels well below the external limits. A team that starts corrective action only after a threshold is crossed is already late.
Prevention Is 80% of the Work
Most chargeback improvement comes from fixing the customer experience, transaction controls and evidence trail before a dispute exists.
Make the billing descriptor recognizable
The descriptor should match the name customers know. A legal entity, holding company or abbreviated brand that never appeared during checkout creates avoidable “transaction not recognized” disputes.
Test how the descriptor appears in banking apps. Include a support number or short URL where the format allows it. If several brands use one merchant account, each customer must still connect the statement entry to the purchase.
Capture clear consent at checkout
The checkout should show the total amount, currency, product or service, delivery timing, refund terms and any recurring commitment. Recurring billing must be clearly authorized and is available depending on your platform.
Do not rely on a policy hidden in a footer. Present material terms before payment and record the version accepted, timestamp, device data and order identifier. For subscriptions, send an immediate confirmation and appropriate reminders before rebilling.
Build delivery evidence into fulfilment
Physical-goods merchants need carrier, tracking and delivery records linked to the order. High-value shipments may justify signatures. Digital merchants should record account creation, login history, access events, device information and the service used. Service businesses need evidence that the appointment, report or agreed work was delivered.
Make refunds easier than disputes
A customer who cannot find the cancellation route or waits several days for a response may call the issuer first.
Publish a clear refund policy, resolve low-value cases quickly and show the expected refund timeline. Send confirmation when a refund is issued, and check whether a dispute is already open before refunding outside the chargeback process.
Set a customer-service response standard
High-dispute categories need fast support. A subscription, digital-goods or cross-border merchant should define response times for billing questions, cancellation requests, delivery complaints and suspected fraud.
Track disputes that began as support contacts. Repeated chargebacks after the same delayed or confusing response point to an operational problem, not a fraud-rule problem.
How to Respond to a Chargeback Properly
A good response is reason-code specific, complete and submitted before the processor’s deadline. A large evidence pack is not automatically a strong one.
First decide whether the dispute should be challenged. Accept cases where the charge was wrong, a refund was missed, fulfilment failed or the evidence is weak. Fighting every case wastes time.
For disputes worth challenging, use a controlled workflow.
1. Triage the notice immediately
Record the card network, reason code, amount, transaction date, deadline, order ID and customer account. Assign an owner on the day the notice arrives. Processor deadlines may be shorter than the network’s outer time limit because the processor needs time to review and submit the case.
2. Match evidence to the allegation
For an unrecognized or fraud claim, use authentication results, account history, device data, prior undisputed transactions and proof connecting the cardholder to the purchase.
For non-receipt, provide fulfilment date, tracking, delivery confirmation and the checkout address. Digital merchants should provide access and usage records.
For “not as described,” include the product description, order confirmation, communications, return instructions and remedy offered. For recurring disputes, include accepted terms, notices, billing history and the cancellation date.
3. Write a short case summary
The reviewer should understand the case in under a minute. State what was purchased, how it was delivered or used and why the evidence answers the reason code.
4. Submit clean, legible documentation
Use consistent order IDs, readable dates and a logical sequence. Screenshots must show the customer, transaction and event being proved.
5. Record the outcome and root cause
Record why the chargeback occurred and whether the prevention process should change, even when the merchant wins.
Measure win rate by reason code, but do not use win rate as the main chargeback KPI. The best dispute is the one that never enters the formal process.
Chargeback Protection Tools and When They Help
Tools pay off when they address a defined source of disputes. Buying every product in the market without fixing policies, descriptors and support creates cost without control.
Ethoca Alerts
Ethoca Alerts connects issuers, acquirers and merchants so the merchant can receive early notice of a fraud report or dispute. The merchant may be able to stop fulfilment, cancel access or issue a refund before the case becomes a chargeback.
It is valuable when the merchant has enough eligible volume and can act quickly. It is less useful when alerts sit untouched or fulfilment is already irreversible.
Verifi Order Insight
Order Insight shares enhanced transaction and order information with issuers and cardholders. It can help a customer recognize a legitimate purchase and can support the use of transaction history and compelling evidence to deflect certain first-party-misuse disputes.
It is strongest with clean order data and consistent identifiers. It does not replace customer service or fix genuine delivery and cancellation failures.
3D Secure 2
EMV 3-D Secure helps merchants and issuers authenticate card-not-present transactions. Depending on the transaction, market, exemption and authentication result, it may shift liability for certain unauthorized-fraud disputes.
That does not make the transaction chargeback-proof. 3D Secure generally does not protect the merchant from disputes about delivery, service quality, cancellation, refunds or misleading terms. It also needs careful configuration because unnecessary challenges can reduce conversion.
Use 3D Secure based on transaction risk, regulation and commercial performance. Review approval rate, challenge rate, authentication success, fraud loss and conversion together.
What Happens When You Cross a Threshold
The processor’s response usually becomes progressively more restrictive.
The first step may be a warning, data request or corrective-action plan. The merchant may be asked to explain dispute sources, provide current policies, show fraud controls and commit to measurable reductions.
If the ratio remains high, the processor or acquiring partner may increase the reserve, delay settlement, cap volume, restrict products or markets, require prevention tools or place the account under closer monitoring.
Termination becomes more likely when the merchant cannot explain the cause, misses action-plan targets, provides incomplete information or continues the behavior that created the disputes. A processor may also close the account earlier than the network limit if it believes the loss, compliance or reputational risk is unacceptable.
This is why merchants should understand why processors terminate accounts. Network thresholds are only one part of the decision. Underwriting accuracy, fulfilment, liquidity, complaints and communication also affect stability.
Negotiation is strongest when the merchant brings evidence rather than promises:
- A reason-code and root-cause breakdown
- Daily and weekly chargeback forecasts
- Refund and support improvements already implemented
- Fraud-rule changes and measured results
- Alert and pre-dispute coverage
- Updated fulfilment and delivery controls
- A named internal owner and reporting cadence
A credible remediation plan may preserve the account, but there is no guarantee. Build it before the processor asks.
Build a Chargeback Operating System, Not a Monthly Report
Monthly reporting is too slow for an account near a threshold.
Create a daily dashboard by merchant account and network. Track settled transactions, disputes, fraud reports, alerts, refunds, representments, reason codes, product, country, traffic source and fulfilment status.
Use three limits:
1. Internal target: the level the business expects to maintain during normal operation.
2. Warning level: the point that triggers investigation and corrective action.
3. Critical level: the point that triggers executive review, provider escalation and immediate traffic or fulfilment controls.
Account for reporting lag. Chargebacks arriving this month often relate to earlier sales. A sales decline can worsen the ratio because disputes continue while the transaction denominator falls.
Segment the data. One affiliate, cohort, product claim, shipping route or market can create most of the exposure.
High-volume merchants also need to coordinate dispute controls with capacity planning and provider communication. The wider guide to card processing for high-volume merchants explains how volume changes, reserves and acquiring structure affect continuity beyond chargebacks alone.
Run a weekly review until performance is stable. Assign actions across payments, fraud, support, fulfilment, finance and marketing.
Working With a Provider That Supports You Through Disputes
A merchant facing elevated chargebacks needs direct access to someone who understands the account, the underlying acquiring relationship and the remediation plan.
Vellis acts as an authorized provider and works with relevant acquiring, banking and payment partners. Vellis is not a bank or an acquirer and is not positioned as the direct owner of the underlying infrastructure. In some arrangements, Vellis may act as a referral agent.
The client relationship remains clear: you work with Vellis. Vellis manages setup end to end, coordinates with the relevant partners and remains the merchant’s direct point of contact for documentation, account reviews and dispute escalation.
That matters when deadlines are short. A direct contact can review the transaction profile, identify where ratios are rising, help structure the evidence workflow and coordinate the response expected by underlying partners.
Support can include reviewing descriptors and checkout terms, mapping dispute reasons, evaluating tools, preparing a corrective-action plan and communicating changes early.
Vellis supports businesses globally, excluding OFAC-listed countries. Eligibility remains subject to review and underwriting, with the MATCH list as the hard exclusion. This can include merchants in telehealth, supplements, crypto, healthcare, biotech, cross-border operations and similar categories where fulfilment, recurring payments, customer expectations or international sales can increase dispute complexity.
No provider can guarantee that an account will never be reviewed or terminated. The practical advantage is a structured setup, accurate data and a real person managing the relationship under pressure.
Chargeback management works when prevention, evidence, threshold monitoring and provider communication operate as one system. Fix the causes before disputes are filed. Respond only with evidence that answers the reason code. Track ratios before monthly reports arrive. Escalate early when the trend moves in the wrong direction.
That is how merchants protect processing continuity instead of searching for a replacement account after termination.
