Mastercard sets European offline-payment requirements for network outages

Sourced news briefing

Mastercard announced on 8 October 2026 that it will introduce new offline-payment requirements across Europe. From February 2027, newly issued Mastercard cards in Europe are to be enabled for offline payments, and from May 2027 new and replacement terminals are to support them. Mastercard says eligible chip-and-PIN transactions can be approved locally when connectivity is unavailable, within limits established by the issuing bank, and submitted for clearing after service returns. The announcement follows payment disruption during major power and network outages and describes a phased scheme requirement rather than an immediate capability at every checkout.

Mastercard states that an offline transaction may be limited to €200, with the issuer setting the applicable amount, and that the capability has already operated in Denmark, Sweden, Estonia and Latvia. The cited release does not say every merchant, terminal, card, transaction type or country can use offline approval today. It also does not remove issuer, acquirer or merchant controls. These facts are attributed to Mastercard. The following analysis is independent merchant analysis and does not claim that FixPays supplies Mastercard offline acceptance or any named terminal capability.

Independent merchant analysis: Treat resilience as an end-to-end design

Offline approval changes where a payment decision occurs, but it does not make the transaction independent of the wider payment chain. The merchant still needs power for the terminal, a configured acceptance application, secure keys, staff procedures, later connectivity and a route into clearing. A site with a generator but no compatible terminal is not ready, and a compatible terminal without documented limits can create confusion. Merchants should map electricity, local networking, terminal configuration, acquirer support, receipt handling, fulfilment and post-outage clearing as one operational sequence.

Critical merchants should define which locations, lanes and product categories may continue during an outage. A supermarket, pharmacy, fuel station and ticket machine have different customer needs and fraud exposure. The policy should say who may activate contingency mode, what employees see, when cash or another method is offered, and when offline acceptance stops. Staff should not improvise limits or describe a transaction as final merely because a local approval appears. Customer wording must reflect the actual status supported by the terminal and contract.

Independent merchant analysis: Control limits and accumulated exposure

An offline per-transaction limit does not by itself control total exposure. A card might be presented repeatedly, several lanes may operate independently, and a prolonged outage can accumulate approvals before issuers see them. Merchants should ask the acquirer which counters, cumulative limits, merchant-category restrictions, country rules and decline conditions apply. Store-level controls can add lower thresholds, restricted goods or supervisor review, but those choices should be tested so they do not defeat the continuity objective or produce inconsistent treatment.

Fraud teams should distinguish a genuine outage from an attacker attempting to suppress connectivity. Monitoring can compare terminal health, power events, unusual velocity, repeated cards, ticket values and locations, while avoiding unsupported accusations. Physical security also matters because an isolated terminal may be easier to tamper with. Preserve device logs and incident timing. If the merchant manually records exceptions, protect that information and avoid creating insecure workarounds involving full card details or unapproved paper records.

Independent merchant analysis: Reconcile when connectivity returns

The most important financial control begins after service restoration. Every locally approved transaction should move into clearing once, with a stable terminal and merchant reference. Finance should reconcile local receipts, terminal batches, acquirer reports, cleared transactions, reversals and any transactions rejected later. Duplicate submission can harm customers, while a missing batch can turn an apparently successful trading day into loss. The merchant needs an owner for unresolved items and a defined period before assuming that a local approval became collected funds.

Customer service should be able to locate the transaction even if the customer contacts the merchant before clearing completes. Refund timing, cancellation and duplicate correction may differ from ordinary online authorisation. Receipts should identify the merchant and amount clearly without promising settlement status the merchant cannot know. When a transaction ultimately fails, the response should follow the contracted process and consumer law. Merchants should not retry a credential silently through a different route unless the customer has properly authorised that payment.

Independent merchant analysis: Test the contingency before relying on it

A controlled test should remove connectivity without exposing real customers, verify terminal behaviour, inspect staff prompts and confirm how the batch reaches reporting after restoration. Test boundary values, PIN failure, an expired card, a replacement terminal, an interrupted receipt, reversal, refund and a second attempt. Include accessibility and language needs. Results should be documented with the terminal model, software version, acquirer configuration and test date because a later update may change the outcome.

Business-continuity plans should also cover outages that exceed the offline window, affect the acquirer or disable the building. Offline card acceptance is one layer, not the entire plan. Merchants may still need cash procedures, order reservation, manual customer communication and a decision to close. Review insurance, loss allocation and contractual liability with qualified advisers. Scheme announcements explain direction, but the merchant should rely on confirmed implementation details from its own acquirer and terminal provider.

Independent merchant analysis: operating review

Merchants should establish a post-incident review that combines operational and financial evidence. The review should identify which terminals entered offline mode, which cards and values were accepted, what stock or services were released, when connectivity returned and whether every item cleared. Compare losses with the continuity benefit rather than assuming that all offline activity was either successful or unsafe. Feed confirmed findings into terminal limits, staff training and site resilience. Procurement should also confirm whether maintenance contractors and replacement-terminal processes preserve the approved configuration. Where a location operates several acquirer relationships, document which devices and lanes support the mode so employees do not make unsupported promises during an emergency. Treasury should estimate the maximum accumulated exposure for each site and decide who can lower or suspend acceptance. Customer-service scripts should distinguish a pending clearing issue from a duplicate charge or a failed payment. Review the evidence with the acquirer after material incidents and record any configuration change. Include offline batches in routine audit samples so controls are tested outside emergencies, and verify that retained receipts and logs follow security and privacy requirements.