Mastercard GMAP explained: a practical guide for payments operators
Mastercard GMAP monitors merchant and acquirer fraud and disputes to identify risky activity and prompt corrective action. Before April 2027, payments operators should reconcile fraud reports, chargebacks and refunds separately, calculate ratios using the correct months, and confirm monitoring scope and exclusions with each provider.
In this article
A customer receives a refund. Your team closes the alert. The fraud report can still count in Mastercard’s monitoring data.
GMAP is Mastercard’s program for monitoring merchant and acquirer fraud and disputes, helping identify risky activity and prompt corrective action. [1]
Its full name is the Global Merchant Audit Program. For payments operators, the practical task is to understand which records count and resolve the causes behind them.
The revised standards take effect on 1 April 2027. Initial billing follows in May for April activity. Existing monitoring continues alongside new combined fraud and dispute categories. [1]
For a subscription merchant using several processors, preparation starts with one question: can you reproduce the calculation for each monitored merchant?
Start with the payment records
A refund, a fraud report and a chargeback describe different events. A single payment can have more than one of these records.
- Refund
- The merchant initiates a return of funds for a purchase. A submitted refund does not prove the customer received it.
- Fraud report
- A record identifying a transaction reported as fraudulent. It does not automatically mean a chargeback occurred.
- Chargeback
- The card issuer returns a disputed transaction through the card network’s process. This is separate from a merchant refund.
- Clearing
- Payment records are exchanged and validated to establish payment obligations. Clearing is separate from money reaching the merchant’s bank account.
- Acquirer
- The institution acting for the merchant in acquiring card transactions.
- Processor
- The service processing payment messages. A processor is not automatically the acquirer.
In this article, an eligible record means a record included after the applicable exclusions and adjustments. Reconciliation means comparing your calculation with the processor’s report and explaining each difference.
Why can refunded fraud still count
Mastercard’s clarification distinguishes a reported fraud transaction from a chargeback that is reversed or refunded before the reporting month closes. Fraud submitted to its Fraud and Loss Database remains relevant to the amount and count calculations. [2]
For chargebacks, Mastercard says a reversal or refund before the reporting month ends removes the item from the chargeback count. [2] The processor still needs to explain which event and adjustment its report recognises.
An alert is a notification to investigate or resolve a payment issue. Ethoca is one alert service discussed in the Mastercard clarification.
An Ethoca refund therefore needs two checks. Confirm the refund outcome. Then check whether Mastercard received a fraud report for that transaction.
Keep the alert, refund, fraud report and chargeback as separate linked records. Record their dates and reporting months. Ask the processor to trace one refunded transaction through its monthly extract.
One payment, two records
ILLUSTRATIVE · SOURCE [2]CUSTOMER REFUND
Refund completed
Confirm the refund outcome.
MASTERCARD FRAUD REPORT
Reported fraud can still count
Check the fraud report separately.
Exclusions depend on classification
Mastercard’s clarification says first-party fraud and First-Party Trust codes are excluded from its programs. [2] It does not separately establish a blanket exclusion for every case resolved through Ethoca or Collaboration.
Mastercard describes first-party fraud as a genuine purchase later claimed as fraud. The claim can arise from confusion or intentional misuse. A customer-service label such as “friendly fraud” does not establish the applicable Mastercard code.
The important distinction is between how a case was resolved and how Mastercard classified it. A refund through a particular service does not establish that classification.
Request the eligible exclusion codes from each processor. Record the affected program and the evidence supporting each exclusion. Keep excluded records available for reconciliation.
Visa’s Acquirer Monitoring Program, or VAMP, is a separate network program. Its exclusions cannot establish the treatment of a Mastercard transaction.
Calculate counts and amounts separately
Two months feed one ratio
HYPOTHETICAL EXAMPLESEPTEMBER · PREVIOUS MONTH
20,000 cleared transactions
Denominator · bottom of the fraction
OCTOBER · CURRENT MONTH
80 + 20 = 100 eligible records
Numerator · top of the fraction
50 basis points · 0.5%
Mastercard’s clarification gives the High Dispute Merchant, or HDM, ratio using two groups of current-month records. Add the eligible fraud count and eligible non-fraud chargeback count. Divide that total by the previous month’s clearing count. [2]
The numerator is the count above the division line: the eligible records being monitored. The denominator is the count below it: the previous month’s cleared transactions.
These counts come from different months. The calculation does not simply match each fraud report to sales from the same month.
For chargeback monitoring, the numerator is the current month’s chargeback count. The denominator again uses the previous month’s clearing count. [1], [2]
Multiply the fraction by 100 to express it as a percentage. Multiply it by 10,000 to express it in basis points.
A basis point is 0.01 percentage points. Therefore, 50 basis points equals 0.5%, 100 equals 1%, and 500 equals 5%.
Count and amount answer different questions. A count measures how many records enter the calculation. An amount measures their monetary value.
| Criterion | High Dispute Merchant (HDM) | Excessive Dispute Merchant (EDM) |
|---|---|---|
| Minimum cleared transactions | 5 | 5 |
| Combined fraud and non-fraud chargeback amount | $5,000 | $10,000 |
| Combined ratio | 500 basis points 5% | 5,000 basis points 50% |
Read these criteria together. A ratio alone does not establish identification. [1] Confirm the applicable threshold boundaries and reporting periods with your acquirer.
Consider a hypothetical merchant with 20,000 cleared Mastercard transactions in September. October contains 80 eligible fraud records and 20 eligible non-fraud chargebacks.
Work through the example in three steps:
- Add the eligible October records: 80 + 20 = 100.
- Divide by September’s clearing count: 100 ÷ 20,000 = 0.005.
- Convert the fraction: 0.005 × 100 = 0.5%, or 0.005 × 10,000 = 50 basis points.
The example assumes the inputs already reflect applicable exclusions and adjustments. Its 0.5% ratio does not, by itself, establish a program breach.
Now consider the same numerator against 10,000 previous-month cleared transactions. The ratio becomes 100 basis points, or 1%.
For subscription operators, the denominator deserves attention during seasonal declines and processor migrations. Investigate changes in both the eligible records and the clearing population.
Same numerator, different ratio
HYPOTHETICAL EXAMPLECURRENT-MONTH ELIGIBLE COUNT
100 records
COUNT-BASED RATIO
50 basis points · 0.50%
Eligible inputs after applicable exclusions and adjustments. Amount criteria are separate.
Keep the merchant identifiers
A merchant identifier, or MID, identifies a merchant in the acquirer’s system. A company using several acquiring relationships can have several MIDs.
A submerchant identifier identifies an individual seller within an applicable payment-facilitator or marketplace arrangement. The parent account and the individual seller are different levels of reporting.
Mastercard’s clarification places Excessive Fraud Merchant (EFM), Excessive Chargeback Merchant (ECM) and High Excessive Chargeback Merchant (HECM) monitoring at MID level before April 2027. [2]
From April 2027, those categories move to submerchant-level monitoring where applicable. Mastercard’s clarification describes HDM and EDM as operating at MID level. [2]
Keep separate calculations for the relevant acquiring relationship and monitored identifier. Confirm any cross-acquirer aggregation with your provider before combining MIDs into an official program calculation.
Keep the acquirer, MID and applicable submerchant identifier in your reporting.
Before changing routing, confirm which identifier receives each numerator and denominator. Retain a company-wide view for management alongside the applicable program calculations.
One company can have several MIDs
ILLUSTRATIVE IDENTIFIERSYour company
Internal management view
Acquirer A
Acquirer B
Submerchant ID: an additional seller-level identifier where applicable.
Keep 3DS and monitoring treatment separate
3-D Secure, or 3DS, authenticates the cardholder in supported online card-payment flows. Authentication helps establish who is making the payment.
A liability shift concerns which party bears specified fraud losses under the applicable rules. Monitoring treatment concerns whether a record enters a program calculation.
Those are three separate questions. Successful 3DS authentication does not, by itself, establish an exclusion from the combined metric.
Mastercard’s clarification discusses 3DS criteria specifically within its ecommerce-focused Excessive Fraud Merchant program. [2] The deck lists 3DS utilisation for that program and marks it as not applicable to HDM and EDM. [1]
This leaves a specific question for the processor: how does a reported fraud transaction with successful 3DS authentication enter each applicable metric?
Record the authentication result, liability position and monitoring treatment separately. Do not use a liability-shift flag as an automatic exclusion.
Three checks for the same payment
AUTHENTICATION
Who is paying?
Record the 3DS result.
LIABILITY
Who bears the loss?
Check the applicable liability rules.
MONITORING
Does the record count?
Confirm program inclusion or exclusion.
A successful authentication result does not establish a monitoring exclusion.
Get the acquirer policy and reporting
The framework also includes High Dispute Acquirer (HDA) and Excessive Dispute Acquirer (EDA) categories. These concern the acquirer’s portfolio, rather than one merchant’s calculation.
An acquirer’s portfolio threshold and your merchant operating limit serve different purposes. Obtain your provider’s merchant-level policy before setting internal warning levels.
Request warning thresholds, intervention triggers, remediation deadlines and any contractual consequences in writing. Identify who will notify your team when action is required.
In its November clarification, Mastercard says acquirers can view GMAP in the Data Integrity portal, with October data visible in November. [2] Ask your processor how it will provide that reporting to you.
Request an extract showing the program, monitored identifier, reporting month, eligible counts, amounts, denominator, exclusions, adjustments and audit status.
An audit here means a monitoring review opened after the applicable thresholds are crossed. Mastercard’s presentation says identification opens an audit; it does not mean immediate termination. [1]
Compare the processor’s monthly extract with your own records. Investigate missing records, timing differences and exclusions before accepting the total.
Use the remaining months to reconcile
Mastercard says the new HDM/EDM merchant counters and HDA/EDA acquirer counters reset on 1 April 2027. [2] Existing ECM and EFM audits carry over, according to its merchant deck. [1]
A counter tracks months of identification under the relevant program. Resetting the new counters does not erase existing audits or remove the need to resolve fraud and disputes.
Assign one payments-operations owner to the monthly reconciliation. Bring fraud, disputes, finance and data teams into the same review.
Over the next 30 days:
- Reconcile the latest available month across each processor.
- Trace a refunded fraud transaction and a reversed chargeback.
- Check a First-Party Trust case and a 3DS-authenticated fraud case.
- Document the applicable exclusions, identifiers and reporting cutoffs.
- Agree on an escalation owner and response deadline with each processor.
For subscription merchants, use the findings to address renewal surprises, unclear descriptors, cancellation failures and support delays.
Start with one refunded transaction. Ask the processor to show exactly where it appears in the monitoring report.
Sources
[1] Mastercard, Understanding the Global Merchant Audit Program (GMAP), merchant presentation, September 2026, slides 8–11. The presentation sets out merchant criteria and the implementation timeline.
[2] Dave Senci, Vice President, Product Management, Mastercard, clarification in the Merchant Risk Council discussion GMAP (April 2027): how are you treating refunded fraud, First-Party Trust and MID-level measurement?
Further reading: Checkout.com’s GMAP implementation notice, 29 October 2026; Mastercard’s First-Party Trust overview.