Make an NFC Digital Business Card (vCard) Anyone Can Tap

Quick answer

A tap-to-save business card is a vCard — a plain-text contact record — written directly onto an NFC tag. Tap it against a phone, and the phone offers to save the name, company, phone number, and email straight from the chip. No app, no scan, nothing for the recipient to install.

Getting that to work reliably comes down to three decisions: which chip has room for the whole card, which fields to fill, and whether to add a second record so iPhone taps work as cleanly as Android's. Here's the process end to end, plus the fixes for the problems that come up most.

Step-by-step

Pick a tag with room for the whole card

A minimal vCard — just a name and phone number — fits on almost any chip. A real business card doesn't stay minimal for long: name, company, title, phone, email, and a website URL adds up. NTAG216 gives you the most room of the common chip sizes and is the safer pick once you're writing every field. NTAG213 or NTAG215 work fine if you're keeping it to name plus one contact method.

Fill the vCard fields in NFCore

A valid record needs BEGIN:VCARD, a VERSION line, and at minimum FN (display name) and N (name broken into parts). A real card expects more: ORG, TITLE, TEL, EMAIL, and URL. Use vCard 3.0 rather than 4.0 — it's the version address-book importers handle most consistently. NFCore's business-card template fills this structure for you and previews what will land on the tag before you commit, so a typo in a phone field gets caught on screen instead of after the tap.

Add a backup URL record

Write a second NDEF record alongside the vCard — a link to a hosted version of the same contact info. This one extra step is what makes the tag work the same way on both major platforms, for reasons the next section covers. Once the card is confirmed working on both, decide whether to lock the tag or leave it rewritable for when your details change.

Common problems and fixes

The card doesn't offer to save on iPhone. This is the most common surprise, and it's not a bug in your tag. Android's background reader processes the first NDEF record it finds and can import a vCard directly. iPhone's doesn't — Core NFC has no built-in vCard record type, so for a raw vCard record, the background reader falls through to the second record, the URL, which Safari opens and imports the contact from instead. Skipped the backup URL record above? That's almost always the fix. It's a similar gap to why NameDrop can't fully replace a physical tag — proximity sharing and tag reads just follow different rules on iOS.

The contact imports but a field is missing. Usually the phone number or company field, and it's a formatting issue in that one line, not a capacity problem. A stray character or missing type parameter is enough to make an importer skip a field silently. Re-check that field against the template rather than rewriting the whole card.

The tag runs out of space partway through. Trim optional fields first — title, a second phone number — or move up to a larger chip before you shorten the name or email. Those two matter most for the "save contact" prompt to look right.

Doing this on NFCore specifically

The business-card template in NFCore fills the vCard structure field-by-field and checks it against the memory on whichever chip you've selected. It shows the exact bytes before anything is written, so an oversized card gets flagged before the tap, not after — and it handles the vCard record and the optional backup URL record in the same write. Want your card to update without ever touching the physical tag again? NFCore's redirect-tag approach, and the trade-offs against paid business-card platforms, are worth a look once this one works the way you want.

Frequently Asked Questions

Which vCard version should I use for an NFC business card?

vCard 3.0. It's the version most phone address-book importers handle reliably. vCard 4.0 is more space-efficient, but some Android import flows still trip on it.

Will a vCard tag work on both iPhone and Android?

Yes, if you write two NDEF records. Android imports the vCard directly from the first record it reads. iPhone's background reader needs the second record — a URL — which Safari opens and imports the contact from.

What size NFC tag do I need for a full vCard?

A complete card with name, company, phone, email, and a URL needs more room than the smallest chips offer. NTAG216 is the safer choice; NTAG213 will usually run out of space once every field is filled.

Should I lock the tag after writing it?

Only once your contact info is final. Locking makes the tag permanently read-only — nobody can overwrite it, but that also means no updating a phone number or title later without a new tag.

Conclusion

A tap-to-save business card comes down to two records on one tag: the vCard itself, filled out correctly, and a backup URL so iPhone taps work as reliably as Android's do. Pick a chip with room for the whole card — NTAG216 if you're filling every field — and NFCore handles the formatting and the write in one pass. Once it's confirmed working on both platforms, the only decision left is whether to lock it or leave it rewritable for the next time your details change.