Mastercard's Spring 2026 release stacked four fee mechanics across April, May, and June.

They hit four different parts of an acquirer and ISO book, and most teams are modeling them as one variance line.

(Part 1 of 5 in the Mastercard Spring 2026 series)

So if you’re modeling April as a single variance line, you’re going to miss the drivers and the fixes. Pull your April Mastercard invoice detail and reconcile it to your forecast, pricing, and contract assumptions line-by-line.

Here’s who feels what:

If you serve high-risk or specialty merchants: the annual registration fee doubled on May 1, from $500 to $1,000, with additional transaction and volume-based fees following on June 3. Your contract language probably hasn't been touched since the last time this fee mattered. (Part 2)

If you run acquirer operations: Force Post and Fallback Avoidance are showing up as real dollars on the April and May invoices. Two preventable behaviors the invoice now charges for. (Part 3)

If you're an acquirer or ISO on card-not-present volume: DEF didn’t get more expensive. It got rebundled, effective April 6. Your pricing model determines whether you absorb or pass through. (Part 4)

If you run hospitality, travel, or rental acquiring: Mastercard turned stale preauth cleanup into an invoice problem April 1. Incremental flows get an exclusion. Uncleared auths need a full reversal within 30 days or they become a TPE fee event. (Part 5)

Why this gets undercounted. Most acquirer P&L modeling treats the April and May Mastercard invoice as a single variance line. The four mechanics sit across different functions (ops, pricing, vertical specialty, high-risk economics), and those teams don't usually compare notes month to month.

Four parts over the next two weeks. Each one ends with a concrete action for the affected team.