Accepting Apple Pay as a merchant

Apple Pay is a tokenised wallet sitting on top of the card networks. The card number never reaches you; a device token does. For merchants the important consequences are not about the tap but about fraud liability, authorisation quality and, in Europe, a regulatory shift that has changed who else can offer the same experience.

How to accept Apple Pay as a merchant

You enable Apple Pay through your PSP or gateway. Underneath it remains a Visa or Mastercard transaction carried by your existing acquiring relationship, which is why integration is quick and why the commercial questions deserve the attention instead. Device tokens generally authorise better than keyed card entry, and for Mastercard device tokens fraud liability sits with the issuer.

Authentication

Why a wallet clears authentication in one gesture

Strong customer authentication has a precise definition. Article 4 of Commission Delegated Regulation (EU) 2018/389 requires it to be based on two or more elements categorised as knowledge, possession and inherence, and to result in the generation of an authentication code.

A device wallet supplies two of those at once. The provisioned device is possession, the fingerprint or the face is inherence, and the customer performs both in a single gesture they already make to unlock the phone. Article 9 requires the elements to be independent enough that the breach of one does not compromise the reliability of the others, and Article 9(3)(a) sets out how a multi-purpose device satisfies that, through separated secure execution environments in the software installed inside the device. That provision is the reason a phone is allowed to carry both elements at all.

This is where the authorisation uplift actually comes from, and it is worth being precise about it. A wallet transaction is not fairly compared against an unauthenticated card transaction. It is compared against a card transaction that had to be challenged, and the difference between those two flows is the step your customer never had to take. Measure the wallet against your 3D Secure challenge rate rather than against overall card conversion, and the number you get is one you can act on.

Access

Apple no longer has exclusive access to the iPhone NFC chip in the EEA

On 11 July 2024 the European Commission made Apple’s commitments legally binding under EU antitrust rules, requiring Apple to give third-party wallet developers free access to the NFC input on iOS through host card emulation, without going through Apple Pay or Apple Wallet, across the European Economic Area for ten years. The commitments also removed the requirement for developers to hold a payment institution licence, and opened access to Face ID, double-click initiation and default wallet settings on fair and non-discriminatory terms. Under Article 6(7) of the Digital Markets Act the interoperability obligation applies more broadly.

What that opening has produced so far

Vipps MobilePay became the first third-party wallet to enable contactless payments on iPhone after the opening, in December 2024, and PayPal launched tap to pay on iPhone in Germany in May 2025. Wero has stated an intention to support in-store NFC payments. The practical merchant consequence is that the wallet layer at the point of sale is becoming contested rather than singular, and a consultancy estimate from Oliver Wyman puts Apple Pay at around 35 per cent of non-cash point of sale transactions in certain advanced European markets. Where that share goes next affects who sits between you and your customer.

Exemptions

The exemption maths changes when authentication is free

Exemptions exist because authentication costs conversion. The same regulation sets them out and the amounts are specific. Article 11 exempts a contactless transaction at the point of sale where the individual amount does not exceed EUR 50, provided the cumulative amount since the last strong customer authentication stays under EUR 150 or the number of consecutive transactions stays under five.

Online, Article 16 exempts a remote transaction of no more than EUR 30, with a cumulative limit of EUR 100 or five consecutive transactions. Article 18 adds transaction risk analysis, where the exemption threshold rises to EUR 100, EUR 250 or EUR 500 depending on the reference fraud rate achieved, which for card-based payments runs from 0.13 per cent down to 0.01 per cent.

Read those together and the wallet case sharpens. An exemption buys conversion by removing a step, and it moves the fraud loss to the party that removed it. On a wallet the step costs the customer almost nothing, so there is far less conversion to buy and far less reason to take on the loss. The exemption policy that makes sense on keyed card entry is not the one that makes sense on wallet volume, and most merchants run a single policy across both.

Cost

A wallet adds a party, it does not remove one

Underneath the button the transaction is still a card transaction on your existing acquiring relationship, so interchange and scheme fees are unchanged. What the wallet adds is a layer, and layers get priced.

The question to put to your provider is therefore narrow. What does wallet volume cost, and is the card cost underneath passed through or blended into the same average as everything else? Under a blend the two cannot be separated, so a rise in wallet share and a rise in your effective rate look identical on the statement even when only one of them happened.

The second question is about data rather than price. Ask whether your provider reports which tokenised transactions were eligible for liability shift. That figure moves your chargeback line, it is already being calculated somewhere in the chain, and it costs nothing to ask for.

Which payment provider supports Apple Pay?

Adyen, Checkout.com, Stripe, Mollie, Unzer, Saferpay and Worldline all document Apple Pay, among others, and so does every other provider of consequence, so ask instead what you pay on wallet volume, whether the card cost underneath is passed through or blended, and whether your provider reports liability shift eligibility on tokenised transactions. A wallet does not remove interchange; it adds a party.

Reviewing what this costs you

What you pay is set in your PSP contract, not by the scheme. Start by establishing whether you are overpaying your PSP, or look at what payment performance optimisation does to authorisation rate and cardmix, which is where a wallet earns or costs you money.

Relevant markets: global