Visa and Mastercard Chargeback Monitoring Programs, Explained for Merchants

Visa (VDMP and VFMP, now VAMP) and Mastercard (ECP) monitor every merchant account monthly for disputes and fraud. A merchant is identified when it fails a count test and a ratio test in the same month, at levels the networks revise. Identification brings a remediation plan, assessments passed through by the acquirer and, if it continues, termination and a MATCH record. Track your ratio monthly and confirm the current rules with your acquirer.

Visa and Mastercard monitor every merchant account each month for disputes and fraud. Visa ran VDMP for disputes and VFMP for fraud until 2025, when it folded both into VAMP; Mastercard runs ECP, the Excessive Chargeback Program, with a separate fraud program beside it. A merchant is identified when it fails both a count test and a ratio test in the same month. Identification reaches you through your acquirer and brings a remediation plan, network assessments passed through under the merchant agreement, tighter terms on the MID and, if the ratio stays high, termination and a MATCH record. This guide covers the mechanics in general terms and a monthly check of your own numbers; the current thresholds come from your acquirer.

The programs by name, and who they bind

The programs are rules between each network and its member acquirers. You are not a member of Visa or Mastercard; your acquirer is. The network measures the acquirer's merchants, notifies it when one crosses a threshold and bills it for the assessments that follow. Your merchant agreement passes those obligations down: the acquirer may pass through network fines, require a remediation plan and terminate for excessive disputes or fraud. The acquirer's internal thresholds usually sit below the network's, because the acquirer is the party being fined; under VAMP its whole portfolio is tested too, so an acquirer under pressure tightens every merchant at once. How hard to react is the acquirer's call: some add a reserve and a plan, others terminate at the first letter.

How a merchant is identified: a count test and a ratio test

Each network applies two tests to each merchant account, every month. The first is a count: a minimum number of disputes or chargebacks, or a minimum fraud amount under the fraud programs. The second is a ratio: those disputes divided by sales. A merchant is identified only when both are exceeded in the same month. The count floor keeps small merchants out: a few disputes on a few hundred sales make an alarming ratio but not the count. The figures behind both tests are published to acquirers and revised from time to time; treat any number on a public page as historical and ask your acquirer for the current rule. The shape of the test does not change:

• Per network and per program. Visa counts Visa transactions and Mastercard counts Mastercard transactions. Fraud and non-fraud were separate under VDMP and VFMP and are combined under VAMP; Mastercard keeps them apart in ECP and EFM.
• Per month, with different denominators. Visa compares a month's disputes with the same month's sales; Mastercard compares a month's chargebacks with the previous month's sales count. The ratio guide works through the arithmetic.
• Outcome is irrelevant. A dispute you later win is counted in the month it arrived, and a refund issued after the dispute posted does not remove it; the ratio guide explains why.
• Fraud is what issuers report. Visa's fraud measure runs on issuer fraud reports (TC40 data), which arrive before any chargeback; Mastercard's fraud program counts fraud-coded chargebacks.

What identification means for the merchant

The network notifies the acquirer; the acquirer notifies you, by letter or through the ISO that boarded you, with the program, the level and the month. The consequences arrive in the same sequence at both networks:

1. A remediation plan. The acquirer has to show the network that the merchant is being fixed, so it asks you for a written plan with a root cause and dates, and reports your progress monthly.
2. Assessments passed through. The networks bill the acquirer for each identified month, usually after an initial period without fines. The dispute programs have used schedules that grow the longer the merchant stays identified; VAMP bills per dispute above the threshold. The merchant agreement passes the amounts to you, sometimes with an administrative fee on top.
3. Tighter terms on the MID. A larger rolling reserve, a lower processing cap, a settlement delay, or all three.
4. Termination. A merchant identified month after month reaches the point where the network can require the acquirer to stop processing for it; many acquirers terminate earlier. Termination for excessive chargebacks or fraud is a listed reason on MATCH, so the record follows the business and its principals; the MATCH guide covers that file.
5. Exit. Exit is a run of consecutive months below the thresholds, not one clean month; the length is a program rule, so ask your acquirer how it is counted.

What a remediation plan contains

A remediation plan can be forwarded to the network, so it is written for an underwriter: the cause, the fix, the owner and the date, followed by monthly reporting until the ratio is back under the acquirer's internal threshold. Accepted plans are specific:

• Root cause by reason code. Which categories drove the month: fraud, goods not received, cancelled recurring, not as described. Each points to a different fix.
• Descriptor and support. A recognizable billing descriptor with a working phone number or URL, and support that answers before the cardholder calls the bank. The descriptor guide covers the format.
• Refund and cancellation policy. Refunds issued fast on complaint and, for subscription billing, a cancellation path the cardholder can find.
• Pre-dispute alerts and fraud controls. Alert services that let you refund before a dispute posts, paid per alert, and address, card and 3-D Secure checks where fraud is the problem.
• Volume. A voluntary cap, or a pause on the traffic source that produced the disputes. The fastest way to move a ratio is to stop feeding it.

How to track your own ratio every month

You can see an identification coming a month before the acquirer's letter if you read your own numbers the way the networks do. The ratio guide has the weekly routine per MID; this is the monthly check against the program rules, per merchant account:

1. On the first business day of the month, export the previous month's sales count and dispute count by card brand. Keep Visa and Mastercard apart; they are measured apart.
2. Compute the Visa ratio as Visa disputes in the month divided by Visa sales in the same month, and the Mastercard ratio as Mastercard chargebacks in the month divided by Mastercard sales in the month before, in basis points. Record the counts next to the ratios; the count test is half the rule.
3. Ask your acquirer for your Visa fraud report totals and add them to the Visa numerator; VAMP counts fraud reports and non-fraud disputes together.
4. Compare each figure with two lines: the acquirer's internal threshold, from your agreement or your ISO, and the network threshold the acquirer quotes as current. Write both down with the date, because they change.
5. Watch the trend, not the month. Two months of rising ratio at half the threshold is the moment to act; the month the letter arrives is late.
6. Keep the record per MID and per entity; the next underwriter reads the history.

Monitoring programs on a fresh US entity

The programs measure a merchant account, so a new MID on a fresh US entity starts every counter at zero. That is why a merchant who lost a MID to a dispute problem opens the next one on a new entity and a new director rather than on the listed ones. It is not a reset for the business: if the traffic, the offer and the refund policy that produced the disputes come with you, the new MID is identified for the same reason, and that termination is listed with the new entity and its principal. Change the business first; the guide on what happens after a MID termination covers the order.

IBOCore's package fits that picture in a limited way. Each package is a US LLC or C-Corp incorporated in the director's home state, with an EIN, a business bank account at Bluebanc or Relay with full access, and a director, the IBO (Independent Business Operator), qualified in-house with zero criminal record and a credit score of 650 or more, exclusive to one merchant and never used before. The director takes the acquirer's verification calls and compliance queries for the life of the package, including the calls an identification triggers; the plan and the ratio remain yours. IBOCore does not sell chargeback management and gives no legal or tax advice. The documents show the director on the state filing and on the EIN letter; on beneficial ownership reporting, the status at the time of writing is that domestic US companies and US persons are exempt under FinCEN's interim final rule of March 2025, to be verified against current FinCEN guidance.

The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model. If an acquirer terminates the MID there is no clawback from IBOCore; the package stays yours and can be presented to another acquirer, which reads your MATCH record and ratio history first.

Questions merchants ask

What changed when Visa replaced VDMP and VFMP with VAMP?

One program replaced two. VAMP counts issuer fraud reports and non-fraud disputes together in one numerator and divides them by settled Visa transactions in the same month, where VDMP and VFMP measured disputes and fraud separately. It tests the acquirer's whole portfolio as well as each merchant, and it bills enforcement per dispute above the threshold instead of on an escalating monthly schedule. The rollout was staged, with an advisory period and tiers that Visa revises; the tier and ratio that apply to your MID today come from your acquirer, not from a public page.

Who pays the fines, the acquirer or the merchant?

The network bills the acquirer, because the acquirer is the member; the acquirer bills you under the pass-through clause of the merchant agreement, often with an administrative fee on top. Read that clause and the debit authorization before you sign: the amounts are taken from settlements, the reserve or the business bank account of record, in the order the acquirer chooses. A fine is disputed with the acquirer; a merchant has no standing with the network.

How long does a merchant stay in a monitoring program?

Until it has recorded the run of months below both thresholds that the program requires, counted from the last identified month, not from the day the plan was submitted. Each network sets and revises that length, so ask your acquirer for the current exit rule in writing. Assessments in most programs start after an initial period and grow while the merchant stays identified, so an early exit is worth far more than a late one, and a merchant identified again soon after leaving may be treated as a repeat case rather than a fresh one.

Compliance touchpoints that survive audit

Clean setups disclose beneficial ownership, file BOI, use genuine IDs, and keep the IBO informed of website and descriptor changes. Processors re-scan for prohibited products, undisclosed aggregation, and transaction laundering. Violations land on MATCH and kill future MID applications.

• AML / CDD: customer due diligence on the merchant entity.
• PEP screening: politically exposed persons get enhanced review.
• OFAC / SDN: sanctions lists checked on owners and signers.
• Website compliance: refund policy, terms, pricing visible before checkout.

Compliance shortcuts that trigger MATCH

Fake guarantors, borrowed SSNs, cloaked websites, and third-party processing through your MID are the fastest paths to MATCH listings. Recovery requires legal work and years of delay. Disclose, document, and keep the IBO in the loop.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.