ATM Nearby™

Visa subscription management mandate has been in force since 18 April 2026 across 13 European markets, and the question for product teams has moved from whether to build subscription management to how to build it correctly. The full mandate overview covers all three of Visa's 2026/2027 requirements; this article focuses only on and what it takes at the implementation level. The rule asks issuers to do three things: identify and label three recurring transaction types, enable merchant-level stop instructions with the correct decline responses, and inform cardholders that cancelling a card charge does not end their contract with the merchant. None of these are unreasonable. Each one, though, depends on the quality of the transaction data sitting underneath the interface.

A mid-sized European retail bank with 5 million active card customers sees around 1,5 billion card transactions a year - every purchase a data point on where the customer shops, what they spend on, and how their habits shift over time. The raw material for almost every personalised banking product sits in that feed. The question is not necessarily about access, more like whether the data, once you reach for it, is usable enough to build on - clear enough for customers, structured enough for analytics, consistent enough for credit and risk models.

When a customer taps their card, the bank's issuer system receives a tightly structured but surprisingly thin bundle of card network transaction data. The fields are standardised, the values are constrained, and most of what an end user expects to see in their app - clean merchant names, logos, recognisable categories, exact shop locations - is simply not in the message. Everything from statement clarity to credit decisioning is built downstream of this raw payload, which makes the gap between what arrives and what a customer needs the single most consequential data problem in retail banking.