To program an NFC business card, you write a single web link onto the card's chip using a free NFC writer app on an Android phone, or a compatible NFC app on an iPhone 7 or newer. The chip stores that link, not your contact details, so whatever the link opens becomes your card.
That clears up most of the confusion, since people often assume the chip holds their name, number and email like a tiny hard drive. Below: what to put on the chip, which chip to buy, how to write it on each platform, when to lock it, and how to fix a card that won't read.
What actually gets written to an NFC business card?
An NFC business card contains a passive chip and a thin antenna coil sandwiched inside plastic or paper. It has no battery — a nearby phone's field powers the chip just long enough to hand over its stored data.
That data is formatted as NDEF (NFC Data Exchange Format), the standard every modern phone understands. An NDEF message holds one or more records, each with a type. Three types matter here:
- URI record — a web link. This is what you want in almost every case. Phones treat it as a tappable link and open it in the browser.
- Text record — plain text with no action attached. An iPhone will often show nothing useful for a text-only tag, which is why text records are a common cause of "my card does nothing".
- vCard record — your contact details written directly onto the chip. It works, but it is the option most likely to disappoint you.
Writing a raw vCard to the chip feels self-contained, but it has three problems. It eats memory fast, so a photo is out of the question and a long job title plus two addresses can overflow a small chip. Handling is inconsistent across phones, especially older iOS versions. And when your number or title changes, every card you handed out is wrong forever.
Encoding a URL avoids all three. The link is short, universally handled, and points at a page you can edit. If you're weighing the formats against each other, our comparison of NFC and QR business cards covers where each one wins.
NTAG213 vs NTAG215 vs NTAG216: which chip do you need?
Almost every NFC business card sold today uses an NXP NTAG21x chip. They are NFC Forum Type 2 tags running at 13.56 MHz, and all three read on the same phones. The only practical differences are memory and price.
| Chip | Total user memory | Usable for NDEF | Rough URL length it fits | Best for |
|---|---|---|---|---|
| NTAG213 | 180 bytes | about 144 bytes | roughly 130 characters | Standard cards holding one short link |
| NTAG215 | 540 bytes | about 504 bytes | roughly 490 characters | Long URLs, tracking parameters, a small vCard |
| NTAG216 | 924 bytes | about 888 bytes | roughly 870 characters | A full vCard on the chip, or multiple records |
The usable figures are lower than total memory because NDEF adds header bytes and the tag reserves space for its own configuration, so treat the character counts as working estimates.
For a card that stores a link, NTAG213 is enough. A short branded URL such as a followmysite.com profile link is well under 40 characters. You only outgrow 213 if you insist on a long URL stuffed with campaign parameters, or you want the contact record itself on the chip. Buy 215 for headroom; buy 216 only for a specific reason such as a full multi-number vCard.
Avoid cards sold with no chip type stated — some use small legacy tags with very little usable space, which refuse your URL without a clear error. And check the card is rewritable and unlocked: some suppliers ship cards pre-programmed to their own platform and locked, so you can never change the destination.
How do you program an NFC card with an Android phone?
Android has supported NDEF writing natively for years, so this is the easy path. Any Android phone with NFC hardware can write tags.
- Turn NFC on. Settings, then Connections or Connected devices, then NFC. No NFC entry means the phone lacks the hardware.
- Install a writer app. NFC Tools and NXP TagWriter are two widely used options, both free for basic writing.
- Choose Write, then add a record. Pick the URL or URI record type, not Text.
- Enter the full link including the scheme. Type https:// at the front. Without it, some apps store the value as plain text and it won't open reliably.
- Check the size estimate. Good apps show bytes used against tag capacity before writing. If it exceeds capacity, shorten the URL rather than buying a bigger chip.
- Hold the card against the phone's NFC antenna. On most Android phones it sits in the upper third of the back near the camera; on some it is dead centre. Keep the card still for a few seconds.
- Wait for the write confirmation, then test the card before writing the next one.
Most writer apps offer a batch mode that keeps the payload loaded: write two, test both, then run the rest.
How do you program an NFC card with an iPhone?
The iPhone situation is more nuanced, and it's where most bad advice circulates.
Reading: iPhone 7 and later can read NFC tags through an app. iPhone XS and later added background tag reading, so the phone detects a tag and shows a notification banner with no app open, as long as the screen is on and unlocked. That's why your recipient doesn't need to install anything.
Writing: iPhone 7 and later running iOS 13 or newer can write NDEF records using a third-party app such as NFC Tools for iOS. The flow mirrors Android: choose write, add a URL record, enter the full https link, then hold the phone against the card. The iPhone's NFC antenna is at the top edge near the rear camera, not the middle of the back, and that alone accounts for a lot of failed writes.
What Shortcuts actually does, and doesn't do. Shortcuts can create a personal automation triggered by an NFC tag, but it does not program the tag. It reads the tag's unique chip ID and stores a rule on your own iPhone: when I scan this specific tag, run this action. Nothing is written to the chip, and nobody else's phone knows about the rule.
Shortcuts is the right tool for a tag on your own desk — scan it to open your booking page or start a focus mode — but the wrong tool for a card handed to other people, since nothing gets written to the chip itself.
Should you encode a direct URL or a link you control?
This decision determines whether your cards stay useful. Once a tag is written and handed out, the only way to change what it stores is to get every card back. So encode a link whose destination you can change without touching the chip.
| What you encode | Can you change the destination later? | Notes |
|---|---|---|
| Direct URL to a fixed page | Only if you still control that exact URL | Fine on your own domain where you can redirect. Risky if it's a third-party page you don't own. |
| Your own short link or redirect | Yes | Full control, but you maintain the redirect and the domain renewal yourself. |
| A hosted profile link | Yes | You edit the profile content; the link stays the same. Can include visitor analytics. |
| Raw vCard on the chip | No | Every change means re-writing every card individually. |
A hosted profile is the least fragile of the four. The chip points to one address, and the page behind it is editable. That's how a digital business card platform is meant to work: write your profile link to the chip once, then change your job title, add a service, swap the photo or update your WhatsApp number from your dashboard. Cards already in circulation never need re-writing.
It also lets the card do things a chip never could on its own: a one-tap save-to-contacts vCard download, appointment booking, an enquiry form, an image portfolio, and visitor analytics showing how many people actually opened it. For the wider picture, start with our guide to digital business cards.
Two rules whichever option you choose. Use https, never http — some phones warn on insecure links. And keep the URL short: shorter links fit smaller chips, print cleanly as a QR code on the same card, and are easier to say out loud when the tap fails.
Should you lock an NFC business card?
Type 2 tags support two very different protections, and they are frequently confused.
Permanent lock (read-only). This sets the tag's lock bits so the memory can never be written again. It is a one-way physical change: no unlock, no factory reset, no recovery. A locked tag with the wrong URL on it is scrap.
Password protection. NTAG21x chips support a 32-bit password that gates write access. Anyone can still read the tag, but changing it needs the password. Reversible if you know it, useless if you forget it.
Lock when: cards are left out at a reception desk or in a shop, distributed to a large team where an accidental overwrite would be costly, or bulk-printed with a URL that will never change because it points to an editable profile.
Don't lock: test cards, any card where the destination might change, and anything you wrote in a hurry. For protection without the risk, use the password instead. Casual overwriting is uncommon — someone would have to deliberately open a writer app and hold it against your card — so most people are better off leaving cards writable.
Whatever you decide, never lock before testing. Write, test on two phones, then lock.
How to test an NFC card properly
A few minutes of testing now saves a reprint later.
- Test on both platforms. One Android, one iPhone. A text record that works on Android may do nothing on iOS.
- Test with the phone locked and unlocked. Most iPhones need the screen on and unlocked for background tag reading.
- Test through a phone case. Thin plastic and silicone are fine. Thick wallet cases, cases with metal plates for magnetic mounts, and cases holding credit cards frequently block the read.
- Test the destination on mobile data, not just wifi. A link that resolves only on your office network is a real failure mode.
- Test one card from each production batch, not just the first one you wrote.
- Have a fallback. Print a QR code and the plain URL on the card face, so the card still works when NFC fails or the recipient has an older phone. Our walkthrough on creating a QR code business card covers the print side.
NFC business card not working? Troubleshooting
The tag isn't detected at all
Confirm NFC is enabled (it is off by default on some Android phones, and battery savers switch it off) and that the phone has NFC hardware at all — several budget models don't. Then check position: hold the card flat against the back and move it slowly, pausing briefly at each spot, focusing on the top edge near the camera on iPhone. If a known-good tag also fails, the problem is the phone.
It reads sometimes but not reliably
Almost always position or distance. NFC's working range is roughly a centimetre or two, and coupling depends on the antenna coils lining up. Remove the phone case and retest. Take the card out of a wallet. Hold it still rather than waving it. If one card is consistently weak while others are fine, its antenna may be damaged — cards that have been bent, folded or carried loose for months do fail.
Metal is blocking the read
Metal near the antenna detunes the field and can kill the read completely. Common culprits: metal or metal-look phone cases, magnetic mount rings, the metal plate in a card holder, and testing on a steel desk. Metal NFC cards are a real product, but they need an on-metal tag with a ferrite isolation layer built in. A standard tag applied to a metal card will not work — check that the supplier explicitly lists it as on-metal or ferrite-shielded.
The card wrote successfully but nothing opens
Nine times out of ten the record type or the scheme is wrong. Re-read the tag in your writer app and check three things: the record is a URI or URL record, not Text; the value begins with https://; and there is no leading space or line break. Also paste the URL into a browser — a tag can be written perfectly and still point at a typo. If a notification appears and vanishes, tap the banner rather than waiting; iOS requires that tap.
The tag is read-only, or the write keeps failing
The tag is locked, either by you or by the supplier. Permanent locks are irreversible; that card can only be read from now on. If you set a password rather than a permanent lock, enter it in your writer app's authentication section and the write will go through. If a supplier shipped locked cards pointing at their own platform, that's a returns conversation, not a fix you can apply yourself.
Not enough memory, or the write is rejected as too large
Your payload exceeds the chip's usable NDEF space. Shorten the URL: drop tracking parameters, use a short profile link, and remove extra records. If you were writing a full vCard to an NTAG213, that's the cause — trim the contact fields, or switch to a link instead.
Some people's phones simply don't work with the tag
iPhones older than the 7 have no user-accessible NFC reading, and some low-cost Android phones ship without NFC hardware. This is not fixable at your end — the whole case for a QR code and printed URL on the card face. Give people a second route in and you stop losing contacts to hardware you can't control.
Program once, update forever
The point of doing this properly is that you only do it once. Write a stable link to the chip, keep the page behind it under your control, and the card becomes a permanent pointer rather than a snapshot of one moment.
That's the practical case for pairing NFC cards with a hosted profile. Follow My Site gives you one profile — photo, bio, contact buttons, services list, product catalogue, image gallery, appointment booking, an enquiry form and a downloadable vCard — behind a single short link you can write to any tag, with a one-time lifetime plan alongside the monthly and yearly options, since the whole point is a card that outlives a subscription. Optional pre-programmed physical NFC cards are available if you'd rather skip the writing step yourself.
Whichever route you take, the checklist is short: buy an unlocked NTAG213 or better, write an https URI record you can redirect, test on an iPhone and an Android before locking anything, print a QR fallback, and never encode data you can't change. Still deciding whether to move off card stock at all? The trade-offs are in our look at alternatives to paper visiting cards.
Frequently Asked Questions
Can I program an NFC business card with my phone, or do I need special hardware?
A phone is enough. Any Android phone with NFC can write tags using a free app such as NFC Tools or NXP TagWriter. An iPhone 7 or newer running iOS 13 or later can also write tags through a compatible app. Dedicated USB tag writers exist and are faster for large batches, but for a handful of cards they are unnecessary.
What is the difference between NTAG213, NTAG215 and NTAG216?
Mainly memory and price. NTAG213 has about 144 bytes usable for NDEF data, NTAG215 about 504 bytes, and NTAG216 about 888 bytes. All three use the same standard and read on the same phones. For a business card storing a single short URL, NTAG213 is sufficient. Choose 215 or 216 only if you need long URLs or want a full contact record on the chip.
Can I change the link on an NFC business card after it is printed?
Yes, as long as the tag was not permanently locked. Rewriting overwrites the previous record using the same writer app. But rewriting means physically handling every card. The better approach is to write a link whose destination you control, such as a hosted profile, so you update the page instead of the chip and cards already handed out keep working.
Why does my NFC business card work on Android but not on iPhone?
Usually the record type or the antenna position. iPhones only act on properly formed URI records, so a tag written as a Text record often does nothing on iOS while Android still shows the content. Check that the record is a URL starting with https. Also hold the card to the top edge of the iPhone near the camera, with the screen on and unlocked.
Should I lock my NFC tag after programming it?
Only after testing, and only if the destination will never change. A permanent lock sets the chip read-only forever with no way to undo it. Password protection is the safer middle ground: the tag stays readable by everyone but needs your password to rewrite. For most individuals, leaving the card unlocked is fine, since overwriting requires deliberate effort by someone holding your card.
Do the people I tap my card against need an app?
No. Modern iPhones and Android phones read NFC tags natively, with no app on either side. The phone shows a notification with the link, the recipient taps it, and the page opens in their browser. They can then save your contact details from that page. Adding a printed QR code and the plain URL covers anyone whose phone lacks NFC.