Short answer: When Tap to Pay can't run, Payment for Stripe tells you why. Find the message you're seeing below. Some are quick fixes, like turning on NFC. Others mean the phone itself can't do Tap to Pay, and a card reader is the way to go.
New to Tap to Pay on Android? Start with Tap to Pay on Android.
Don't see Tap to Pay in the app at all?
The app only offers Tap to Pay where Stripe supports it on Android. That's based on your Stripe account's country, not where you are right now. It works in 40 countries, including the US, Canada, the UK, Australia, New Zealand, Singapore, Malaysia, and most of Europe. Japan, Hong Kong, Mexico, and some European countries are in Stripe's public preview. See Stripe's full list.
If your country is on the list but the menu has no Enable Tap to Pay, the app has already found that this phone can't run it. Tap Connect reader, then Tap to Pay on this phone, to see the reason.
Tap to Pay isn't available
This device has no NFC hardware, which Tap to Pay needs to read contactless cards. A card reader works on any device.
Why: Tap to Pay reads the card through the phone's NFC chip, and this phone doesn't have one. No setting or update adds it.
Fix: use a Stripe card reader. Tap Order a reader in the message to get one, or enter the card details manually in the meantime.
You'll see one of these:
Tap to Pay isn't available
Tap to Pay needs Android 13 or newer. This device is on Android [version]. Update the device to use it.
Tap to Pay requires Android 13 or newer on a supported device.
Why: Stripe's Tap to Pay only runs on Android 13 and up.
Fix: update your phone's software, then try again. If your phone can't get Android 13, it can't use Tap to Pay. Use a card reader instead.
Tap to Pay isn't available
Tap to Pay needs an Android security update from the last 12 months. Open Settings > System > System update and install the latest update. If your phone has no update available, it can't use Tap to Pay — use a card reader instead.
Why: Stripe requires a recent security update to keep card data safe. Phones that no longer get updates fall behind over time, even if Tap to Pay used to work on them.
Fix: install the latest system update, then try again. Once the phone is up to date, the app checks again on its own. If there's no update for your phone, use a card reader.
Tap to Pay isn't available
Tap to Pay isn't available on this phone. It doesn't meet the security requirements for contactless payments, and a software update won't change that. Use a card reader to accept contactless cards, or enter card details manually.
Why: Stripe checks the phone's built-in security hardware before it lets it take cards. This phone doesn't pass.
Fix: there's nothing to change on the phone. Use a Stripe card reader, or enter card details manually.
Tap to Pay needs NFC. Turn on NFC in your device settings, then try again.
Why: the phone has NFC, but it's switched off. You might see this when you turn on Tap to Pay or in the middle of a sale.
Fix: if the message has an Open settings button, tap it. Otherwise open your phone's Settings, search for NFC, and turn it on. Then try again.
Tap to Pay can't run while Developer options or USB/Wi-Fi debugging are enabled. Turn them off in Settings, then try again.
Why: Stripe blocks Tap to Pay while the phone is open to debugging tools, to protect card data.
Fix: open your phone's Settings, find Developer options (often under System), and turn it off. That also turns off USB and Wi-Fi debugging. Then try again.
You'll see one of these:
Location permission is required to connect to the card reader.
Precise location is required to connect to the card reader. In the app's Location permission settings, turn on "Use precise location".
Why: Stripe needs your precise location to take card payments in person. It's only used while the app is open. If you said no, or picked approximate location, Tap to Pay can't start.
Fix: open your phone's Settings, go to Apps, then Payment for Stripe, then Permissions, then Location. Allow it while using the app and turn on Use precise location. Then try again.
Not seeing your device? Tap to Pay needs Android 13 or later with NFC turned on.
Why: the app looked for this phone's Tap to Pay and didn't find it.
Fix: check that the phone is on Android 13 or newer and NFC is on, then try again.
Can't turn on Tap to Pay. Your Stripe account may need more verification. Check your Stripe Dashboard for pending requirements, or contact Stripe support.
Why: this one isn't about your phone. Stripe wants more details about your account before it allows in-person payments.
Fix: sign in to your Stripe Dashboard and finish any pending requirements. If nothing's listed, contact Stripe support.
Trouble adding a location
The first time you turn on Tap to Pay, the app may ask you to Select a location for Tap to Pay. Pick your business, or tap Add location to create one. If you see this, the message under the title is Stripe's reason, usually a problem with the address:
Couldn't add location
[Stripe's reason]
Fix the address and try again, or add the location in your Stripe Dashboard at dashboard.stripe.com/terminal/locations (use your business address), then come back to the app.
At checkout
Tap to Pay isn't connected
Try again to take this payment with Tap to Pay, or enter the card manually.
Why: Tap to Pay was set up, but it didn't reconnect when you opened the app. An out-of-date security update or NFC being off can cause it.
Fix: tap Try again. If it still can't connect, the app shows you why. Match that message to this article. To finish the sale right now, tap Enter card manually.
Tap to Pay couldn't show the PIN screen. Turn off screen recording, screen overlays and accessibility services, check your internet connection, then try again.
Why: some cards ask for a PIN. Stripe won't show the PIN screen while something could record or draw over it.
Fix: stop any screen recording, close apps that draw on top of other apps (chat bubbles, screen dimmers), and turn off accessibility services you don't need. Check you're online, then run the sale again.
Tap to Pay isn't available on this device.
Why: Stripe turned the phone down for a reason the app doesn't recognize.
Fix: make sure the phone is up to date, then try again. If it keeps happening, use a card reader or enter the card manually, and contact us so we can take a look.
Stuck on "Initializing card reader…"
The spinner says Initializing card reader... while the app connects Tap to Pay. Sometimes it stays on screen.
Why: the app is still waiting for Tap to Pay to finish setting up on the phone. The first time can take a minute or more. A weak or dropped internet connection can also hold it up. After about a minute the message changes to Still setting up Tap to Pay… and a Cancel button appears, so you're never stuck with no way out.
Fix:
- Give it a minute on a good connection, especially the first time.
- If you see Still setting up Tap to Pay…, tap Cancel. Check you're online, then turn on Tap to Pay again.
- Close Payment for Stripe completely, reopen it, and try again.
- Restart the phone, then try again.
- Still spinning? Match any message that shows up to this article, or enter the card manually or use a card reader for now, and contact us.
Good to know
- Tap to Pay needs an internet connection. It doesn't take offline payments.
- Can't get Tap to Pay working? You can still take every payment. Enter card details manually, or connect a Stripe card reader.