How an NFC business card works
The card contains an NFC Forum Type 2 chip (usually an NTAG) with an NDEF record written to it. When a phone is held against the card, the phone reads the record and acts on it: opens a URL, or offers to save a vCard. No app is needed on current iPhones or Android phones, and the card has no battery.
Two things can be written. A URL record sends the phone to a web page: a profile, a booking link, a portfolio. A vCard record puts the contact details directly into the phone's address book without any web page. The URL approach is more flexible because what the page shows can change; the vCard approach works offline and does not depend on anyone's server.
Most programmes write a URL and put the vCard download on the page behind it. Both are cheap to change on our side, but only the page is free to change after the cards ship.
Chip choice for a card programme
NXP's NTAG family covers nearly every business-card use. Memory and security are what separate them.
| Chip | Usable memory | Fits | Use it when |
|---|---|---|---|
| NTAG 213 | 144 bytes | One URL of moderate length | Standard profile-link cards |
| NTAG 215 | 504 bytes | A short vCard with name, phone, email, company | Contact must save without a web page |
| NTAG 216 | 888 bytes | A fuller vCard or URL plus text | Offline-first programmes |
| NTAG 424 DNA | 416 bytes plus SUN | A URL with a signed, changing code | Proof the card is genuine, per-tap analytics, gated content |
Why the URL should live on your own domain
Many card sellers encode a link to their own profile service. It works until the subscription lapses, the vendor changes plans or shuts down, or you want to move to a different profile tool. Then every card in the field points somewhere you no longer control, and re-issuing physical cards is the only fix.
The alternative is one level of indirection. Encode a link like a short path on your company domain with a per-person code. Your web server redirects each code to wherever that person's profile lives today. Change the profile vendor, redesign the page or point the code at a booking calendar for a campaign, and no card has to move. The redirect table is a small file or database that IT or marketing owns.
This also gives you the analytics without depending on the vendor: every tap passes through your redirect, so you count taps per card, per team and per campaign in your own web analytics.
Joiners, movers and leavers
The failure mode of most card programmes is not technical. Six months after launch, a quarter of the cards belong to people who have changed title, moved office or left, and nobody has a process for it. With an owned redirect the fixes are small:
- Joiner: allocate the next code, order or assign a card from stock, create the redirect. Cards can be pre-encoded with codes and handed out from a drawer, which is why we recommend ordering a buffer of unassigned cards.
- Mover: change the profile behind the code; the card is untouched.
- Leaver: point the code to a team page, the person's successor or the company contact page. Do it in the same offboarding checklist that disables their email.
- Lost card: retire the code and issue a new one. Because the card only holds a code, nothing personal is exposed.
Measuring whether the cards are used
A card programme costs design time, cards and the people who run it, so someone will ask whether it worked. Measure at the redirect: taps per card per month, share of cards with zero taps, and what happens on the profile page (contact saved, meeting booked, form sent). Compare cohorts: sales versus support, one office versus another, a campaign month versus a normal one.
NTAG 424 DNA takes this one step further. Its signed URL changes on every tap and includes a tap counter, so you can distinguish genuine taps of the physical card from someone re-opening a link they saved earlier, and you can detect a copied card. That matters for programmes where the card unlocks something, such as a partner portal or a loyalty benefit; for plain contact sharing it is more chip than you need.
Card body and design
The card body affects how the card feels and how well it reads. Standard PVC cards read reliably from any phone. Metal NFC cards look premium but a full-metal body blocks the antenna, so they are built with a cut-out or a hybrid construction and read from one side. Wooden and bamboo cards laser-engrave well. Paper and PLA options suit sustainability policies.
Design for the tap: mark the NFC position with a small symbol, keep foil and metallic inks off the antenna area, and print a QR code on the back for phones that are locked or older. A QR fallback costs nothing and removes the awkward moment when a tap does not register.
What Proud Tek manufactures
We manufacture NFC business cards in PVC, metal, wood, bamboo and paper, with NTAG 213, 215, 216 or 424 DNA chips, printed with your artwork and variable names, and pre-encoded with your URL scheme or vCard records from a spreadsheet you supply. We also make Google review cards and plain NFC cards for other tap-to-open uses. The redirect and profile pages run on your systems; we can encode against a URL pattern before it is live so the cards are ready when the pages are.
Published 2026-09-09 · Updated 2026-09-25
