NFC Not Working on Your Phone? How to Fix It and Share Your Digital Card Anyway

You’re mid-conversation at a conference, you tap your card against someone’s phone, and nothing happens. It’s one of those small moments that can feel disproportionately awkward. Before you write off NFC entirely, it helps to understand what’s actually going on — because in most cases the fix is simple, and even when it isn’t, you have two solid fallbacks ready to go.
This guide covers why NFC not working on a phone with a digital card is more common than it should be, how to resolve the most frequent causes, and how to build a sharing sequence that doesn’t stall regardless of the hardware in the other person’s pocket.
Why NFC Fails More Often Than You’d Expect
NFC — Near Field Communication — requires both devices to be NFC-capable, both to have the feature active, and the tap to happen in roughly the right spot. Any one of those conditions being off is enough to break the exchange. The technology itself is reliable when the conditions are right. The conditions, unfortunately, are not always right.
The four most common causes are: NFC disabled in settings, a phone case interfering with the signal, the tap landing on the wrong part of the device, and the recipient’s phone simply not having NFC hardware at all.
Check the Settings First
On most Android devices, NFC is a toggle in the quick-settings panel — the same place you’d find Wi-Fi and Bluetooth. It is often off by default and stays off unless the user has a reason to enable it. On iPhones, NFC for background tag reading is on by default from the iPhone XS onwards, but older models require the user to open the NFC reader manually from the Control Centre.
If you’re sharing your own card, your settings aren’t the issue — you’re presenting the card, not reading it. But if the person you’re sharing with has NFC switched off, the tap will fail silently. Politely suggesting they check their settings is reasonable, though in a busy networking moment it’s often faster to switch to your QR code.
Phone Cases Are a Surprisingly Common Culprit
Thick wallet cases, cases with built-in magnets, and cases with metal plates used for magnetic car mounts can all attenuate or block the NFC signal. The phone may be perfectly capable and NFC may be enabled, but the physical barrier between the antenna and your card is enough to prevent a read.
You can’t ask someone to remove their case at a networking event. What you can do is be aware that if a tap fails on a device that should work, the case is a likely cause — and you move on to your QR code without making it a production.
The Tap Zone Varies by Handset
The NFC antenna is not always in the same place on every phone. On most Android devices it sits near the centre of the back. On iPhones it tends to be near the top edge. Tapping your card against the middle of an iPhone’s back, or against the bottom of an Android, may produce no result even when everything else is correct.
A slow, deliberate tap — moving the card across the back of the device rather than pressing at a single point — gives the antenna a better chance to register. If you’re the one initiating the tap, try the top third of the phone first, then the centre. Most successful reads happen within a second or two; if it hasn’t worked after three attempts, switch methods.
For a more detailed walkthrough of how the tap and write process works with a BONKT card, the NFC Read and Write knowledge base article covers the mechanics clearly.
Some Phones Don’t Have NFC at All
NFC is standard on mid-range and premium Android handsets and on iPhones from the iPhone 6 onwards, but it is not universal. Budget Android devices — particularly those sold in regional markets or on prepaid plans — frequently omit NFC hardware entirely. No amount of settings adjustment will fix a missing antenna.
There is no reliable way to tell at a glance whether someone’s phone has NFC. The practical answer is to treat NFC as a first attempt, not the only method.
The Fallback Sequence: Tap, Then QR, Then Link
A well-prepared digital card user has three sharing methods available and knows when to use each. The sequence is straightforward.
First, try the tap. It’s the fastest method when it works, and it creates a natural moment of interaction. If it works first time, great.
If the tap fails, show the QR code. QR codes work on any smartphone with a camera, which covers the vast majority of devices in use today. The recipient opens their camera app, points it at the code, and your card opens in their browser. No app required on their end — they see your profile, tap “Save to Contacts”, and your details land in their phone. BONKT cards are designed to make that save-to-contacts step straightforward for the recipient.
Your QR code can be displayed on your phone screen, printed on a badge, or added to a virtual background for video calls. The knowledge base article on downloading your QR code covers those use cases, and you can customise the QR code’s appearance to match your branding.
If neither tap nor QR is practical — say, you’re on a phone call, exchanging details over email, or in a situation where showing a screen isn’t easy — send your card link directly. A BONKT card link opens in any browser. The recipient doesn’t need an account, doesn’t need to download anything, and doesn’t need to have heard of BONKT. They click the link and your profile is in front of them.
Building the Habit Before You Need It
The time to think through your fallback sequence is not when you’re standing in front of someone and the tap has just failed. It’s worth spending five minutes before any event making sure your QR code is easy to access — either saved to your phone’s photo library or set as a widget — and that you know where your card link is so you can copy and send it quickly.
If you use a physical NFC card, the same logic applies. The card is a convenient trigger, but the profile it points to is what does the work. A recipient who scans your QR code ends up in exactly the same place as one who tapped your card.
The QR code customisation options in BONKT let you tailor the code’s colour and style so it looks intentional rather than like a fallback — which matters if you’re displaying it on a badge or a screen at a stand.
When the Other Person Is Trying to Tap You
The scenario above assumes you’re sharing your card. But sometimes the person you’re meeting also has a digital card and wants to share theirs with you. If your NFC is off, or your case is blocking the signal, you’ll want to know how to receive as well as send.
On Android, enabling NFC in quick settings takes a few seconds. On iPhone, background tag reading is on by default for supported models — you just hold the phone near the card and the notification appears at the top of the screen. If you’re using an older iPhone model that requires manual activation, it’s worth adding the NFC reader to your Control Centre before you attend any event where you expect to exchange cards.
The Broader Point About Digital Card Reliability
A digital card’s profile is not stored on the NFC chip itself — the chip simply carries a link. That means if the tap fails and you share via QR or link instead, the recipient receives exactly the same profile. Nothing is lost. And because the profile lives online, any update you make — a new phone number, a changed title, a new employer — is reflected immediately for anyone who saved your card, regardless of how they originally received it. There’s no reprint cycle and no version mismatch.
That’s a meaningful practical advantage over a physical card, and it’s one that holds regardless of whether the NFC tap worked on the day.
You can explore the full range of sharing and profile features on the BONKT features page, or browse the knowledge base for step-by-step guidance on specific settings. If you’re ready to set up your card, the plans page covers what’s included at each tier, including the free option.


