Visa and Mastercard fee changes, priced in advance
The April and October releases and the interim bulletins are mapped into the engine with effective dates and source references — then priced against your own volume so you see what each one moves before it reaches an invoice.
- Scheme releases and bulletins tracked for Visa and Mastercard
- Impact modelled against your book, in basis points
- Every rule version dated and referenced back to its document
Rule changes on your book
10 Apr 2026
Mastercard
Interregional consumer credit IRD 75 → 1.15%
−7 bps on 4.2% of volume
17 Apr 2026
Visa
International service assessment rebase
+1.8 bps on cross-border
12 Aug 2026
Mastercard
Bulletin 2026-08 · recurring acquirer fee
+€0.0002 per txn
9 Oct 2026
Visa
October release · EEA debit tiers
modelled, not yet effective
Every change carries an effective date and a reference to the announcing document — so you can see which rule version priced any historical transaction.
Impact, not announcements
A bulletin is not useful. What it does to your book is.
Anyone can subscribe to scheme notices. The question that matters is which of your transactions a change touches and what it moves — and that can only be answered by pricing the change against your own volume.
- Transactions and merchants in scope, before the effective date
- Movement expressed in basis points and in currency
- Changes modelled ahead of time, then confirmed once live
Rule changes on your book
10 Apr 2026
Mastercard
Interregional consumer credit IRD 75 → 1.15%
−7 bps on 4.2% of volume
17 Apr 2026
Visa
International service assessment rebase
+1.8 bps on cross-border
12 Aug 2026
Mastercard
Bulletin 2026-08 · recurring acquirer fee
+€0.0002 per txn
9 Oct 2026
Visa
October release · EEA debit tiers
modelled, not yet effective
Every change carries an effective date and a reference to the announcing document — so you can see which rule version priced any historical transaction.
Engine health
Anomalies surfaced, never silently absorbed
The engine also watches itself: calculation coverage, transactions it could not price cleanly, deviations against clearing files, and the reconciliation position per scheme per day. A number that cannot be trusted is worse than a number that is missing.
- Unpriced or partially resolved transactions listed with a reason
- Reconciliation drift caught per day rather than per cycle
- Findings carry the transactions behind them, ready to act on
Open findings
Interregional IRD 75 priced at the old rate
1.85% charged where the scheme now uses 1.15%. 4,180 transactions across 12 days.
Fee applied without a matching charge driver
A tiered fee resolved but never charged for one entity. Surfaced rather than defaulted to zero.
Unresolved BIN metadata
22 transactions priced on a fallback product profile. Listed with the transactions attached.
Recivr records what happened and prices it. Where the data is anomalous, it says so instead of quietly correcting it.
What is watched
The things that quietly change your cost base
Release cycles
April and October scheme releases mapped in ahead of their effective dates.
Interim bulletins
Out-of-cycle changes tracked between releases, where surprises usually live.
Rate movements
Interchange and scheme fee rate changes, by region and card product.
Source references
Every rule version linked to the document that announced it.
Coverage
Transactions the engine could not price cleanly, surfaced with a reason.
Reconciliation drift
Deviation against the clearing files watched per day, per scheme.
The principle
Record what happened. Price it. Surface what looks wrong.
Recivr does not arbitrate. It records the event as it was sent, prices it against the rules in force at that moment, and makes the result inspectable.
When something does not add up — a fee resolved but never charged, a rate that moved without a bulletin, a day that will not reconcile — the anomaly is surfaced with its transactions attached, rather than smoothed away by a default.
That is the difference between a number you can defend and a number you merely have.
FAQ
Monitoring questions
What does rule change monitoring cover?
The April and October scheme releases, interim bulletins, and regional and interchange rate updates for Visa and Mastercard — mapped into the engine with effective dates and a reference back to the announcing document.
How do we know a change affected us?
Because the change is priced against your own book. When a rule takes effect you see the transactions and merchants it touches and what it moves in basis points — before it shows up as an unexplained line on an invoice a quarter later.
What else is monitored?
The engine's own behaviour: calculation coverage, unpriced or unresolved transactions, deviations against clearing files, and the reconciliation position per scheme per day. Anomalies are surfaced with the transactions behind them rather than silently absorbed.
The rest of the platform
One engine, several surfaces.
Every product below runs off the same priced transaction events.
Real-time cost engine
Interchange and every scheme fee calculated in under 50 ms, at authorization, capture, refund and chargeback.
Pricing management
Set how each merchant is priced by region, card type, amount and currency, and see the margin on every transaction.
Merchant analytics
Scheme cost in basis points by merchant, MCC, card product and region, so under-priced merchants stand out.
Invoice reconciliation
Visa and Mastercard invoices matched line by line against calculated fees, with every difference traced to its rule.
Interchange reconciliation
The schemes' own clearing reports reconciled against your transactions, with a daily deviation in basis points.
See what this year's releases did to your book
We will price the 2026 scheme changes against a period of your traffic and show you what each one moved, in basis points.