Mastercom to Mastercard MIND: what issuers and acquirers need to do before 21 April 2028

If your team files Mastercard chargebacks in Mastercom today, you have until 21 April 2028 to move to MIND, Mastercard's new dispute platform. The same day, a rewritten chargeback rulebook takes effect. The platform change is a sizeable integration project. The rulebook change is a workflow project, and it lands on your dispute team.

When does Mastercom switch off?

On 21 April 2028. That is Mastercard's deadline for moving from Mastercom to MIND, the Mastercard Intelligence Network for Disputes. From then on, all new disputes are managed on MIND.¹

Mastercard announced MIND in bulletin GLB 14132.1 on 4 August 2026. The move is mandatory.¹

Mastercard's migration plan:¹

• November 2026: API specifications available.
• July 2027: a test environment opens.
• January 2028: MIND goes live and you can start moving.
• 21 April 2028: every new dispute on MIND.

Mastercard will replace the Mastercom screens with a single MIND screen. If you connect to Mastercom through its APIs today (Mastercom V6, Bridged or Single Message Extended), you will move to a single MIND API. Mastercard will confirm the exact dates, and announce pricing, later.¹³

Once the migration starts, you can run both Mastercard platforms until the disputes opened in Mastercom are resolved. A dispute opened in Mastercom can be finished in either one, but a dispute opened in MIND can't go back to Mastercom. After 21 April 2028, every dispute is opened and finished in MIND.¹

Until Mastercard publishes the API specifications, institutions and their vendors have nothing to build against.

For how Mastercom filing works today, see our guide to Visa VROL and Mastercom.

What changes in the Mastercard chargeback rules on 21 April 2028?

Mastercard will revise its Chargeback Guide on the same date. Bulletin GLB 12939.1, published in January 2026, sets out what changes for chargebacks processed on or after 21 April 2028:²

• The separate rules for single message and dual message transactions merge into one set.
• Two-digit reason codes for single message transactions become four-digit codes.
• Dispute resolution forms are eliminated.
• Time frames are standardized. Mastercard puts the longest cycle, for a case that reaches arbitration, at 88 days, down from up to 123 today.³
• A reason code is added for non-fraud ATM disputes.
• Appeals are handled inside Mastercard's dispute platform.

Chargebacks processed on or before 20 April 2028 stay under the current rules until they resolve. The bulletin also changes arbitration. An issuer that wants to take a case to arbitration will have to file pre-arbitration first. Today, some dispute types let the issuer skip pre-arbitration and go straight to arbitration.²

A platform migration changes where you file a case. A rulebook revision changes what the case is. In a working dispute operation, the new rules change how reason codes are mapped and the deadlines are set in your system. They also change the checks that stop a case being filed wrongly, and your reports by reason code. You will also run both rulebooks at once, while cases opened before 21 April 2028 resolve under the old rules.

What does MIND do that Mastercom does not?

Three things: a new way for your call center to create disputes, fewer disputes over purchases the cardholder doesn't recognize, and new reporting with shorter time frames. Mastercard presents MIND as more than a new filing connection.³

• It gives your call center a new front end. Your call center can create cardholder disputes directly in MIND. That raises a new question for your operation: are disputes created in your own system, or in Mastercard's?
• It aims to stop disputes before they start. MIND brings in more detail about the purchase and the merchant, including from Ethoca, Mastercard's service that shares merchant and receipt details with card issuers. The aim is that a cardholder recognizes a purchase instead of disputing it. If it works, expect fewer of those claims, and a question about where your cardholders see that detail.
• It adds reporting, and some time frames get shorter. MIND brings Mastercard reporting on dispute activity. The shorter time frames come with the rulebook change above.

Can Mastercard MIND handle disputes on other networks?

Partly. Mastercard says MIND will let you manage card, account-to-account (A2A) and other transaction disputes in one platform.¹ But two things stay with your own operation: working disputes on other networks through to a decision, and your duties to cardholders under your own regulators.

Mastercard's customer presentation shows what that means for transactions on other networks: transaction detail, Ethoca services, fraud reporting, and starting and reporting on chargebacks. Working a chargeback through the network's stages to a decision stays Mastercard-only.³

So MIND can be one front end for disputes on other networks, but not one place to work them. A Visa or debit network dispute that starts in MIND is still worked to a decision through that network, under its own rules and deadlines. Your cardholders see one bank, not a set of networks, so your team still needs one view of every case, whichever network decides it.

Your duties to cardholders under your own regulators, such as Regulation E for US issuers, also stay with you, whichever platform files the case. So before 2028, decide where the line sits between MIND and your own operation, network by network. Then decide whether you run one dispute operation across your networks, or one per network.

What does an issuer or acquirer have to be able to do?

Seven things, from running two rulebooks at once to deciding where your call center creates disputes:

1. Run two rulebooks at once until every case opened before the date is closed.
2. Map the old reason codes to the new ones, without entering open cases again or losing their history.
3. Retire the forms and record the same information in fields on the case.
4. Move deadlines to the new standard time frames, with an unbroken audit trail.
5. Move your Mastercard connection to MIND when the API specifications arrive, without changing how your team works cases.
6. Report on cases from before and after 21 April 2028 together, for example cases opened in March and in May.
7. Decide whether your call center creates disputes in your own system or in MIND's front end.

None of this is new to an institution that has lived through a network mandate. This time it all arrives on one date: a merged rulebook, a new code format, retired forms, a platform migration and a new network front end.

What usually goes wrong in a network change?

Three things: testing takes longer than planned, analysts have to apply the new rules correctly, and two rule sets at once cause confusion. Lean has seen all three while supporting institutions through the Visa VROL and Mastercom go-lives, and the network rule updates since.

• Testing takes longer than planned. The part most often underestimated is end-to-end testing and the effect of the change on workflows. Delays usually come from establishing access to the network's test environment or from slow set-up of test transaction data, and they can run to months. Start testing as soon as the network's test environment opens. Vendors often test first with one or two institutions that are ready. That brings network issues and gaps in the specification to light while there is still time to fix them.
• Analysts have to apply the new rules correctly. New processes, reason codes and deadlines need to be understood by the people who work the cases. Train analysts before go-live. Teams that plan for this early have smoother first months.
• Two rule sets at once cause confusion. Open cases follow the old rules while new cases follow the new ones. Managers and analysts need clear guidance on which rules apply to each case, so decisions stay consistent.

There is no standard time from specification to go-live. It depends on how much changes and how ready the network is. In past mandates, Lean has shared a document with clients setting out the impact on AdjustmentHub and NetworkHub. Lean then tested with one or two clients ready to move early, and rolled out to the rest once the changes were stable. Ask your vendor for the same: an impact document early, and a place in the first test group if you are ready.

What should you decide before Mastercard's test environment opens?

Five things: who owns the change, who maintains your dispute system, how many platforms you run, where disputes are created, and what you will test. If you treat this as a 2028 project, you will be remapping reason codes in the middle of a migration.

1. Who owns the change.
2. Whether your own team or a vendor maintains your dispute system, and who makes the changes when a network updates its rules.
3. Whether you run one platform per network, or one operation across every network and payment type you handle.
4. Where your call center creates disputes once Mastercard offers its own front end.
5. What you will test when the API specifications arrive.

The software decision follows from those five.

What this means for your dispute team

On 21 April 2028, Mastercard changes both where your team files a chargeback and the rules each case follows. The platform move is an integration project. The rulebook change reaches your reason codes, deadlines, filing checks and reports, and for a while your analysts will work under two rulebooks at once. Until the last case opened under the old rules is closed, both sets of lines are on the field. In earlier network changes, the teams that prepared early had the smoothest first months.

Three things to do now:

• Name an owner for the change, and work through the five decisions above before July 2027.
• Ask your vendor for an impact document once the API specifications are out, and a place in the first test group if you are ready.
• Plan how analysts will learn the new rules, and how they will tell old-rule cases from new ones.

Lean Industries has built and implemented dispute software for banks, credit unions and processors for over twenty years, including through the Visa VROL and Mastercom go-lives. MIND is the next change of that kind, so Lean is following Mastercard's announcements closely and will share each specification update as Mastercard publishes it. Lean will keep this guide current as Mastercard reaches each milestone: the API specifications due in this month (November 2026), the pricing announcement, and the test environment due in July 2027.

Whatever MIND changes on the Mastercard side, your team still works Visa and debit network cases too. NetworkHub does that job today: it connects AdjustmentHub, Lean's dispute management software, to Visa VROL, Mastercom and the connected debit networks, so one operation works cases across all of them.

If you have questions about what this means for your operation, contact your Lean Industries account manager or customer success specialist.