How to Accept Apple Pay and Google Pay as a Merchant: What You Need to Know

If you run a shop, a market stall, a salon, or a service business, the decision to accept Apple Pay and Google Pay is no longer a "nice to have." Mobile wallets have moved from novelty to expectation. Customers now reach for their phone or watch as naturally as they once reached for a card, and when the tap fails, they remember it. This guide explains, in plain language, how to accept Apple Pay and Google Pay as a merchant, what you need to start, how the fees and security actually work, and how to choose an acceptance method that fits the way you sell.

Whether you are taking your first contactless payment or rethinking your setup, the goal is to give you a clear, practical understanding of mobile wallet payments so you can make confident decisions rather than guessing.

Key Takeaways

What Apple Pay and Google Pay Actually Are

Before deciding how to accept them, it helps to understand what these wallets are and what they are not.

Mobile wallets, not new card networks

Apple Pay and Google Pay are digital wallets. A customer adds their existing debit or credit card to the wallet on their iPhone, Apple Watch, Android phone, or Wear OS watch. When they pay, the wallet presents that card to your reader over NFC (near-field communication), the short-range wireless technology that powers all contactless taps.

This is the key point many merchants miss: a wallet payment is still a Visa, Mastercard, or American Express transaction underneath, and the wallet is just the delivery mechanism. That is why, in most cases, accepting contactless cards automatically means you accept the wallets that carry those cards. The same NFC rails also carry Samsung Pay and various bank-specific wallets, which behave almost identically at the point of sale.

The customer experience

For the person paying, the flow is fast and familiar: they wake their phone or raise their watch, authenticate with Face ID, a fingerprint, or a passcode, then hold the device near your reader until it confirms. The whole interaction usually takes a couple of seconds, and the customer never has to hand over a physical card or type a PIN for typical amounts. That speed is a big part of why these payments convert so well at the counter.

Why Merchants Should Care About Mobile Wallet Payments

It is easy to treat wallets as a fringe option, but the behavioural shift is real and it affects your bottom line in several concrete ways.

Speed reduces queue friction

Contactless wallet taps are among the fastest ways to pay. For high-volume, low-ticket businesses such as coffee shops, food trucks, and convenience retail, shaving seconds off each transaction means shorter lines and more customers served at peak. A slow checkout is a silent revenue leak, and wallets directly address it.

Higher checkout completion

When a customer has left their wallet at home but has their phone, a mobile wallet can be the difference between a sale and a walk-away. Phones are rarely forgotten, and biometric confirmation makes customers comfortable paying without a card.

Meeting customer expectations

Younger shoppers in particular increasingly default to their phone or watch, and a business that cannot take a wallet payment can feel dated. Being able to confidently say "yes, we take Apple Pay and Google Pay" is now part of looking like a current, trustworthy merchant, and the broad trend across many markets has been steadily toward contactless and wallet usage.

How to Accept Apple Pay and Google Pay: Your Options

There is no single Apple Pay machine. Instead, you choose an acceptance method that supports contactless, and the wallets come along for the ride. Here are the main routes, from most traditional to most modern.

Traditional countertop or portable terminals

The classic approach is a dedicated card terminal from a payment provider. Almost every terminal sold today supports contactless, so it accepts Apple Pay and Google Pay out of the box. This suits established retailers with a fixed counter and steady volume, but it involves hardware costs, contracts, and sometimes a separate connection.

Mobile card readers paired with a phone

A step lighter is a small card reader that connects to your phone or tablet by Bluetooth: the app handles the sale, the reader handles the tap. This is popular with market traders, pop-ups, and mobile services because it is portable and relatively inexpensive, though it is still one more piece of hardware to charge, carry, and not lose.

Tap to Pay directly on your phone

The newest and often simplest option is Tap to Pay on a phone. Here, your compatible smartphone itself becomes the contactless reader using its built-in NFC. The customer taps their card, phone, or watch directly against your phone, and the payment is processed through an app, with no external terminal or reader at all.

This is where a modern mobile payment app changes the economics for small and growing merchants. With a platform like FiatFlex, a merchant can take contactless Tap to Pay over NFC (Visa, Mastercard, Amex, Apple Pay, Google Pay/Wallet, and Samsung Pay) directly on a compatible phone, with no separate terminal to buy or maintain. For anyone who already carries a capable phone, this removes the biggest barrier to getting started: the hardware. (Apple Pay and Google Pay also work online in website and in-app checkout buttons, but that is a distinct setup; this guide focuses on in-person acceptance, where most small merchants begin.)

Setting Up: What You Actually Need

Getting ready to accept wallet payments in person comes down to a few practical pieces.

A compatible device or terminal

For Tap to Pay, you need a phone that supports NFC and the acceptance app. Most recent smartphones qualify, but confirm your specific model before relying on it for business. For terminal-based setups, the provider supplies compatible hardware.

A merchant account and identity verification

To accept card-based payments, wallets included, you generally go through an onboarding process with a payment platform. Expect identity verification: business and individual identity checks, commonly referred to as KYC and KYB, may be required before you can take live payments. This is standard across the industry and protects both you and your customers.

A payout destination

Money you take needs somewhere to land. For euro-denominated payouts, that typically means a bank account in the SEPA area, where settlement may arrive via Instant SEPA where supported by the receiving bank. A platform that brings card acceptance and payouts into a single dashboard saves you from stitching multiple tools together. Beyond that, know your costs before your first sale, because fee surprises are the most common merchant complaint, which is exactly what we break down next.

Fees, Pricing, and What Drives Your Costs

Fees are where merchants feel the most anxiety, so let us demystify them.

Wallet payments cost the same as contactless cards

A crucial reassurance: there is generally no extra fee for a customer choosing a wallet. Because Apple Pay and Google Pay are just Visa, Mastercard, or Amex transactions delivered over NFC, they are priced like any other contactless card payment in your agreement, with no wallet surcharge for the convenience.

What actually makes up your rate

Your effective cost per transaction is shaped by a few layers:

Different providers package these differently, whether as blended flat rates, interchange-plus, or tiered pricing, but the underlying components are the same. When comparing providers, the headline percentage is not the whole story: look for hardware costs, monthly minimums, contract lock-ins, and chargeback handling, since a low rate attached to expensive hardware and a long contract can cost more than a slightly higher rate with no commitment.

Where FiatFlex fits

To make this concrete, FiatFlex is a mobile payment app that lets merchants take contactless card and wallet taps in person and withdraw euros to a SEPA-area bank account. It also supports crypto acceptance as a separate option, where merchants can accept USDC, EUROC (EURC), and SOL on the Solana blockchain via payment links and QR codes, choosing when to convert and withdraw. That dual capability gives merchants flexibility depending on who they sell to.

Security: How Wallet Payments Protect You and Your Customers

One of the strongest arguments for accepting mobile wallet payments is that they are, by design, more private and harder to defraud than older methods.

Tokenization keeps real card numbers hidden

When a customer adds a card to Apple Pay or Google Pay, the wallet replaces the real card number with a device-specific token (sometimes called a Device Account Number). When they tap to pay, your reader receives that token, not the actual card number. So the real card number is never shared with your business, a token is far less useful to a thief than a full card number, and even in the unlikely event of data exposure there is less sensitive information at stake.

Biometric authentication at the point of sale

Every wallet payment is authorised by the customer on their own device, usually with Face ID, a fingerprint, or a passcode. That authentication happens on the phone before the tap completes, adding a strong layer of confirmation that the legitimate cardholder is present, which generally reduces certain types of fraud and disputes compared with a swiped magnetic stripe.

Practical security habits for merchants

Technology helps, but your habits matter too. Keep your acceptance app and device software updated, use device locks on the phone you take payments on, train staff to recognise a completed transaction versus an incomplete one, and reconcile payouts regularly against your sales records. Whatever provider you choose, confirm how they protect payment data both in transit and at rest.

Common Pitfalls and How to Avoid Them

A few avoidable mistakes trip up merchants new to wallet acceptance.

Assuming you need separate Apple Pay setup

You almost never enable Apple Pay and Google Pay individually for in-person sales. If your reader or app supports contactless, the wallets work automatically. Time spent hunting for a separate Apple Pay activation is usually time wasted.

Confusing the tap zone

Taps fail when the customer's device is not close enough to the NFC antenna, or is held against the wrong part of the reader or phone. A quick, friendly "hold it right here" gesture solves most failed taps, so know where the NFC zone is on your specific device.

Ignoring connectivity and reconciliation

Card-based payments need a connection to authorise, so in a basement, a remote market, or an area with weak signal, plan for backup connectivity. And taking the payment is only half the job: check that the money taken matches what lands in your account, net of fees, on schedule. A unified dashboard that shows acceptance and payouts together makes reconciliation far less painful than juggling multiple systems.

Frequently Asked Questions

Do I need to enable Apple Pay and Google Pay separately to accept them?

In almost all in-person setups, no. Apple Pay and Google Pay are delivered over the same contactless NFC rails as physical Visa, Mastercard, and Amex cards, and underneath they are ordinary card transactions. If your terminal, reader, or app accepts contactless cards, it accepts these wallets automatically. There is usually no separate activation step for taking them at the counter.

Does it cost more to accept a wallet payment than a card payment?

Generally not. Because a wallet payment is still a standard card-network transaction, providers typically price it the same as any other contactless card tap, so you should not expect a wallet surcharge. Your real costs come from interchange, scheme fees, and your provider's margin, the same components that apply to all your card payments, so focus your comparison there rather than on the wallet itself.

Are mobile wallet payments safe for my business to accept?

They are designed to be safer than older methods. Wallets use tokenization, so your business receives a device-specific token instead of the customer's real card number, and each payment is confirmed on the customer's device with biometrics or a passcode. This reduces the sensitive data you handle and adds a strong layer of cardholder verification. Pair that with a provider that encrypts data in transit and with sensible device security on your end.

Can I accept Apple Pay and Google Pay without buying a card terminal?

Yes. With Tap to Pay on a compatible smartphone, your phone's built-in NFC becomes the reader, so customers tap their card, phone, or watch directly onto your device with no extra hardware. A mobile payment app that supports Tap to Pay for cards and wallets, with euro payouts to a SEPA-area bank account, is a practical starting point for small and growing merchants who do not want to invest in terminals.