Visa's VAMP Is Live: How Small Merchants Stay Under the 0.9% Chargeback Threshold in 2026

If you process 800 Visa transactions a month, just seven customers disputing a charge — even for $15 each — could put your entire merchant account on Visa's watchlist this year. Not because you defrauded anyone, but because Visa stopped counting fraud and disputes separately and started counting them together.

For years, most small businesses shrugged off the occasional chargeback as the cost of taking cards. In late 2025, that math changed. Visa replaced two older monitoring programs with one consolidated program that has tighter thresholds, faster penalties, and far less room for error if you run a low volume. The merchants getting hurt in 2026 are not the large retailers Visa designed the program to police. They are neighborhood restaurants, contractors, online boutiques, and service shops that never realized the threshold dropped to less than one percent.

This guide explains Visa's Acquirer Monitoring Program (VAMP) in plain English, shows exactly how your ratio is calculated, breaks down the four dispute categories that hit small businesses hardest, and gives you a bookkeeping playbook to keep your ratio low, your fees clean, and your processor from putting you on the defensive.

What Changed: VAMP in One Paragraph​

VAMP — the Visa Acquirer Monitoring Program — went live in Europe on April 1, 2025, rolled out globally through 2025, and replaced Visa's two legacy programs: the Visa Fraud Monitoring Program (VFMP) and the Visa Dispute Monitoring Program (VDMP). Instead of tracking fraud and disputes on separate tracks with separate thresholds, VAMP rolls them into a single metric: your VAMP ratio.

VAMP ratio = (TC40 fraud reports + TC15 non-fraud disputes) ÷ total settled Visa transactions

TC40 is the Visa fraud reporting stream — every time an issuing bank flags a transaction as fraudulent, even if no formal dispute is filed. TC15 is the non-fraud dispute stream — the traditional chargebacks for "I didn't get my order," processing errors, and similar reason codes. Visa now adds both numerators together and divides by your total settled Visa transaction count. Cross the threshold and your acquirer — the bank that processes for you — gets penalized by Visa. Those penalties flow through to you as higher fees, a remediation plan, or in serious cases, account termination and placement on the MATCH list.

Two other important details: Mastercard runs a separate program with different thresholds, and American Express has its own. This guide focuses on Visa, because Visa's new combined metric is the one that moved most in 2026 and is catching small merchants by surprise.

The 2026 Thresholds That Actually Matter​

VAMP uses phased thresholds so merchants and acquirers had time to adjust, but the tightening is now fully in effect. The figures below reflect Visa's published schedule as summarized by acquirer documentation and Checkout.com, Sift, and Visa's own bulletins.

Some processor summaries phrase the pre-2026 merchant threshold as 1.5% and the 2026 threshold as 0.9%, with acquirer thresholds tightening from 0.5% to 0.3% for "Above Standard." You may also see an older 2.2% figure from the initial rollout period — that was the launch runway before the step-down to 1.5% took effect.

Visa also applies a minimum volume gate: you generally need at least 1,000 combined TC40 + TC15 events in a month for the ratio to trigger formal program placement (some acquirers describe this as 1,000 disputes/fraud reports on at least 1,000 transactions). In practice, that gate protects the smallest merchants from a single dispute blowing up a ratio, but it does not protect a merchant who processes 800 to 1,200 transactions a month and accumulates even a handful of fraud reports and disputes.

Quick math: If you process 1,000 Visa transactions in a month:

• 5 disputed or fraudulent transactions = 0.5% — your acquirer is now "Above Standard" and watching you more closely.
• 9 transactions = 0.9% — you are "Excessive" as a merchant and enter the penalty track.
• 15 transactions = 1.5% — under the old threshold, this was the line; now it is well into the penalty zone.

If you process 2,500 transactions, your room is 22 disputes before you hit 0.9%. If you process 600, your room is only five. Low volume is not an exemption — it is a multiplier on risk.

The Enumeration Ratio Is Separate — But Worth Knowing​

VAMP also introduced a card-testing metric. If Visa identifies at least 300,000 enumeration attacks — automated bot attempts that test stolen card numbers on your checkout — and those attacks represent 20% or more of your total transaction volume, you are flagged under the excessive enumeration track. Most brick-and-mortar businesses will never hit 300,000 attempts, but any small online store with a public checkout page and no bot protection can be probed thousands of times in a single attack. Enumeration is tracked separately from your VAMP fraud-plus-dispute ratio, but both roll up to your acquirer's oversight and both require monitoring.

The Four Chargeback Buckets That Hit Small Businesses​

Almost every small-business chargeback falls into one of four categories. Knowing which bucket a dispute sits in changes both your prevention strategy and your chance of winning it.

1. Friendly Fraud (First-Party Fraud)​

The customer received the goods or services and disputes the charge anyway. Sometimes it is a spouse who does not recognize the descriptor, sometimes a customer who forgot about a subscription renewal, sometimes a deliberate refund hunt after a return window closed. Industry studies now estimate friendly fraud accounts for 45% to 75% of all chargebacks, with Mastercard reporting that merchants identify roughly 45% of chargeback volume as fraudulent in 2025 and Chargebacks911 finding that more than 83% of enterprise merchants reported rising friendly fraud into 2026. For small businesses, the share is often 40–50%.

This is the most winnable category when you have documentation — and the most frustrating when you do not.

2. True Fraud (Third-Party Fraud)​

The card was stolen or compromised; the cardholder did not make the purchase. You will see this most in card-not-present transactions: online orders, phone orders, and any purchase where the chip was not read. You are not the fraudster, but you are still liable for the transaction if your fraud controls are not documented.

3. Service Not Received or Not as Described​

Common with deposits, service plans, contractors billing before delivery, prepaid appointments, and any business that bills before the work is complete. Often this is less a complaint about quality and more a documentation failure — the customer disputes because you cannot prove when the service was delivered or what was agreed to.

4. Processing Errors​

Duplicate charges, wrong amount charged, credit not processed, or a refund that posted late. The easiest category to win and to prevent entirely with cleaner procedures.

Understanding the bucket matters because Visa reason codes map to different evidence requirements. A fraud-coded dispute with a 3D Secure authentication looks very different to an acquirer than the same fraud code without it.

Why Small Merchants Get Caught Faster​

Large retailers could absorb a 0.9% threshold across millions of transactions. Small businesses feel it differently:

Denominator risk. If you do 900 transactions a month, each dispute is 0.11% of your ratio. Four friendly-fraud disputes plus two true-fraud flags and you are at 0.67% — already above your acquirer's watch line. A restaurant with 2,000 covers or a plumber with 150 invoices has less statistical cushion than a chain with 200,000 swipes.

Acquirer pass-through. Visa fines your acquirer, not you directly. But your merchant agreement lets the acquirer pass through fines, raise your discount rate, impose a rolling reserve (holding back 5% to 10% of your settlements for 60 to 180 days), or demand a remediation plan you must document monthly. Small merchants rarely have a dedicated risk contact to negotiate this.

Card-not-present exposure. If you take phone orders, send invoices with a pay link, or run an online store without address verification (AVS), CVV checks, or 3D Secure, you are in the highest-risk transaction category for both fraud and disputes — yet many small businesses have none of those controls turned on.

No response team. Studies consistently show merchants win roughly 45% of disputes when they respond at all, with non-fraud disputes winning closer to 56% and fraud-coded disputes closer to 36%. Merchants who use their acquirer's risk team and respond within 24 hours with a complete evidence pack win 60% to 70% of eligible disputes. Solo merchants who handle it themselves, late and with partial documentation, win closer to 20%. In a 0.9% world, that win rate is not just lost revenue — it is a higher VAMP ratio because unchallenged or poorly defended disputes still count.

The True Cost Hiding Behind a $75 Chargeback​

A $75 dispute never costs $75. Track the full stack:

• The transaction reversal: $75 credited back to the cardholder.
• The chargeback fee: $15 to $100 per dispute depending on your processor and program status; higher if you are already in VAMP.
• The processor penalty: $8 per dispute for merchants in the excessive track, with escalating monthly fines for sustained breaches and additional fines to your acquirer that become your rate increase next quarter.
• The merchandise or labor: The food you served, the shirt you shipped, the three hours your tech spent on site. You cannot reclaim it.
• The operational cost: Industry data pegs the average processing cost of a single chargeback at about $78 before you count the product, and LexisNexis estimates U.S. merchants lose $4.61 for every $1 of fraud when fees, time, and lost goods are included.
• The ratio cost: Every dispute and every TC40 fraud report — whether you win or lose — was counted in your VAMP numerator at the time it was filed. Winning a dispute gets your $75 back, but it does not erase the numerator hit. Prevention is the only real lever.
• The existential cost: Sustained excessive status can lead to a MATCH listing, which makes it difficult to open a new processing account with any acquirer for up to five years.

In your books, that $75 chargeback plus a $25 fee is not $100 of "fees." It is a reversal of revenue, a bank fee expense, and a hit to a compliance ratio that can raise your cost of accepting cards for months. Book it wrong and you will understate both your true margin and your risk.

10 Things to Do This Week to Lower Your Ratio​

None of these controls are exotic. All of them were flagged as effective by processor risk teams reviewed for this guide.

1. Use a Clear, Recognizable Billing Descriptor​

Your statement descriptor should match the name on your storefront, website, or invoice. "SMITHENT LLC #04412 POS" gets disputed; "Smith Plumbing Charleston SC" does not. If you operate multiple DBAs, set a descriptor per location.

2. Capture a Signature or Written Order Confirmation​

For any sale over your average ticket — especially contractor estimates, event deposits, and B2B orders — get a signed work order, emailed approval, or checkout checkbox with the total, scope, and cancellation terms. Even a tablet signature defeats most "I didn't authorize this" disputes.

3. Email a Detailed Receipt Automatically​

Customers who receive a clear receipt within minutes of payment, with itemized charges, tax, tip, and a support phone number, almost never file a dispute. Make it automatic from your POS or invoicing tool, not manual.

4. Require CVV and AVS for Every Card-Not-Present Transaction​

Both are basic fraud filters and both are evidence at dispute time. Declining a transaction that fails CVV or AVS is far cheaper than eating a fraud chargeback.

5. Turn On 3D Secure (Visa Secure)​

For online checkouts, 3D Secure prompts the cardholder for an extra authentication step and, on most fraud disputes, shifts liability from you to the issuing bank. It is free to enable through your gateway, and the small amount of friction is far less costly than a VAMP hit.

6. Tokenize Card-on-File​

If you store cards for repeat customers, subscriptions, or house accounts, use gateway tokenization rather than storing raw card numbers. Tokenization reduces your PCI scope and creates cleaner dispute evidence because the token history ties the cardholder to prior legitimate transactions.

7. Refund Quickly When Customers Ask​

A $100 refund is cheaper than a $100 dispute, a $25 chargeback fee, and a 0.1% hit to your VAMP ratio. Do not fight small disputes on principle. If the customer asked for a refund and you can grant it, do it before they call their bank. Many issuers now count refunds issued within a short window as reducing dispute risk.

8. Document Service Delivery​

Photos of completed work, signed delivery receipts, GPS check-ins for field jobs, appointment no-show logs, and time-stamped completion emails are all valuable when you defend a dispute. For service businesses, a before-and-after photo attached to the invoice is the single best piece of evidence.

9. Train Staff on Refund Policy​

Most disputes start as a phone call that was not handled well. A clear, generous refund policy that front-line staff are empowered to execute promptly cuts disputes by 30% to 50% at small businesses that track it. Put the policy on your receipt, on your website, and at the register.

10. Watch Your Ratio Monthly — Demand the Dashboard​

If your processor dashboard does not show you a dispute rate, a fraud rate, and a combined VAMP-relevant ratio in real time, that is a problem in 2026. Ask for it. Track two numbers in your own books at month-end: (disputes + fraud reports) ÷ settled Visa transactions. If you are above 0.5% for two months running, treat it as a priority, not a curiosity.

When You Do Get a Chargeback: Respond, Don't Ignore​

You usually have 7 to 21 days to respond, depending on the reason code, and the evidence must be uploaded in a specific format your acquirer dictates. Do not wing it from your inbox.

A strong response pack includes:

• The signed order, contract, or online checkout confirmation
• The itemized receipt and proof of delivery or service completion
• CVV/AVS results and any 3D Secure authentication data
• Prior undisputed transaction history with the same cardholder
• Any customer communication (emails, texts, call logs) showing they received or acknowledged the purchase

Submit through your acquirer, not directly to Visa. A risk team that helps you build the pack and files within 24 hours wins at roughly twice the rate of a merchant filing alone. Even when you win, remember: the filing itself already counted toward your VAMP ratio for that month. Use the win to recover funds, but fix the underlying cause so the next transaction does not create another filing.

Bookkeeping: How to Track Chargebacks Without Blinding Yourself​

In 2026, chargeback accounting is not just a bookkeeping chore — it is your early-warning system for VAMP. If your processor settles net and you only book net deposits, you will never see your ratio rising.

Build the Right Chart of Accounts​

Create separate general-ledger accounts rather than dumping everything into "bank fees":

• Sales — Gross Visa (income, for total authorized sales before any deductions)
• Sales — Contra Revenue: Chargeback Reversals (contra-income, for the original sale amount when a dispute is charged back — keeping gross sales accurate)
• Processing Fees — Chargeback Fees (expense, for the $15–$100 fee per dispute)
• Processing Fees — VAMP or Monitoring Penalties (expense, for any excessive-track fines your acquirer passes through)
• Accounts Receivable — Processor Holds / Rolling Reserve (asset, for funds your acquirer holds back as a reserve — not yet available cash)
• Other Income — Chargeback Reversals Won (income, for disputes you successfully defended and had re-credited)

Some accountants prefer to book chargeback reversals as a debit to cash and credit to the contra-revenue account. Either approach is defensible if applied consistently — what matters is that you do not bury the reversal in a generic "refunds" account where it disappears from your monitoring.

Reconcile Gross, Not Net​

Your processor gives you a daily settlement file. Reconcile it this way:

1. Record gross sales per the processor's authorized-batch total.
2. Record fees separately — discount rate, interchange pass-through, batch fees, monthly fees.
3. Record chargeback debits and credits separately — the reversal and any fee on the day they hit.
4. Record reserve holds and releases — a hold is a transfer from cash to the reserve asset, not an expense; a release is the reverse.
5. Match to bank deposits — the net deposit should equal gross sales minus all fees, reserves, chargebacks, and adjustments. If it does not, you are missing a line item.

If your processor only provides a net deposit without a detailed batch file, request the full settlement report. In a 0.9% world, gross-to-net without detail is not bookkeeping — it is a blindfold.

Reserve for What You Know Is Coming​

If your trailing three-month VAMP ratio is 0.6% or higher, accrue a reserve. Estimate next month's chargeback-related cash outflow as: expected disputes × (average ticket + average fee) + any known acquirer penalties or rolling-reserve hold percentage. Book the reserve as an expense and a liability, then relieve it when actual chargebacks post. This keeps a spike month from wrecking your cash forecast and makes the cost of disputes visible to you before it surprises your bank account.

Mind the 1099-K Gap​

Your Form 1099-K reports gross payment-card volume — before fees, chargebacks, and reserves. Your books should show gross sales far closer to the 1099-K than to net deposits. If your gross card sales in the ledger are far below the 1099-K total, you are likely booking net deposits as revenue, which understates both income and the fee expense. Reconcile the 1099-K to your gross-sales account at year-end; the difference should be a clean tie-out of documented fees, refunds, and chargebacks.

Track Two Ratios Outside Your Processor​

Even if your dashboard shows a VAMP ratio, keep your own:

• Monthly VAMP ratio: (TC40 reports + TC15 disputes) ÷ settled Visa transactions. Get TC40 counts from your processor — many merchants only track TC15 and miss half the numerator.
• Dispute loss rate: Dollars lost to disputes ÷ gross Visa sales. Track by category (friendly fraud, true fraud, service, processing error) so you know which fix moves the needle most.

Review both at the same meeting where you review bank reconciliation. A ratio is just another KPI.

Stay Off Visa's Radar Without Slowing Down Sales​

Visa did not design VAMP to punish a bakery that had two forgetful customers in one month. But the program is automated, threshold-based, and acquirer-enforced — which means your acquirer will act on the numbers before it asks for the story behind them. The most effective small businesses in 2026 are doing three things consistently:

They prevent more than they dispute. The fastest way to cut a ratio is to stop the dispute at the customer-service step. Fast refunds, clear descriptors, and automatic receipts prevent more filings than any evidence pack recovers.

They authenticate the risky transactions. 3D Secure on online checkouts, CVV and AVS on phone orders, and signed authorizations for large tickets do not just prevent fraud — they create the evidence you need when fraud happens anyway.

They book like they mean it. Separate accounts for reversals, fees, and reserves; daily gross-to-net reconciliation; and a monthly ratio review tied to the same books you use to price, staff, and plan. When a ratio creeps from 0.4% to 0.7% over two months, the books — not a letter from your acquirer — should be the first place you see it.

Enumeration protection deserves the same discipline if you sell online: rate limiting on your checkout, bot filtering through your gateway, and a CAPTCHA on payment pages cost little and keep you far below the 300,000-attempt, 20% threshold that most small businesses will never see — unless they have no protection at all.

Simplify Your Financial Management​

Staying clear of VAMP thresholds is ultimately a visibility problem: tracking disputes against volume, reconciling processor settlements gross-to-net, and spotting a risky month before it becomes a penalty. Beancount.io gives you plain-text accounting that is transparent, version-controlled, and AI-ready — so your chargeback, fee, and reserve history lives in one auditable ledger you control. Explore the docs to set up a merchant-friendly chart of accounts, use Fava to watch monthly ratios alongside cash flow, and get started for free when you are ready to turn payment data into a real early-warning system.