A small peptide store can sit at a 3% ratio and never appear in Visa's Excessive tier, yet still get a reserve or termination letter from its processor. That is because Visa's Excessive merchant tier only applies once a merchant logs at least 1,500 fraud reports and disputes in a month, a floor a store doing a few hundred orders a month will never reach.
Reading that as safety is a mistake, because your processor acts on its own rules long before Visa names you. Pick an internal warning line well below Visa's published merchant level, agree the exact figure with your processor, count events the way Visa does, and tie every counted event to a WooCommerce order you can explain.
What replaced VDMP and VFMP?
VAMP is the Visa Acquirer Monitoring Program. It consolidated the older VDMP (the dispute program) and VFMP (the fraud program) into one framework. Visa sets out the program in its Visa VAMP fact sheet. The new thresholds took effect on June 1, 2025, and the advisory period ended on September 30, 2025. A processor still talking about separate VDMP and VFMP tiers is using old language.
A quick note on the query. "Visa vamp" is what founders type into search. "Visa VAMP" is what processors and risk teams say. It is not a payment gateway, and it does not automatically close small merchants. It is a monitoring framework for card-not-present activity on VisaNet.
Visa assesses the acquirer's portfolio first. Pressure then flows down through the acquiring bank and the payment processor to you. That means your contract with your processor, not a letter from Visa, is where most consequences land: reserves, limits, remediation demands and termination.
This post is about ratios. If you want the separate topic of what you sell and how Visa classifies it, read our earlier post on the Visa Integrity Risk Program.
Peptide Marketing HQ is a small hands-on agency for research-use-only peptide suppliers. We build WooCommerce stores ready for processor underwriting and set up high-risk payment processing with a backup route. We also tell every client to read their own ratio every month.
How the Visa VAMP ratio is counted
Visa's formula, from its VAMP fact sheet, has three parts:

- TC40: fraud reports that issuers send to Visa.
- TC15: disputes (chargebacks) raised against a transaction.
- TC05: settled card-not-present sales transactions.
The ratio is TC40 plus TC15, divided by TC05. It counts events, not dollars. One small dispute weighs the same as one large one, so a store with low dollar losses can still post a poor ratio. Visa excludes disputes resolved through pre-dispute tools and fraud reports that qualify for Compelling Evidence 3.0.
Worked example (hypothetical)
This is an invented store used only to show the arithmetic. It is not a client. We ask stores to build one row per descriptor, one sheet per month, from their processor report:
- Descriptor: the exact billing descriptor as it appears on statements.
- TC05: settled Visa card-not-present transactions for the month.
- TC40: fraud reports received for that descriptor.
- TC15: disputes received for that descriptor.
- Events: TC40 plus TC15.
- Ratio: Events divided by TC05.
Now fill in the row. Say the store settles 400 Visa card-not-present transactions in a month (TC05 = 400). It receives 3 fraud reports (TC40 = 3) and 2 disputes (TC15 = 2). That makes 5 events, and 5 divided by 400 is 1.25%.
Read that 1.25% against three lines. It is below Visa's merchant Excessive line of 1.5%, and 5 events is nowhere near the 1,500-event floor, so Visa's merchant tier does not apply. It is also above 0.5%, the level at which Visa rates an acquirer's whole portfolio as Above Standard.
It is also above your own 0.5% warning line, which is the one you can act on. Two events fewer would bring this store to 0.75%, still over the line.
Two questions most guides skip
Does a TC40 count if the customer never files a chargeback? Yes. Fraud reports are counted in the numerator even without a dispute, which is a big reason this differs from a chargeback rate you track yourself.
Can one transaction produce both a fraud report and a dispute? The sources we have do not settle how overlap is handled. Ask your acquirer how it deduplicates, and get the answer in writing.
Why it is not a chargeback rate
A classic chargeback rate counts disputes only, usually against all transactions. The VAMP ratio adds fraud reports to the numerator and uses only settled card-not-present Visa transactions as the denominator. Your own dashboard figure will not match it.
Visa VAMP thresholds and dates as published
Here is what the cited sources report, each with its date.
- Merchant Excessive (US, Canada, Europe and Asia Pacific): 1.5% with at least 1,500 combined fraud reports and disputes in a month. Visa lowered this from 2.2% on April 1, 2026. Other regions differ, so check the Visa VAMP fact sheet for yours.
- Acquirer portfolio levels: Above Standard at 0.5% and Excessive at 0.7%, measured across the acquirer's whole portfolio. Your processor may also set stricter levels of its own, so ask for them in writing.
Per-event fees reach merchants only through the acquirer contract and vary by agreement. For a small store, the consequences that bite are contractual: the reserve percentage, the length of any rolling hold on payouts, and the termination notice terms in your processing agreement. Find those clauses now, before a warning arrives.
Why the 1,500 floor does not protect you
A store with a few hundred orders a month is unlikely to hit 1,500 events. But acquirers set their own reserves, limits and termination rules below Visa's merchant threshold. The acquirer's own portfolio has a 0.5% Above Standard line, and your processor has every reason to manage accounts that push it up.
That is why we recommend 0.5% as the internal warning line. It is a rule of thumb, not a published processor policy. We borrowed it from the acquirer-level Above Standard line, and we have not found a processor that fixes a merchant action at exactly 0.5%.
What a processor can do when an account drags its portfolio up is written in your contract: demand a remediation plan, add or raise a reserve, extend a rolling hold on payouts, or end the agreement on notice. Read those clauses, because the percentages and lengths sit there.
Waiting for 1.5% means waiting for the last warning.
Card testing is a separate metric
Visa also tracks enumeration, which is the bot behavior behind card testing. We have not confirmed the current enumeration thresholds against Visa's own page, so we do not quote them here. Ask your processor for the exact figures. The bot behavior behind it still hits small stores, so we cover the defenses in our card testing post.
Reconcile Visa VAMP data against WooCommerce orders
Do not rely on WooCommerce alone. Your processor holds the TC40 and TC15 counts, and they are the numbers that matter. Run this workflow every month:

- Ask the processor for TC40 and TC15 reports, plus settled Visa card-not-present counts by descriptor.
- Match each event to a WooCommerce order, refund, shipping record and help-desk ticket.
- Separate fraud reports, fraud chargebacks, non-fraud disputes, refunds and declines.
- Tag each event with one root cause: true fraud, did not recognize the charge, not received, or refund dispute.
- Total each cause and rank them.
Find the fixable clusters
Five clusters are worth checking first.
- Descriptor mismatch: a statement line that shows a holding-company name, such as "Northfield Holdings LLC", while the storefront shows a different brand name, causes "I don't recognize this" claims. Our billing descriptor audit covers this in detail.
- Slow tracking: late tracking updates cause "not received" claims.
- Vague refund terms: unclear terms push customers to their bank instead of your inbox.
- "Not as described" claims: a certificate of analysis that carries a batch number different from the one on the product page or vial label invites exactly this dispute. So does an invoice that words the product differently from the page.
- Buyer's remorse on research purchases: a customer who regrets an order and finds no clear refund path may go straight to a dispute.
In our experience the batch-number and wording mismatch is the fastest fix. It is a content edit you control today, with no processor sign-off. Descriptor changes go through your processor and take longer, and changing one mid-review can look like evasion. Raise any descriptor fix with your processor before a review starts, or wait until it closes.
The point of the tagging is to find real causes. It is not to massage the numbers or to argue events out of the count.
Build the evidence pack before you need it
A processor running an underwriting or risk review will ask for the same things each time:
- Order and fulfillment proof, including carrier tracking and delivery confirmation.
- Customer-support history for disputed orders.
- Your refund policy as it stood on the order date.
- Product page, label and invoice wording that matches what you actually ship.
For research peptide stores, ambiguity in wording creates disputes. Intended-use language should be the same on the product page, label and invoice, and it must match how you actually sell. No page should carry health, dosing or effect claims. Our compliance review for research peptide stores checks exactly this wording. For the dispute-response side, see our post on peptide chargeback prevention.
A 30-day plan after a Visa VAMP warning
A warning from your processor is a data request, not a verdict. Here is the sequence we use.
Week 1
- Answer the processor's data request quickly and honestly.
- Freeze changes to descriptors and product categories. Changing them mid-review looks like evasion.
- Build the root-cause map from the reconciliation step.
Weeks 2 and 3
- Fix checkout and fulfillment causes from the map.
- Tighten fraud screening on checkout.
- Add dispute and fraud alerts where your processor supports them. Ask whether Verifi Order Insight, Rapid Dispute Resolution (RDR) and Compelling Evidence 3.0 are available to you. Disputes resolved through RDR and fraud reports that qualify for CE3.0 are left out of the VAMP ratio.
- Rewrite order confirmation, tracking and refund emails so customers recognize the charge and know where their order is.
Week 4
- Set up monthly ratio tracking with the 0.5% internal line.
- Assign one named owner.
- Send the processor a short written remediation summary.
The hard line
We never suggest splitting volume across accounts, miscoding, or hiding product types from an acquirer to dodge monitoring. That is transaction laundering. It ends accounts and can lead to a merchant being listed. We will not help with it, and no ratio is worth that risk.
Backup routes that hide nothing
A disclosed backup route is a second processor that knows your business, your products and your descriptors. A prohibited route is built to evade monitoring or to conceal what you sell. The first is resilience. The second is the reason accounts get terminated.
Payment orchestration can legitimately give you redundancy, retries and failover to an approved second acquirer. It must not shift volume to keep a ratio low at one processor while hiding the problem. It must not use inconsistent descriptors either.
Each acquirer runs its own VAMP exposure. A backup route keeps you selling if the primary account is restricted, but it does not repair a poor ratio. The repair is the root-cause work above. A second processor will see the same disputes, and it will ask the same questions at underwriting.
If you want a second pair of eyes on your TC40/TC15 reconciliation and evidence pack, send them with a request for the free store audit, or start from our peptide payment processing page.
Frequently asked questions
What does Visa VAMP stand for?
VAMP stands for Visa Acquirer Monitoring Program. It consolidated the older VDMP and VFMP programs into one monitoring framework for card-not-present activity, with pressure flowing through acquirers and processors.
How is the VAMP ratio calculated?
Visa's formula adds TC40 fraud reports and TC15 disputes, then divides by settled card-not-present TC05 transactions. It counts events, not dollars, so every event weighs the same.
What is the Visa VAMP threshold for US merchants?
The Excessive Merchant threshold is 1.5% with at least 1,500 counted events in a month, lowered from 2.2% on April 1, 2026 (Visa VAMP fact sheet). Acquirers can apply stricter rules to your account below that level.
Can a small store ignore VAMP because of the 1,500-event minimum?
No. The minimum applies to Visa's merchant-level classification. Your acquirer can still set reserves, limits or termination rules at lower levels, which is why we use 0.5% as an internal warning line.
Does a fraud report count without a chargeback?
Yes, TC40 fraud reports count in the numerator even if no dispute follows. How overlap between a TC40 and a TC15 on the same transaction is handled is something to confirm with your acquirer.

