Visa MERP Asia-Pacific: What Merchants Must Watch

The short answer: Visa's Merchant Elevated Risk Program (MERP) identifies individual merchants in Asia-Pacific whose activity shows elevated risk — early, before their volumes are large enough to trip portfolio-level monitoring programs. Visa evaluates several signals together and does not publish the thresholds it uses, so there is no MERP number you can calculate your way under. What you can do is watch the signals themselves: fraud and dispute rates, decline rates, and abnormal spikes in activity, especially on new accounts or new product lines.

What MERP is — and the date to note

MERP is Visa's program for spotting deceptive or high-risk merchant activity in the Asia-Pacific region. Visa's Singapore Security Roadmap describes its aim plainly: to target objective elevated merchant-risk activity and offer an avenue for liability reversal and reimbursement for issuers and cardholders, concentrating on high-confidence cases of deceptive activity that show up as smaller-scale, disproportionate fraud or dispute rates or abnormal spikes in activity. Its stated goals include identifying merchants whose fraud and dispute rates, decline rates or abnormal spikes demonstrate excessive risk, and improving acquirer controls and oversight.

One date needs care. Visa's April 2026 Core Rules introduced MERP for the AP region, effective 9 April 2026, with the identification and non-compliance rules sitting in sections 10.4.4.4 and 12.5.8.1 of that edition. Stripe's monitoring documentation, the version most Stripe merchants actually encounter, describes MERP as effective October 2026 for businesses accepting Visa in Asia-Pacific. Treat October 2026 as the enforcement wave merchants are feeling now, and the April 2026 rulebook as the program's origin — not as two different programs. If your acquirer cites MERP, ask which notice and date it is relying on.

The signals Visa watches

Stripe's monitoring documentation lists the signals Visa considers when identifying a business under MERP, and stresses that Visa evaluates them together rather than against individual thresholds. No single figure below is a published tripwire — that is the whole point of the program, and any article quoting a MERP threshold as fact is inventing it:

Transaction count and volume — how much you process, and how fast it changes.
Fraud volume and fraud rate — reported fraud, not just fraud chargebacks.
Non-fraud dispute volume and dispute rate — consumer disputes as well as fraud claims.
Authorization count and decline rate — early declines are a signal in their own right, not just a sales problem.

Visa's own framing adds the pattern that ties these together: disproportionate rates at small scale, and abnormal spikes. A new account or a new product line doing modest volume with a high fraud or dispute rate is exactly the profile MERP was built to catch early — before the merchant is big enough for a portfolio program to notice.

What identification can trigger

Stripe's documentation describes the sequence: Visa notifies Stripe when it identifies a business under MERP, and if the account is still active, Stripe contacts the merchant. Response timelines are short, so a slow reply can cost the chance to contest the identification. If Visa confirms it, the consequences can include:

Network non-compliance assessments charged to Stripe, which may be passed on to the merchant.
Backdated fraud disputes: during a specific window, Visa lets issuers submit fraud disputes for earlier transactions, including transactions past the standard dispute deadline — so payments you considered settled can come back.
A remediation plan documenting the controls you put in place to address the activity Visa identified.
Account closure in some circumstances.

Under Visa's April 2026 rules, acquirers that fail to refute an identification face non-compliance assessments and Dispute Condition 10.5 (Visa Fraud Monitoring Program) on eligible transactions. That is why your acquirer has its own strong incentive to act fast — and why a merchant that answers quickly, with evidence, is in a better position than one that waits.

How MERP sits beside VAMP and Stripe's 0.75% line

Three different yardsticks, three different jobs:

VAMP (Visa Acquirer Monitoring Program) is the portfolio-level program. Since 1 April 2026, a merchant in Asia-Pacific, Canada, the EU, the US or Latin America is flagged Excessive at a combined fraud-plus-dispute ratio of 1.5% with at least 1,500 counted fraud reports and disputes in the month. VAMP counts fraud reports (TC40) plus disputes (TC15) against settled card-not-present transactions. Below 1,500 events in a month, VAMP's merchant tier does not engage — which is precisely the gap MERP fills.
MERP is individual and early. It evaluates one merchant's signals together, with no published thresholds and no minimum-volume floor in the public descriptions. Staying under VAMP's 1.5% does not keep you safe from MERP, and a clean VAMP report is not evidence about MERP.
Stripe's 0.75% line is the industry-standard marker for excessive dispute activity in Stripe's own measuring-disputes documentation: dispute activity above 0.75% is recognised as excessive, but a sudden spike or steep upward trend can trigger placement in a monitoring program before the rate reaches 0.75%. Stripe also notes that all disputes, won or lost, count toward the dispute rate. Treat 0.75% as Stripe's early-warning line, not as a Visa threshold — and remember your processor can act on its own rules well before any network program does.

The practical reading: VAMP is the line you can compute, Stripe's 0.75% is the line your processor watches, and MERP is the judgement call Visa makes on your pattern. A merchant watching only one of the three is exposed on the other two.

What to watch and do now

Track the MERP signals weekly, not monthly: fraud rate, dispute rate, decline rate and volume spikes, split by new accounts and new product lines. A spike on a new line deserves a same-week look, not a month-end review.
Treat early declines as a risk signal, not just lost sales. A rising decline rate alongside rising fraud or disputes is the pattern MERP describes.
Resolve disputes before they post where you can. Pre-dispute resolution keeps cases out of monitoring counts; winning a filed dispute recovers revenue but does not remove it from the count.
Tighten the new-line launch checklist: clear descriptors, honest product descriptions, working cancellation and refund paths, and fraud screening before fulfilment. Most early MERP signals are preventable at launch.
Answer any Stripe or acquirer MERP enquiry immediately, in writing, with evidence. Timelines are short, and the acquirer's ability to refute the identification depends on what you send.
Ask your acquirer, in writing, which program any notice refers to — MERP, VAMP or a processor-internal review — and what figures it is using. The three programs have different thresholds, different consequences and different defences.

FAQ

Is there a MERP threshold I can calculate and stay under?

No. Visa does not publish MERP thresholds, and Stripe's documentation states explicitly that Visa evaluates the signals together rather than against individual thresholds. Any source quoting a MERP percentage as fact is guessing. Watch the signals — fraud rate, dispute rate, decline rate and spikes — instead of chasing a number.

Does staying under VAMP's 1.5% keep me safe from MERP?

No. VAMP's Excessive tier needs 1.5% plus at least 1,500 counted events in a month. MERP is designed to catch elevated risk before volumes reach that scale, evaluating one merchant at a time. A clean VAMP report says nothing about MERP.

What happens if Visa identifies my business under MERP?

Visa notifies your processor, which contacts you if the account is still active. If confirmed, consequences can include non-compliance assessments passed through to you, backdated fraud disputes for earlier transactions, a required remediation plan, and in some circumstances account closure. Respond promptly and in writing — timelines are short.

I am a small merchant. Can MERP really catch me before VAMP does?

Yes — that is its design. MERP targets smaller-scale, disproportionate fraud and dispute rates and abnormal spikes, evaluated merchant by merchant, rather than waiting for portfolio-level volumes. Small volume with a high rate is the profile it was built for, especially on new accounts and product lines.

Visa’s New Merchant Elevated Risk Program (MERP) in Asia-Pacific — and Stripe’s 0.75% Dispute-Rate Watch

On this page