A card-network update can arrive as a long list of fees, mandates and future dates. For a smaller business, the difficult part is working out which lines will reach its own processing bill.
PayPal Braintree's Fall 2026 release guide, published on 4 September, covers changes taking effect in October and beyond. The scope varies by network, region and transaction type.
Start with the date and region
One example is Visa's replacement of its Acquirer Clearing fee with an Acquirer Network Access and Brand Usage fee in Canada, effective 19 October 2026. The guide says the new fee is charged at authorisation and flags the treatment of authorisation reversals.
The same guide discusses a European Digital Commerce Services Fee with an April 2027 effective date. Putting both changes into an October cost estimate would give the wrong picture.
Use the guide to identify relevant questions, then confirm your processor's own notice and pricing agreement. A network announcement does not establish exactly how a provider will pass a cost through to your account.
Your payment mix matters
Break down the transactions you actually process. Include customer and merchant locations, domestic and cross-border activity, currencies and the kinds of payments your integration creates.
A shop selling goods, a platform funding accounts and a business paying recipients may use different transaction categories. A fee attached to one category should not be applied to every payment in a spreadsheet.
If the category is unclear, ask your processor to identify it from a representative transaction. Keep the answer with the fee notice so you can repeat the calculation next month.
Count authorisations as well as completed sales
Fees charged at authorisation can make attempts and reversals relevant to cost. Check how your integration handles duplicate submissions, retries and cancelled orders.
For example, compare completed sales with total authorisation attempts over the same period. A growing gap is worth investigating, even before you decide what a new fee will cost.
Do not remove necessary payment checks to improve that number. Find accidental duplicate attempts or incorrect retry behaviour first, and test changes with your payment provider.
Turn the notice into a usable estimate
Our recommended review is a small worksheet with a line for each applicable change: effective date, transaction scope, provider treatment, relevant volume and estimated impact.
Use recent volumes and show the assumptions. Where the provider has not confirmed how a fee applies, mark the estimate as unresolved and assign the question to someone.
After the first affected statement arrives, compare it with the estimate. That gives you a chance to catch an incorrect classification or a pass-through charge you did not expect.
You do not need to memorise the entire release guide. You need a defensible answer to what changes for your own business, when it changes and how much your processor expects it to cost.
Reporting checked on 13 October 2026. Fee scope and merchant pricing should be confirmed with the processor.
