How to accept Google Wallet and Samsung Wallet payments at the counter.

By Daniel Wilson Kemp · Founder, Lifted Payments · July 26, 2026

Here is the short version, because it is the question most merchants are really asking: you do not "add" Google Wallet or Samsung Wallet the way you add a new sales channel. A phone tap is just a contactless card transaction wearing different clothes. If your terminal takes a tap-to-pay Visa or Mastercard, it takes the phone wallets built on those same cards, automatically, with no per-wallet enrollment.

The only real requirements are two things you probably already have or can turn on quickly: a payment terminal with an NFC (near-field communication) reader, and a processor that has enabled contactless acceptance on your account. Get those two lined up and Google Wallet, Samsung Wallet, Apple Pay, and tap-enabled physical cards all work the moment a customer holds their device to the reader.

Why all three phone wallets "just work" on one terminal

Google Wallet, Samsung Wallet and Apple Pay are not competing payment networks. They are secure containers for the same Visa, Mastercard, American Express and Discover cards your customers already carry. When a customer taps, the wallet presents an EMV contactless transaction to your reader — the identical protocol a physical contactless card uses.

Visa describes contactless simply as "transactions made by tapping either a contactless card or payment-enabled mobile or wearable device over a contactless-enabled payment terminal" (Visa, 2026). From your terminal's point of view, a tapped phone and a tapped card are the same event. That is why there is no "Google Pay integration" to buy and no "Samsung Pay merchant account" to open — those products do not exist on the acceptance side, and anyone selling you one is selling you nothing.

Google's own guidance confirms how little the customer side asks of you: payments work "wherever you find the contactless or Google Pay symbols," and the only device-level requirement is that "near field communication (NFC) must be turned on" (Google Wallet Help, 2026). Your job as the merchant is upstream of all of that — provide the NFC reader, and the wallet handles the rest.

The one real Samsung wrinkle: MST vs. NFC

There is exactly one place where Samsung differs from Google and Apple, and it is worth understanding so you are not misled. Samsung's older phones and watches shipped with a second technology called Magnetic Secure Transmission (MST) alongside NFC. Samsung states that "Samsung Pay/Wallet... uses both NFC and Magnetic Secure Transmission (MST) technology on supported devices, making it work with nearly all current payment terminals" (Samsung, 2026).

MST let an older Samsung phone emulate a magnetic-stripe swipe, so it could pay even at a terminal that had no NFC reader at all. That sounds handy, but it is a legacy bridge, not the future — and Samsung has been removing it. On newer hardware the company notes the "device does not have MST payment capability and only supports NFC payment," a group that includes the Galaxy S22 series (Samsung, 2026).

The practical takeaway is the opposite of a complication:

• An NFC reader covers everyone. New Samsung phones are NFC-only, exactly like Google Wallet and Apple Pay, so a single NFC terminal handles all three wallets and every current device.
• You do not need to chase MST. MST only ever mattered for merchants with old swipe-only terminals and customers on old Samsung phones — a shrinking overlap. Do not buy hardware to support it.
• The direction of travel is NFC. As Samsung itself puts it, "merchants are required to upgrade to a new payment terminal with NFC capabilities in order to accept Apple Pay or Android Pay" — and Samsung's own new phones now sit in that same NFC-only camp (Samsung, 2026).

What tokenization means for your card-data risk

The most under-appreciated fact about phone wallets is that they are usually safer for you to accept than a keyed-in card, because the real card number is never in play. Mobile wallets use payment tokenization: the wallet stores and transmits a token, not the actual card.

EMVCo, the body that maintains the standard, describes it plainly — tokenization works by "removing the primary account number (PAN), and replacing it with a unique alternative value, the EMV Payment Token." Critically, "an EMV Payment Token is constrained in how it can be used. For example, to a specific merchant, device or payment scenario" (EMVCo, 2026). A token skimmed from one tap is close to worthless anywhere else.

Visa reinforces the runtime security: a contactless tap means "each transaction generates a one-time code, just like contact EMV" (Visa, 2026). So a captured tap cannot be replayed as a second charge. Between the persistent token and the per-transaction one-time code, a tapped phone exposes dramatically less reusable data than a magnetic-stripe swipe or a number read over the phone.

Does the card number ever touch my system?

With contactless, the sensitive card number does not land in your point-of-sale in usable form — the token does the work. That is one of the reasons card-present tap acceptance can keep a merchant in the lightest PCI-DSS validation tiers. On Lifted-provisioned hardware we go a step further with end-to-end encryption (Voltage) so account data is encrypted at the read head, supporting a SAQ-A posture for card-present acceptance. If you want the mechanics, our explainer on tokenization and SAQ-A compliance walks through what stays in and out of your scope. (Note the honest distinction: a keyed virtual terminal where a staffer types a card number is a different, heavier SAQ tier — tapping is not that.)

How the money and data actually flow

Nothing about the settlement changes because the card came from a phone. The flow is the same one your existing card sales already follow:

• Tap. The customer holds the phone to your NFC reader; the wallet unlocks with the phone's own biometrics or PIN and presents the tokenized card plus a one-time code.
• Authorize. Your terminal routes the token to your processor and out to the card network, which detokenizes it to the real account and returns an approval — typically in a second or two.
• Settle. The batch settles like any card sale. On a commercial or purchasing card, Lifted appends Level 2 and Level 3 data automatically so B2B taps can still qualify for lower interchange.
• Fund. Proceeds deposit to your bank on your normal funding schedule. The wallet brand never sits between you and your money.

Because it is an ordinary card transaction, it is priced like one. On interchange-plus, a tapped Google Wallet payment costs you the same interchange-plus rate as the underlying card — the wallet adds no surcharge of its own. If you are comparing that against a bundled flat rate, our breakdown of interchange-plus vs. flat-rate pricing shows why the difference compounds on tap-heavy days.

Does my current terminal already accept phone taps?

Before you buy anything, check what you have. Most terminals sold in the last several years are already NFC-capable — the reader is often there even if contactless was never switched on. Run through this:

• Look for the contactless symbol. The four-arc "wave" mark on the terminal face or screen means an NFC antenna is present.
• Confirm contactless is enabled on your merchant account. Hardware can support taps while the processor has the capability switched off. This is the most common reason a tap "does nothing" — a one-line fix on the processor side, not a new terminal.
• Test with your own phone. Add a card to Google Wallet or Samsung Wallet, run a small live sale, and refund it. A successful tap proves the whole chain end to end.
• If it truly lacks NFC, upgrade the terminal, not the wallet. The fix is always contactless-capable hardware plus a contactless-enabled account — never a per-brand product.

Enabling contactless with Lifted

If you process with us, contactless acceptance for all the phone wallets is part of standard card-present setup — there is nothing wallet-specific to configure. Lifted Payments runs card processing on the Maverick gateway, and our card-present hardware is built around the PAX A920, A920 Pro and A920 Max, which have NFC readers on board.

Lifted Pay is our PAX-signed, PayDroid-certified terminal app for those devices. It runs alongside PAX's BroadPOS and is deliberately careful never to draw over the card screen during a live transaction, so the tap experience stays exactly as the customer expects. We have also proven refund-after-settlement on live PAX A920 Pro hardware using the tokenized capture, so returns on a phone-wallet sale work like any other card refund. The Lifted Pay app overview and the PAX A920 setup guide cover the device side; if you are weighing hardware, we also compare the PAX A920 against Clover and the Square Terminal.

None of this requires you to commit blind. Because taps are priced as ordinary card sales, the only number that matters is your effective interchange-plus rate — which is why we quote it only after reviewing one real statement, with no application fee. You can see the full model on our merchant services page.

A note on cost, honestly

You will read claims online that phone wallets are "free" or that they "cost extra." Both are half-truths. There is no separate consumer-wallet fee that lands on your statement — a tapped card is priced as that card. What phone wallets can genuinely earn you is throughput and trust: Visa's small-business materials note customers move through checkout in seconds with contactless, and that visible acceptance signage makes shoppers "2.4x more likely to think a merchant is reputable" (Visa, 2026). Faster lines and fewer abandoned sales are the real return — not a line item. Accept the taps, price the underlying cards well, and the wallets take care of themselves.

Sources

1. Google Wallet Help — Make contactless payments — Confirms NFC must be on and payments work wherever the contactless or Google Pay symbols appear. Verified via WebFetch 2026-07-26.
2. Samsung — NFC vs. MST for Samsung Pay/Wallet — States Samsung Pay uses both NFC and MST on supported devices; the Galaxy S22 series is flagged NFC-only ('device does not have MST payment capability and only supports NFC payment'); notes NFC upgrade needed for Apple/Android Pay. Verified via WebFetch 2026-07-26.
3. Visa — Contactless payments for small business — Defines contactless taps; each transaction generates a one-time code like contact EMV; signage claim: shoppers 2.4x more likely to think a merchant is reputable. Verified via WebFetch 2026-07-26.
4. EMVCo — Payment Tokenisation — Defines the EMV Payment Token replacing the PAN and constrained to a specific merchant, device or payment scenario. Verified via WebFetch 2026-07-26.