What Retailers Actually Need to Know About Apple Pay and Google Pay

Consumers have seen an increase in the popularity of contactless payments such as Apple Pay and Google Pay. For retailers and merchants, it is important to offer mobile wallet payments in their stores to meet customers’ demand for fast, convenient checkout methods.

So when it comes to deciding between Apple Pay and Google Pay, which is the best contactless payment system for shops? This article compares the features and advantages of Apple Pay and Google Pay for retailers to identify the benefits of offering both payment options.

Quick Answer: Accept Both

When it comes to choosing between Apple Pay and Google Pay, retailers do not have to choose. A terminal capable of NFC will accept both, with neither company charging the merchant a fee, and both processing the transaction at the same interchange rate as the card behind the wallet.

The consideration that consumers have (that is, which wallet to load onto their phone) has almost no practical significance behind the counter. For a retailer, the differences are more limited and practical: they concern which customers can pay you, what data enters your system, and who bears the loss when a transaction is disputed.

Apple Pay vs. Google Pay at a Glance

The following table shows the two wallets from the merchant’s perspective rather than the customer’s.

How Each Wallet Works at Your Counter

Both wallets work the same way mechanically: they replace the customer’s actual card number with a device-specific token, then pass it to your reader via NFC. The customer completes authentication using Face ID, Touch ID, or a fingerprint before the phone sends anything. The mechanics should be understood only once, since they explain why an Apple Pay POS setup is the same as a Google Wallet setup.

What Your Terminal Actually Sees

Your reader sees a contactless EMV transaction carrying a token, not a card number. Nothing in that exchange identifies the wallet brand. A tap from an iPhone and a tap from a Pixel produce the same kind of message on the same rails, which is why no retailer needs a separate Apple Pay setup and a separate Google Pay setup. Apple calls its token a Device Account Number, and Google issues an equivalent device token.

What Appears on Your Processing Statement

Your statement only indicates the card brand and the interchange category, not the wallet. When a Visa credit card is tapped using Apple Pay, it is shown as a Visa credit card-present transaction and is priced the same as when the card is dipped using a chip terminal.

Since most processors do not break down wallet volume, merchants looking for an Apple Pay entry will not be able to find one. If you want to check this for yourself on your account, go through your processing statement sentence by sentence and look for the interchange category rather than the type of payment.

There is one point that warrants asking your provider: a small number of processors use a different per-transaction markup for NFC than for chip transactions.

Google Pay is Now Google Wallet

On June 4, 2024, Google stopped offering the standalone Google Pay app in the United States and relocated its features into Google Wallet. Android users now use Google Wallet as their app of choice, and this app also stores transit passes, loyalty cards, event tickets, and state IDs.

Although the Google Pay name is still used for the online checkout button and the developer API, when a customer taps an Android phone in your store, they are using Google Wallet, and therefore any instruction telling you to accept Google Wallet via a standalone app is referring to a product that no longer exists in the US.

How to Accept Both Wallets in Your Store

To accept both wallets, you need one NFC-capable terminal, a processor with contactless enabled on your account, and approximately one hour of staff training. The steps are as follows.

1. Check Your Terminal for NFC

Make sure that your POS payment terminal has near-field communication capability and check for the four-arc contactless symbol on the device’s face. Terminals sold in the last several years almost always include NFC, though it is occasionally shipped disabled.

If your hardware predates contactless entirely, replacement is the only path, and an entry-level NFC reader costs far less than the volume you would otherwise turn away. Our guide to contactless payment terminals covers what to look for when you are buying.

2. Confirm Contactless is Enabled on Your Merchant Account

Get in touch with your payment processor or merchant services provider and request that they verify that contactless acceptance has been enabled for your MID.

Whilst you’re speaking to them, put two specific questions to them: one about whether NFC transactions have a different per-transaction markup compared to chip transactions as per your current schedule, and the other about whether contactless functionality is enabled on all terminals under the account or only on the main terminal.

3. Turn on NFC at the Terminal

Contactless is a setting on most readers and not the default option, and your payment processor or the terminal’s manufacturer can guide you through turning it on. On several models, the change involves downloading a parameter rather than simply using a menu option, so allow a few minutes of downtime per device.

4. Train Your Staff on the Tap

Teach your cashiers to ask customers to tap their phones and to handle the two types of failure that cause most of these problems. Either the customers hold their phones too far from the terminal, or they tap their phones before the terminal asks for payment. It is also important for staff to know that a failed wallet payment cannot be reattempted as a swipe, since there is no card available to swipe.

5. Put the Contactless Symbol at the Counter

Place the EMVCo contactless symbol and the wallet logos where customers can see them before they reach for a card. Signage measurably increases tap usage. Card network rules also require that the symbols meet size, color, and placement standards, so use the artwork your processor supplies rather than creating your own.

6. Run Test Transactions on Every Register

Process a small live sale from an iPhone and from an Android phone at each station, then void or refund both. Testing every register matters because contactless is enabled on a per-terminal basis, and the one you skipped is the one that fails during a Saturday rush.

What Mobile Wallets Cost a Retailer

Mobile wallet transactions cost a retailer exactly the same as card transactions. Interchange follows the card type, not the payment method, so a rewards credit card tapped through Google Wallet carries rewards-credit interchange precisely as it would if the plastic were dipped.

Apple and Google do not charge the merchant. Instead, Apple obtains its fee from the card issuer. According to the US Department of Justice’s 2024 antitrust complaint, Apple charges issuing banks 15 basis points per credit card transaction processed via Apple Pay, plus a flat fee of approximately $0.005 for debit transactions. This amount is taken from the issuing bank’s interchange revenue and not from your settlement. Google, on the other hand, charges nothing for the transaction.

Any source claiming that accepting Apple Pay or Google Pay lowers your processing fees is wrong. For a fuller breakdown of what a tap actually costs you, see our guide to Apple Pay fees for merchants. The savings from mobile wallets are real, but they go elsewhere.

Where the Savings Actually Are

Four benefits show up on a retailer’s books, and none of them appear as a lower rate on the statement.

Fraud Liability Shifts to the Issuer

When a wallet payment made in-store using Face ID, Touch ID, or a fingerprint has been authenticated, responsibility for claims related to unauthorized transactions is transferred to the issuing bank rather than the merchant. In the case of a stolen physical card used at your counter, there is no such protection.

Because fewer such claims reach you, you have fewer chargebacks to deal with. Be sure to check the limit: the change applies only to cases of unauthorized use, not to friendly fraud, and transactions where the card is not present are handled differently from in-store transactions.

PCI Scope Shrinks

In a tokenized transaction, the actual card number isn’t entered into your systems, which means there is less cardholder information in your environment to secure, audit, or worry about. If there is a breach at the register, the device tokens revealed are of no use beyond the original transaction.

Since there is less data that has to be protected, the annual PCI compliance requirements become lighter, something that is most important to a small business operator who has no security team and has fewer potential points of failure.

Transaction Time Drops

A tap takes about a second, while a chip insert takes several seconds. The difference is insignificant on a single sale, but during a Friday evening rush at a liquor store or a morning shift at a convenience store, it can add up to the point of making the difference between a continuously moving line and one that has been left abandoned. Owners generally undervalue the advantage of throughput, and it is the easiest aspect to measure.

Declines Fall

Credentials that have been tokenized remain valid even if the card is replaced. Whenever the card issuer issues a new card, the token is automatically updated, so a customer whose card has just expired can still use it by tapping and paying. A significant proportion of rejected codes at the counter are caused by expired and reissued cards, and by getting rid of this cause, wallets eliminate that problem.

With fewer outdated credentials, there are also fewer frustrating instances of having to retry their payments in front of a queue and fewer sales lost because a transaction that should have succeeded did not go through. Before you conclude that any of it affects your effective rate, use the processing rate calculator to work out the figures.

The Merchant Case for Accepting Both

There is no advantage for a retailer in accepting Apple Pay rather than Google Wallet, since customers use both methods at the same price.

You Cover Your Whole Customer Base

Apple Pay reaches iPhone owners, who account for roughly 58% of US mobile operating system usage, according to StatCounter, and skew toward higher-income households. Google Wallet reaches Android, which holds about 41% in the US and roughly 70% worldwide. Supporting one and not the other means turning away a customer who has already decided to buy from you.

Checkout Gets Faster

Contactless is now the standard rather than the outlier. In its January 2026 earnings call, Visa stated that the proportion of tap-to-pay transactions had exceeded 80% of all face-to-face transactions worldwide and reached almost 70% in the United States. When customers come in, they expect to be able to tap, and this quicker checkout process helps reduce the number of people who leave during the week’s busy hours.

Fraud Exposure Drops

Because tokenization is used alongside biometric authentication, wallet payments are much less susceptible to abuse than payments made with a stolen card, and the liability shift that applies to authenticated taps means more chargebacks are kept off your account. Visa attributes the reduction in fraud to the acceptance at the point of sale of tokenized chips and contactless payments. For retailers responsible for handling retail fraud at the register, that level of protection is more important than the rate debate.

Enabling Both Costs You Nothing

When your terminal is compatible with NFC, then both wallets will function. There is no fee per wallet, no individual certification is required, no extra hardware is needed, and there costs arecontinuing charges from either Apple or Google. The only costs involved are the terminal itself, which you already need to use tap-enabled plastic cards, and the 10 minutes it takes to enable contactless.

What You Lose With Wallet Payments

The real cost of wallet payments is not financial. Retailers give up the identity signal that used to come attached to a card, and they take on a hardware dependency.

You Lose the Customer Identity Link

With wallet payments, neither the name, address, nor phone number is shared with the merchant. Apple makes it clear that Apple Pay does not send the payer’s contact details, and Google also keeps this information back. A customer who used to hand over an identifiable card is now paying anonymously at the till. The solution is to enroll at the point of sale, not through card recognition, so that a loyalty program linked to a phone number can still capture the relationship, regardless of the payment method.

You Depend on NFC Hardware

There is no NFC reader and no option for wallet payments. The older terminals have to be replaced, and if a reader fails, it affects both wallets rather than just one payment type. For a single-register store, it is cheap to have a spare reader, and this becomes all the more important as the proportion of customers who carry no physical card at all continues to rise year by year.

Your Processor Still Sets the Terms

Wallet acceptance runs entirely through your processor, so their pricing, their settlement timing, and their contract terms govern it. The lever worth pulling is choosing a POS system with unbundled processing, since this keeps the rate issue open for discussion. Retailers who use bundled systems cannot renegotiate their contactless pricing without switching software, and the processors are aware of this.

Support Runs Through Your Processor

If a tap stops working, neither Apple nor Google will provide you with any assistance. The only means of getting support is through your processor and your POS provider, and the quality of that support varies greatly. When selecting between the two vendors, take into account the number of support hours and how quickly escalations can be resolved, since a failed reader on a Saturday causes revenue loss measured in hours rather than days.

Tap to Pay: Accepting Wallets Without a Terminal

Tap to Pay turns the phone in your employee’s hand into a contactless reader. Both Tap to Pay on iPhone and Tap to Pay on Android are live in the US and accept contactless cards, as well as Apple Pay, Google Wallet, and Samsung Wallet, with no extra hardware required.

A payment app from a provider with the relevant feature is needed. According to Apple’s developer documentation, merchants download a payment app that is supported, agree to the terms, and accept the device, and then begin taking payments, while the payment service provider carries out the certification and loads the terminal configuration onto the phone. Tap to Pay on Android works the same way through providers such as Square, Stripe, PayPal, and NMI. The simple, practical question is just whether the processor you are currently using offers this feature.

Adoption is no longer a minor thing; Visa stated that its Tap to Phone product handled more than $33 billion in 2025, which was more than double the amount from the previous year, on over 20 million transacting devices.

Where Tap to Pay Earns Its Place

Tap to Pay is appropriate in those cases where it is impractical to carry a terminal or where a register is only required from time to time.

• Sidewalk sales, tastings, festivals, and farmers’ markets
• Curbside handoffs and local delivery
• Line-busting during a rush, with an employee walking the queue to take payment
• A seasonal second or third register that does not justify buying hardware for six weeks of the year

Where Tap to Pay Falls Short

Tap to Pay serves as a reader, not as a point of sale. Even the main checkout area will still require a barcode scanner, a receipt printer, a cash drawer, and a screen big enough to browse an inventory catalog. A phone isn’t capable of scanning a driver’s license to verify age, nor can it be used to operate a busy convenience store counter. You should regard Tap to Pay as an extension of your existing setup rather than as a replacement for it.

Digital IDs And Age Verification in Mobile Wallets

The most important development in the area of age-restricted retail is not payment at all; both Apple and Google are incorporating government-issued identity into the same app the customer currently uses, and the trend suggests age will be verified without requiring the customer to hand over a physical license.

What Apple Wallet Supports Today

As of August 2026, Apple Wallet can hold state driver’s licenses and IDs from 14 states, including Puerto Rico, as well as North Carolina, Oklahoma, Utah, and Virginia, which have been announced. With the introduction of Digital ID in iOS 26, any US passport holder can create a Wallet credential without waiting for their state to issue it. Digital ID is accepted at TSA checkpoints at more than 250 airports and has also been extended to age verification in certain cases.

What Google Wallet Supports Today

Google Wallet includes the state IDs of fewer states, a list that is growing, and it also allows the use of passport-based ID passes. In May 2025, Google introduced zero-knowledge proof technology for private age verification, enabling a user to demonstrate that they have reached the required age without disclosing their date of birth, name, or ID number.

Two months after that, Google made the relevant libraries available as open-source software. The implementation is carried out via the Digital Credentials API for use by apps and websites.

What Age-Restricted Retailers Should Do Now

Continue to check physical IDs, since wallet IDs are still very limited in business acceptance, law enforcement generally does not accept them, and each state still requires the physical card. Make sure your POS records each ID scan, rather than relying on the cashier to perform a visual check.

And when you next replace the hardware, ask the vendor directly whether they support mobile driver’s licenses, as the equipment purchased in 2026 will still be in use by the time the answer becomes nothing but a theoretical possibility.

Apple Has Opened NFC Access to Third-Party Wallets

With the release of iOS 18.1, Apple has made its NFC and Secure Element APIs available to external developers, first in the United States, the United Kingdom, Canada, Australia, Brazil, Japan, and New Zealand, as a result of years of pressure from European antitrust authorities.

The payment chip on the iPhone is no longer exclusive to Apple Pay. On the terminal side, there is no difference since a third-party wallet still sends the same tokenized contactless transaction to the reader. What could change over time, however, is the range of wallets that customers choose to tap.

Accepting Both Wallets With the Right POS System

It is not the POS system that determines whether or not you accept Apple Pay and Google Wallet; that decision is made by the terminal and the processor. What the POS system does decide instead is all that takes place correct the tap, such as whether the sale is posted to the correct inventory item, whether the customer is added to your loyalty program, whether the age check was recorded, and whether the transaction reconciles properly at the end of the day.

KORONA POS is processor-agnostic, which is the most important part here. Because the software does not lock you into a single payment processor, you can shop for contactless rates, switch providers, and renegotiate without replacing your point of sale. Retailers tied to a bundled processor lose that leverage completely, and it usually costs them on the rate schedule.

In addition to handling payments, KORONA POS covers areas left unaddressed by wallet transactions, such as inventory management in both single-store and multi-store arrangements, maintaining customer records even when card-based recognition is lost, and reporting that links payment type to margin.

Conclusion: Accept Both, Then Focus on What Happens Next

Take up both wallets, since there is no need to consider any trade-offs from the merchant’s point of view, no price difference to take into account, and no configuration decision to make other than turning on contactless on your terminal. Apple Pay and Google Wallet appear as one and the same transaction, at the same price and with the same level of protection.

The ones that actually impact your margin are one layer up. Whether your processor pricing is competitive. Whether your POS locks you to that processor. Whether you capture the customer relationship after tokenization strips the identity out of the payment. And whether or not your age verification process remains effective when the ID format changes. These are the questions that deserve your attention.

FAQs: Apple Pay vs. Google Pay for Retailers

1. Do I pay more to accept Apple Pay or Google Pay?

Not at all; both wallets use the same interchange rate as the card’s, and neither Apple nor Google charges the merchant any fee. Apple does take 15 basis points from the issuing bank in the case of US credit transactions, but this amount does not reach your settlement. The only situation in which a difference might be seen is if your processor applies a markup, since a small number of providers charge different amounts for NFC transactions than for chip transactions.

2. Does my POS need to support Apple Pay and Google Pay separately?

No. Both wallets offer the same type of tokenized contactless transaction to the reader. Should your terminal support NFC and contactless payments, and if they are enabled on your merchant account, it will accept both together with Samsung Wallet and physical cards that have the tap function. There is no need for wallet-specific setup, certification, or integration.

3. Can I tell which wallet a customer used?

It isn’t based on standard reporting. Your processor records the card brand and the interchange category, not the wallet. Neither wallet contains the customer’s name, address, or phone number. The merchants do. It’s a purposeful privacy feature, not a flaw in your system. The only way to reestablish that identity link is by enrolling in loyalty at the register.

4. Is Google Pay the same as Google Wallet?

For in-store payments in the United States, yes. Google shut down the standalone Google Pay app on June 4, 2024, and moved its functions into Google Wallet. The Google Pay name still applies to the online checkout button and the developer API, so documentation referring to both is not necessarily wrong; it just describes different contexts.

5. Do I need a new terminal to accept mobile wallets?

Only if your current reader lacks NFC. Look for the four-arc contactless symbol on the terminal face. Most readers sold in recent years include NFC, though they are sometimes shipped switched off and need enabling by your processor. If your hardware genuinely predates contactless, an entry-level NFC reader is an inexpensive replacement.

6. Are Apple Pay and Google Pay transactions safer for my store?

Yes, in two specific ways. No real card number enters your environment, so a breach at the register exposes nothing usable. And an in-store tap authenticated with a fingerprint or face scan generally shifts fraud liability for unauthorized-use claims to the issuing bank rather than the merchant. Neither protection covers friendly fraud, where a legitimate customer disputes a purchase they actually made.