An NFC business card not working on some Android phones is almost always caused by the phone, not the card: NFC is switched off, the screen is locked, a case blocks the signal, or the card is tapped away from the antenna. Less often, the card uses a chip type that some Android phones don’t support, or the tag holds data Android can’t turn into a link.
On Android 17 there’s one more catch: a tap may show a notification instead of opening your card.
Why an NFC business card is not working on one Android phone but works on another
An NFC business card behaves differently across Android phones because each maker chooses where the antenna goes, whether NFC is on, and which tag types the phone supports. iPhones are much more uniform, so “works on my iPhone, fails on her Pixel” is a common story.
The causes split two ways:
- Phone-side problems: NFC switched off, screen locked, a blocking case, or a tap in the wrong spot. These cause most failures.
- Card-side problems: a chip the phone doesn’t support, a blank or badly written tag, or a damaged chip. These show up as failures on many phones, not just one.
Test with a second phone. If the card opens on one Android phone and fails on another, check the phone first.
Check that NFC is on and the screen is unlocked
An Android phone only reads an NFC card when NFC is switched on and the screen is unlocked. Android’s developer documentation says phones are “usually looking for NFC tags when the screen is unlocked, unless NFC is disabled in the device’s Settings menu.”
The lock screen is what catches people at events. Someone holds out a dark phone, you tap, nothing happens. Ask them to unlock first.
If NFC is off, open Settings and search for “NFC”. On a Samsung Galaxy, it lives under Settings > Connections > NFC and contactless payments. Our guide on how to turn on NFC covers other brands.
If NFC is on but stuck, Samsung’s troubleshooting page suggests toggling it:
- Add the NFC button to Quick settings.
- Tap NFC to turn it off.
- Tap NFC again to turn it back on.
Find the antenna and remove the case
The NFC antenna sits in a different place on different Android phones, so a tap that works on one model can miss on another. Samsung says holding the phone properly keeps the antenna “pointed in the correct direction,” and it shows the exact spot in Settings > Connections > NFC and contactless payments, as an on-screen guide and image.
If you don’t know the model, hold the card flat against the back and slide it slowly. A quick tap-and-pull often misses.
Cases block it too. Samsung warns that certain third-party covers, “such as magnetic covers that hold credit cards and IDs,” can interfere with the NFC antenna. It also notes that NFC won’t work while an LED cover is lit. At networking events the usual culprit is a wallet case, with its cards and magnet sitting right over the antenna.
Some Android phones don’t support every chip type
Some NFC chips work on every Android phone with NFC, while others are optional. Most troubleshooting guides skip this cause. Android’s advanced NFC guide lists the tag technologies every device must support, including NfcA, IsoDep and Ndef. It then lists MIFARE Classic and MIFARE Ultralight as technologies “not required to be supported by Android-powered devices.”
The MifareClassic reference page is blunter: “Implementation of this class on a Android NFC device is optional.” On a phone without it, a MIFARE Classic card is effectively invisible as a business card.
| Chip family | Android support | Good for a business card? |
|---|---|---|
| Chips read as NfcA with Ndef, such as NTAG | Required technologies | Yes |
| MIFARE Classic | Optional per device | Avoid |
Bought a cheap card from a marketplace listing and it fails on several Android phones? Ask the seller which chip it uses. For a new card, pick an NTAG chip; our comparison of NTAG213, NTAG215 and NTAG216 helps you choose a size.
Blank or badly written tags don’t open anything
An NFC card opens your profile on Android only if the chip holds a properly formatted link, called an NDEF record. Android’s tag dispatch system tries the NDEF route first. When a tag “does not contain NDEF data to begin with,” or its data can’t be mapped to a URI, Android hands it to a lower-priority path that ordinary phones don’t act on.
A phone with no special app installed does nothing visible. That’s what you see with a blank card, a card written in a vendor’s own format, or a link that was cut off during writing.
Rewrite the card. Open any NFC writing app, choose a URL record, and paste your full card link. Our step-by-step guide on writing a URL to an NFC tag walks through it.
If you use QRCard, each card has its own NFC-ready URL at qrcard.in/c/yourname. You write that link to any compatible tag yourself, since QRCard doesn’t sell physical NFC cards. The profile opens in a normal browser, so the person tapping needs no app.
Android 16 and 17 changed what happens after the tap
Newer Android versions changed how phones open web links from NFC tags. According to Android’s NFC documentation, starting in Android 16, tags that store web links trigger a standard view-link action. Beginning with Android 17, scanning such a tag “surfaces an ‘open link’ notification, requiring explicit user interaction.”
On an Android 17 phone your card can look broken when it isn’t. The tap works, a notification appears, and nothing opens until the person taps it. Swipe it away and your profile never loads.
When you tap someone’s newer Android phone, tell them to watch for the notification.
When the card itself is the problem
The card is at fault when several Android phones, each with NFC on and the screen unlocked, all fail to read it. The chip may be blank, written with the wrong record type, a chip type those phones don’t support, or physically damaged from bending.
Check in this order:
- Try two or three phones, ideally including an iPhone.
- Read the card with an NFC reader app to see if any data is on it.
- Rewrite your link as a URL record.
- If nothing reads it at all, replace the card.
My take: always carry the QR code too
I’d never rely on NFC alone for a business card. Optional chip support, locked screens, wallet cases and the Android 17 notification each stop a tap from landing. A QR code on the back of the card, or on your phone’s screen, works with any camera app.
That’s the limitation of NFC cards: you control your card, never the other person’s phone. If you’re deciding which to lead with, our breakdown of NFC vs QR code business cards lays out the trade-offs. QRCard’s free plan includes a QR download, so you can print it next to the chip.
FAQ
Why does my NFC card work on one Android phone but not another?
Android phones differ in where the antenna sits, whether NFC is switched on, and which chip types they support. MIFARE Classic support is optional on Android, so a card built on that chip can work on one phone and do nothing on the next.
Does an Android phone read NFC cards when the screen is locked?
Usually not. Android’s developer docs say phones look for NFC tags when the screen is unlocked, unless NFC is turned off in Settings. Ask the other person to unlock their phone before you tap.
Why does my card show a notification instead of opening my profile?
Starting with Android 17, scanning a tag that stores a web link shows an open link notification. The person has to tap that notification before the browser opens your card.
Can a phone case stop an NFC card from working?
Yes. Samsung warns that some third-party cases, especially magnetic covers that hold cards and IDs, can interfere with the NFC antenna. Remove the case and try again.
What should I do if no phone can read my card?
If several phones with NFC switched on all fail, the problem is the card, not the phones. Rewrite the link to the card with an NFC writing app, or replace the card, and show your QR code in the meantime.