NFC makes a close tap useful: a phone can read a small tag, present a supported credential to a terminal, or help start another connection. These actions can look similar from the outside while relying on different software, permissions and services.
When a tap fails, first identify what should happen. Opening a website from a sticker is a different problem from paying at a terminal or using a hotel key. A successful test of one function does not prove that every other NFC function is available.
A tag, a credential and a connection handover are different
The Android NFC overview distinguishes reader/writer mode from card emulation. In reader mode, the phone can read supported tags; with appropriate hardware and software, it can write writable ones. Card emulation lets the phone act as a card to an external reader. Availability of a particular payment, transit or access application is another question.
NDEF, the NFC Data Exchange Format, gives applications a common way to describe records such as a web address. It is a data format, not an account or a proof of identity. A plain writable sticker holding a URL cannot become your payment card simply by copying the visible text or an identifier.
NFC can also help arrange a Bluetooth or Wi-Fi connection. In that case the tap is a setup step; the other radio carries the continuing connection. The NFC Forum’s overview of uses describes this complementary role. Both products still need compatible support for the intended handover.
Phone NFC support is not universal RFID support. A retail UHF label and a compatible NFC tag use different radio technology. Even within HF systems, a phone’s operating system, tag protocol and application permissions determine what you can access. An app cannot add a missing UHF reader radio through software alone.
Bring the intended antennas together
Use the phone manufacturer’s indicated tap area and the reader’s marked location. Move slowly and hold the position long enough for the interaction. A protective case, another card between the devices, metal or an inconveniently mounted tag can make the geometry less favorable. Try one card or device at a time.
The NFC Forum’s Release 15 explanation describes a 2-centimeter operating-volume baseline for the newer specification and notes that some products already worked at that distance or farther. It is not a guarantee that every existing phone and tag pair will work at exactly two centimeters, nor a software upgrade promise for older hardware.
For a sign or exhibit, test the final mounting surface with the actual phones you expect visitors to use. A tag that works loose on a desk may behave differently once attached. Keep a printed address or another access route available so the information does not depend on a successful tap.
A small URL-tag experiment
Android’s NFC basics documentation explains how NDEF records are interpreted and dispatched to applications. Apple’s background tag-reading documentation describes supported iPhone behavior and URI-record handling. On supported iPhones, a notification can be part of the process; detecting a tag is not the same as silently opening its destination.
Read-back testing should check the record type as well as the address. Then test the intended user path on the actual device: detection, notification or app response, confirmation, and destination. Do this again after mounting the tag. The URL-tag test sheet provides a place to record the results.
Some tags can be made permanently read-only. Do not lock a prototype before verifying its contents and deciding how future changes will work. If the tag points to a page you control, you may be able to update that page without rewriting the tag, but the domain and hosting still need maintenance.
Use the observed failure to choose the next check
On a small screen, scroll the table sideways to read all columns.
| What happens | Check next |
|---|---|
| No response at all | Confirm NFC support and the device’s required setting or reading mode. Reposition, separate other cards, and test a known compatible tag. |
| A tag is detected but no useful link appears | Inspect its record type and content with an authorized compatible app; check whether that phone supports the expected background action. |
| The link opens but the page fails | Try the same address directly. A network, expired-domain or website problem is separate from the NFC read. |
| A payment or access credential is declined | Check the service’s setup, supported credential and account status. Follow the issuer or building operator’s instructions. |
| It works before mounting but not afterward | Retest the mounting material and position; use a tag designed for that surface if required. |
Change one thing at a time. If a known tag works but the new one does not, compare tag type, record contents and mounting. If several known tags fail on only one phone, concentrate on that phone’s supported functions and configuration. Record the model, operating-system version and exact symptom instead of reporting only “NFC broken.”
Treat a tag’s destination like any other link
A close-range interaction does not prove that a website is genuine. Check the domain before entering information, especially on an unfamiliar tag placed over a public sign. A tag may point to a redirect whose destination changes later. Where money or account access is involved, use the service’s established app or independently known website if anything seems wrong.
Do not store passwords or private account details in a public demonstration tag. For shared installations, assign someone to inspect the physical tag and its destination periodically. The RFID privacy guide explains the separate risks of reading identifiers and connecting them with stored records.
Related resources
Researched and updated September 5, 2026. Check the linked official sources for specifications and policies that apply to your equipment and application.