Tap to Pay on Android, explained for merchants.
Yes: a modern NFC-enabled Android phone can accept contactless card taps and mobile wallets directly, with no dongle, dock, or extra reader plugged in. The feature is called Tap to Pay on Android, part of a category the payments industry calls softPOS, and this guide covers exactly what you need, the security behind it, and the honest cases where a dedicated terminal still wins.
Tap to Pay on Android lets a merchant hold a customer's contactless card, phone, or watch against the back of an NFC-equipped Android phone and take the payment on the spot. There is no card reader to buy, no dongle in the headphone jack, and no dock on the counter. The phone's own near-field antenna is the reader.
The broader industry name for this is softPOS, short for software point of sale, and every major card network now backs some version of it. Visa markets it as Tap to Phone and reports 700,000+ active Tap to Phone terminals across 71 countries (Visa, as of August 2022). Below we walk through what actually turns your phone into one of them, why it is safe to run card data through a consumer handset, and where the model breaks down for a working business.
What Tap to Pay on Android actually is
Tap to Pay on Android is a capability inside a payment app, not a standalone app you download by itself. Your processor or a platform like Stripe builds it into their software using an SDK, and that software drives the phone's NFC hardware to read a contactless card the same way a countertop terminal would. Stripe launched its version in February 2023 across the US, Canada, the UK, Singapore, Australia, and New Zealand (Stripe, 2023).
The pitch is real: you can accept in-person cards with equipment you already carry. Visa describes it as turning "smartphones into contactless point-of-sale devices" with "no additional hardware required" (Visa). For a mobile seller, a pop-up, a delivery driver, or a service tech who takes the occasional card, that removes the single biggest friction point, which is buying and carrying a reader.
What you actually need to use it
The requirements are narrower than the marketing suggests. A phone either qualifies or it does not, and there is no way to add the missing pieces after the fact.
- An NFC-enabled Android device. Near-field communication is the antenna that reads the tap. Google confirms "near field communication (NFC) must be turned on to make contactless payments" (Google Wallet Help, 2026). No NFC, no Tap to Pay, full stop.
- A recent Android build with Google Mobile Services. The feature leans on "Google Mobile Services and the wide range of functionality afforded by its associated APIs," per Google's own developer writeup (Android Developers Blog, 2023). Phones sold without Google Play services, common on some imported or heavily locked-down handsets, are out.
- A device that passes integrity checks. Rooted phones, unlocked bootloaders, and sideloaded builds typically fail the attestation step and are blocked. This is a feature, not a bug.
- A supported payment app in a supported country. Availability is tied to your processor's SDK and its live regions, not just to the phone.
If you are shopping for a payment provider partly to get this feature, confirm your specific phone model is on their supported list before you commit. Two phones from the same brand and year can differ.
What it accepts and what it does not
Tap to Pay on Android reads anything the customer can tap. Visa lists acceptance from "card, phone or watch" (Visa), and Stripe's Android implementation takes Visa, Mastercard, and American Express contactless credit and debit, plus Google Pay (Stripe, 2023).
What it does not do matters just as much. There is no card slot, so a chip card that will not tap has to fall back to a keyed entry, if your app even allows one. There is no magnetic stripe reader. And there is no receipt printer, so receipts are email or SMS only. For a low-volume mobile seller those gaps are fine; for a busy counter they add up fast.
Is it safe? The PCI MPoC architecture
Running live card data through a phone that also holds your texts and photos sounds risky. The reason it is not comes down to a standard the payments industry built specifically for this: PCI MPoC, or Mobile Payments on COTS, where COTS means "commercial off-the-shelf" devices such as ordinary smartphones (PCI Security Standards Council, 2026).
MPoC governs solutions that include "the entry of both PIN and contactless cardholder data on the same COTS device," and it "builds on the existing PCI Software-based PIN Entry on COTS (SPoC) and PCI Contactless Payments on COTS (CPoC) Standards" (PCI SSC, 2026). In plain terms, it is the rulebook that says a phone is allowed to be a card reader and defines how it must protect the data.
Two mechanisms do the heavy lifting. First, the card data is encrypted the instant it is read, so the app never handles a clear card number. Second, the platform continuously verifies that the app itself has not been tampered with. Stripe uses Google's Play Integrity API, which "replaced SafetyNet Attestation," to confirm that apps using the Tap to Pay SDK are "unmodified" and were "installed from a trusted source like the Google Play Store" (Android Developers Blog, 2023). If a phone is compromised, the check fails and the tap is refused.
This is the same encryption-first philosophy behind Lifted's own acceptance. We tokenize card data with E2EE (Voltage) so the sensitive value is protected end to end and never lands in the clear on the device. If you want the deeper version of how tokenization keeps you inside a lighter compliance scope, see our note on tokenization and SAQ-A compliance.
Phone softPOS vs. a dedicated terminal
Here is where a lot of guides go quiet, because the honest answer is that a phone is not always the right tool. A dedicated Android smart terminal, such as the PAX A920 or A920 Pro, is itself a locked-down Android device, but one purpose-built to take payments. The trade is real and worth laying out side by side.
| Consideration | Tap to Pay on your phone (softPOS) | Dedicated smart terminal (e.g. PAX A920) |
|---|---|---|
| Upfront hardware | None, if your phone already qualifies | A terminal purchase or lease |
| Receipt printing | Email or SMS only | Built-in thermal printer |
| Chip and swipe fallback | Tap only (keyed entry if allowed) | Tap, chip, and swipe |
| Battery under load | Competes with your personal phone use | All-day battery dedicated to sales |
| Device is also… | Your personal phone | Nothing else; a clean payments device |
| Best for | Mobile, pop-up, occasional, backup | Steady counter or route volume |
The deciding factors usually come down to three things. Do you need to hand a paper receipt to the customer? Can you afford to have your only phone tied up, and draining, during a rush? And do you want a business device that is not also where your family texts arrive? If any answer is yes, a dedicated terminal earns its keep. If not, the phone is a genuinely good option.
Lifted's route to contactless today runs on that dedicated hardware. Our Lifted Pay terminal app is PAX-signed and PayDroid-certified for the PAX A920, A920 Pro, and A920 Max, and it runs alongside BroadPOS without ever drawing over the card screen during a transaction. If you are weighing the hardware itself, our comparison of the PAX A920 vs. Clover vs. Square Terminal and the A920 setup guide go deeper. We have also proven refund-after-settlement on live A920 Pro hardware using the tokenized capture, which matters more than most demos admit.
What it costs, honestly
SoftPOS removes the hardware line item, but it does not remove processing fees, and the fee model is where most of your money goes over a year. The two dominant approaches are flat-rate pricing, where every card costs the same headline percentage, and interchange-plus, where you pay the true network cost plus a fixed, disclosed markup. We break the difference down in interchange-plus vs. flat-rate pricing, and it usually favors interchange-plus once you have any real volume.
The demand backing all of this is not hype. Visa reports that 75% of surveyed US small and midsize businesses expected consumers to prefer contactless, and 82% of surveyed SMB owners globally had updated operations to meet demand for digital payments (Visa Back to Business study, 2021). Stripe similarly found 65% of businesses plan to prioritize unified in-person and online checkout, and 64% of shoppers prefer brands with both an online and in-store presence (Stripe, 2023). Contactless acceptance is now table stakes, whichever device you run it on.
How Lifted handles contactless acceptance
Lifted Payments is the payments ISO and software agency of Lifted Holdings. We process card transactions on the Maverick gateway and ACH or eCheck on the NMI gateway, and we protect card data with E2EE tokenization (Voltage) that supports a SAQ-A posture for card-present acceptance. Contactless taps ride the same rails as any other card-present sale.
- Interchange-plus, quoted after one statement. Send us a single recent processing statement and we return an honest rate review. There is no application fee.
- Level 2/3 data appended automatically. On commercial cards we add the extra line-item detail that can lower your rate; see Level 2/3 processing and, for B2B sellers, B2B credit card processing.
- Software priced plainly. The Lifted Pay app is $15/mo per device and $5/mo per added user, so a second person on the same account is a few dollars, not a second contract.
- A keyed virtual terminal when you need it. For phone or mail orders, our virtual terminal keys a card in a browser. Note that keyed entry is SAQ C-VT scope, a different profile than a tapped card-present sale.
If you are comparing us against the obvious incumbent, our Lifted Payments vs. Square breakdown is candid about where each one fits, and how to lower processing fees covers the levers that actually move your effective rate. For the full menu, start at merchant services or browse the other merchant guides.
The bottom line
Tap to Pay on Android is real, safe when built to the PCI MPoC standard, and genuinely useful for mobile and occasional acceptance on a qualifying NFC phone. It is not a full replacement for a dedicated terminal the moment you need a printed receipt, all-day battery, chip fallback, or a device that is not also your personal phone. The right call is rarely the phone or the terminal in the abstract; it is the one that matches how and where you actually get paid. Send us one statement and we will help you land on it, with an interchange-plus rate review and no application fee.
Sources
- Stripe Newsroom — Tap to Pay on Android — Feb 22 2023 launch across US, Canada, UK, Singapore, Australia, New Zealand; accepts Visa/Mastercard/Amex debit+credit and Google Pay; 65% unified-checkout and 64% online-plus-in-store shopper stats.
- Android Developers Blog — Tap to Pay on Android SDK — Google Mobile Services reliance; Play Integrity API replaced SafetyNet Attestation; verifies apps are unmodified and installed from a trusted source like the Google Play Store; cites recently published PCI MPoC standard.
- Visa — Tap to Phone — 700k+ terminals active in 71 countries; no additional hardware required; accepts card/phone/watch; 75% US SMB and 82% global SMB digital-payment demand stats (underlying surveys predate 2026).
- PCI Security Standards Council — Mobile Payments on COTS (MPoC) — MPoC covers entry of both PIN and contactless cardholder data on the same commercial off-the-shelf (COTS) device; builds on existing SPoC and CPoC standards.
- Google Wallet Help — contactless payment requirements — "Near field communication (NFC) must be turned on to make contactless payments."
Tap to Pay on Android: common questions
Can any Android phone accept tap-to-pay card payments?
Do I need a card reader or dongle for Tap to Pay on Android?
Is it safe to take card payments on a personal phone?
What can't Tap to Pay on Android do?
When should I use a dedicated terminal like the PAX A920 instead?
Does Lifted Payments charge an application fee to set this up?
Get an interchange-plus rate review, no application fee
However you take cards — a PAX terminal at the counter or a keyed virtual terminal — send us one recent processing statement and we will return a plain interchange-plus rate review, card on the Maverick gateway and ACH on NMI. No application fee, no obligation.