NFC Digital Business Cards
Create and Deploy vCard and URL Business Cards
Creating NFC-enabled digital business cards with vCard records, URL links, and cloud-based contact sharing platforms.
NFC Digital Business Cards
NFC business cards replace the paper card tap-and-forget moment with an instant, updateable digital contact exchange. One tap transfers your full contact details, LinkedIn profile, portfolio URL, or any combination — and you can update the content without replacing the card.
How NFC Business Cards Work
An NFC business card is any form-factor — PVC card, metal card, sticker — with an NFC tag embedded. When tapped against an NFC-capable phone:
- iOS (iPhone 7+, iOS 13+): Automatically reads NDEF and offers to save the contact if a vCard is stored
- Android: Opens the URL or imports the contact depending on NDEF content
- No app required on either platform for basic URL or vCard content
Choosing the Right NDEF Payload
| Payload Type | Pros | Cons | Best For |
|---|---|---|---|
| HTTPS URL (redirect) | Updateable without re-encoding tag | Requires internet connection | Business/professional |
| vCard 3.0 MIME | Works offline, no redirect | Fixed — updating requires re-encoding | One-time events |
| smart-poster | Title + URL + icon metadata | Slightly larger payload | Premium experience |
| LinkedIn URL | One-tap profile open | LinkedIn-specific | Tech/startup context |
Recommended approach: Use a URL redirect. Store a short URL on the tag (e.g., https://card.yourdomain.com/yourname) and redirect to your current vCard or profile page. Update the redirect server-side anytime — the physical card never needs re-encoding.
vCard NDEF Encoding
A vCard payload uses MIME type text/vcard:
NDEF Record:
TNF: 0x02 (MIME Media)
Type: "text/vcard" (9 bytes)
Payload:
BEGIN:VCARD
VERSION:3.0
FN:Alice Example
ORG:Example Corp
TITLE:Head of Product
TEL;TYPE=CELL:+1-555-0100
EMAIL:[email protected]
URL:https://alice.example.com
END:VCARD
Calculate the required memory with the Memory Calculator before choosing a chip. A typical vCard above is ~200 bytes — an NTAG215 (496 bytes usable) comfortably holds it with room for an additional record.
Adding a URL Fallback
Always include a URI record for iOS background reading and for readers that don't handle MIME vCard:
NDEF Message:
Record 1: URI record — https://alice.example.com
Record 2: MIME text/vcard — (full vCard)
iOS reads the URI record first and opens the URL; Android's Contacts app handles the vCard. Most NFC apps process the first matching record type they understand.
Use the NDEF Encoder to generate the correct multi-record NDEF byte sequence.
Chip Selection for Business Cards
| Chip | Memory | Form Factor Availability | Security | Recommendation |
|---|---|---|---|---|
| NTAG213 | 144 B | PVC card, metal card, sticker | Lock bits only | URL-only cards |
| NTAG215 | 496 B | PVC card, metal card | Lock bits + password | vCard + URL |
| NTAG216 | 872 B | PVC card | Lock bits + password | vCard + rich data |
| NTAG 424 DNA (ntag-dna) | 416 B | PVC card | aes-encryption, sdm | Anti-cloning premium cards |
For metal business cards, verify the manufacturer uses an on-metal-tag inlay with ferrite backing — a standard inlay embedded in a metal card will not function.
Updating Content Without Re-Encoding
Use a redirect service (a URL shortener you control) to make your card content permanently updatable:
Tag encodes: https://nfc.yourname.com/card
→ Redirects to: https://yourname.com/contact (update anytime)
→ Or: https://linkedin.com/in/yourname
→ Or: https://cal.com/yourname (booking link)
The tag only stores the short redirect URL (25–40 bytes). This fits on even the smallest NTAG203.
Lock Your Card
After encoding and testing, set the lock-bits to prevent accidental or malicious re-encoding:
- Protects against "NFC tag reprogramming attacks" in shared spaces
- Permanent — ensure content is correct before locking
- Does not affect read speed or tag functionality
Do not password-protect (without also locking) — a password adds a round-trip authentication delay visible to the user.
Physical Card Design Tips
| Consideration | Recommendation |
|---|---|
| NFC symbol | Print the n-mark symbol to show where to tap |
| Tap area label | "Tap to connect" text below the N-Mark |
| QR code | Print a QR code encoding the same URL as fallback for non-NFC devices |
| Card thickness | PVC NFC cards are 0.8 mm; standard is 0.76 mm (ISO CR80) |
| Chip position | NTAG inlay is typically top-right corner; verify with manufacturer |
Building a NFC Card Landing Page
Your card URL should resolve to a page optimised for mobile first-time visitors:
- Above fold: Photo, name, title, company — immediately identifiable
- Primary CTA: "Add to Contacts" button (downloads vCard) — highest priority
- Secondary CTAs: LinkedIn, email, phone click-to-call
- Below fold: Portfolio highlights, recent work, testimonials
Response time matters. A mobile page that loads in > 2 seconds after an NFC tap creates a poor impression. Use a CDN and keep the landing page lightweight (< 100 KB total).
See Also
자주 묻는 질문
Our guides cover a range of experience levels. Getting Started guides are written for beginners with no prior NFC knowledge. Programming guides target developers integrating NFC into mobile apps or embedded systems. Security guides are for engineers designing secure NFC deployments for payments, access control, or authentication.
Most guides require only an NFC-enabled smartphone (iPhone 7+ or any modern Android device) and a few NFC tags (NTAG213 or NTAG215 recommended for beginners, available for under $1 each). Advanced guides may reference USB NFC readers like the ACR122U or Proxmark3 for development and testing.
Yes. Programming guides include code examples for Android (Kotlin/Java with the Android NFC API), iOS (Swift with Core NFC), and web-based tools (Web NFC API for Chrome on Android). All code samples are tested and include inline comments explaining each step.