What Can You Put on an NFC Card? A Complete Guide

How an NFC Card Works — the One-Minute Version

The chip inside an NFC card is a passive device: it has no battery and draws the tiny amount of power it needs from the reader's radio field at 13.56 MHz. When a phone is held within 3–4 cm of the card, the chip wakes up and transmits its stored data. The phone reads it in under a second. Most chips used in commercial cards — including the ones in PrintedCards' RFID ID Card and RFID Visiting Card — use the MIFARE Ultralight or NTAG213/215/216 standard, with NDEF-formatted memory that any NFC-capable phone can interpret without a dedicated app.

The key number is storage capacity. An NTAG213 chip holds 144 bytes of usable data. An NTAG216 holds 888 bytes. In practice, 144 bytes is enough for a URL or a short vCard. 888 bytes fits a full contact record with multiple phone numbers, a website, a postal address, and a social profile. The chip in your card is locked at the factory after programming, so the data stays intact indefinitely — there is no battery to die and no signal to lose range on.

URLs: The Most Versatile Thing You Can Store

A URL is the single most powerful thing to put on an NFC card because it makes the chip a pointer to unlimited dynamic content. The card itself stores a short address — 30 to 60 characters — and the phone opens that page in its browser. Whatever is at that page can be updated anytime without reprinting the card. This is the fundamental advantage of a URL over storing data directly: a card printed today can point to a portfolio you updated last week.

Common uses: a digital business profile page (LinkedIn, Linktree, or your own site), a product catalogue or price list, a booking or enquiry form, a WhatsApp chat link (wa.me/your-number), a Google Maps location, a YouTube channel, or a specific landing page tied to a marketing campaign. Hotels program NFC cards to open their dining menu or room service portal. Real estate agents link to a property video tour. Doctors link to their appointment booking system. Retailers link to a loyalty sign-up page.

If you are only going to store one thing on an NFC visiting card, a URL is almost always the right answer — because you can change where it points without replacing the card.

vCard Contact Information

A vCard (Virtual Contact) is a standardised text format that packs your name, phone number, email address, job title, company, website, and postal address into a single block of data. When a phone reads a vCard from an NFC chip, it prompts the user to save the contact directly to their address book — one tap and your number is saved, no typing required.

A minimal vCard with a name, one phone number, and an email fits comfortably within 144 bytes (NTAG213). A full vCard with a photo URL, multiple numbers, a work address, and a website needs an NTAG215 or NTAG216 chip. PrintedCards programs whatever vCard content you provide when ordering your RFID Visiting Card. The practical advice: include your mobile number, professional email, job title, and your website or LinkedIn URL. Leave out fields you rarely give out — a leaner vCard saves faster and reads more reliably across all phone models.

vCard on NFC cards is widely used by sales representatives, consultants, real estate agents, and anyone who frequently hands their contact details to new people. A single tap replaces the friction of a missed call, a typed-out number, or a business card that ends up in a pile.

Wi-Fi Credentials

An NFC card can store a Wi-Fi network name (SSID) and password in a format that Android phones recognise as a network join request. A single tap connects the phone to the network without the user typing anything. This is programmed using the Wi-Fi Simple Configuration (WSC) NDEF record type, and it works on all Android devices from Android 10 onwards. iPhone support is limited — iOS handles Wi-Fi NFC join via QR code rather than NDEF, so a combined NFC + QR approach covers all devices.

Where this is genuinely useful: hotel lobbies, cafes, co-working spaces, conference registration desks, and corporate visitor check-in areas. Instead of writing the Wi-Fi password on a chalkboard or printing it on a paper slip, you place a small NFC card or sticker at each table and guests tap to join. The card itself can be UV-printed with your branding and a "Tap to Connect" label, making it both functional and a brand touchpoint. Wi-Fi NFC cards can be paired with a URL on the same chip — the URL loads a welcome page or a loyalty sign-up form after connecting.

UPI Payment Links

India's UPI system supports a standard URI format: upi://pay?pa=yourvpa@bank&pn=Your+Name&am=0&cu=INR. Program this into an NFC chip and a tap opens the payer's preferred UPI app — Google Pay, PhonePe, Paytm, or any BHIM-compatible app — with your VPA pre-filled. The payer just enters the amount and authorises. No QR code to scan, no number to type.

This is used by freelancers, small merchants, and tradespeople who want a faster payment handoff than showing a QR code on a phone screen. A UV-printed NFC card with your name, UPI ID, and a "Tap to Pay" label sits on a counter or is handed to a client — the interaction takes three seconds. You can also include an amount in the URI for fixed-price services (a fixed consultation fee, for example), so the payment app opens with the amount pre-set.

One important note: UPI NFC links do not require any bank hardware or merchant account beyond your existing UPI VPA. Any individual can program their UPI link onto an NFC card and use it immediately.

Phone Number (Tel: URI)

The simplest possible NFC record: a tel: URI (tel:+919876543210) that opens the phone dialler with the number pre-filled. The user just taps the call button. This is most useful on NFC ID cards where the primary purpose is access to one contact — a helpdesk card, a receptionist's card, a field service engineer's card — rather than saving a full contact record. It is also the most universally compatible format across all phones and operating systems.

Where it is less suitable: if you want the person to save your number, use a vCard instead. A tel: URI only dials; it does not prompt the user to save anything. For any use case where the recipient should have your number in their contacts after one interaction, vCard is the correct choice.

App Store Deep Links

An NFC card can store an app deep link — a URL that opens directly inside an installed app, or redirects to the app's Play Store / App Store listing if the app is not installed. The standard approach uses a universal link (your-app.com/open) that the app claims on both platforms, or a custom URI scheme (yourapp://page/action) for apps that support it.

This is most useful for businesses with their own app: a tap on an NFC loyalty card opens the loyalty section of the app, a tap on an NFC event pass opens the digital ticket, a tap on a staff ID card opens the company's internal directory. The programming is identical to storing a URL — you simply use the deep link address. For companies distributing NFC cards to customers or staff, this removes every step between physical card and in-app action.

Social Media Profiles

LinkedIn, Instagram, YouTube, and Twitter all have mobile web URLs that open in-app on a smartphone. Storing your LinkedIn profile URL (linkedin.com/in/yourhandle) on an NFC visiting card means a tap opens your full professional profile. For a content creator or influencer, an Instagram or YouTube link is more useful than a vCard. For a B2B salesperson, LinkedIn is the natural destination.

If you want to link to multiple profiles, the cleanest approach is to store a URL pointing to a Linktree, Bio.link, or a simple personal page that lists all your links. This also makes the card evergreen — if you change your Instagram handle, update the landing page, not the card.

Geolocation and Map Links

A Google Maps URL (maps.google.com/maps?q=lat,lng or maps.app.goo.gl/shortlink) opens Maps directly with the pin placed. For businesses with a physical location — a shop, a factory, a venue — an NFC card with a map link removes the friction of a customer searching for the address. Tap the card, get directions. This works especially well on NFC cards placed at the entrance or reception of a large campus or industrial facility where visitors frequently get lost.

A geo: URI (geo:12.9716,77.5946) is the native format that opens any mapping app rather than forcing Google Maps. The trade-off is that geo: URIs do not carry a label, so the pin appears with no business name. A Google Maps short link is better for most use cases because it carries the Place name and shows photos, hours, and reviews alongside the pin.

Text, Email, and SMS

A plain NDEF Text record stores any string — a welcome message, an access code, a product serial number, a legal notice, or a set of instructions. When read, the phone displays the text in a notification or pop-up. Text records are useful on internal NFC tags attached to equipment (maintenance logs, asset IDs) but are less commonly used on NFC visiting or ID cards, where a URL or vCard is almost always more useful.

A mailto: URI (mailto:support@printedcards.in?subject=Order+Enquiry) opens the phone's email app with the recipient and subject pre-filled. An sms: URI opens the messaging app with a number pre-filled. Both are useful on support or helpdesk cards where the primary action is contacting a specific team, and they work without an internet connection — the trigger is local to the phone.

What You Cannot Store on a Standard NFC Card

A standard NDEF NFC card cannot store a full-resolution image, a PDF file, a video, or any file larger than a few kilobytes. It also cannot execute code — the chip delivers data, and the phone's OS or an app decides what to do with it. Biometric data (fingerprints, facial recognition templates) is stored on cryptographically secured sectors of MIFARE DESFire or similar high-security chips, not on the NDEF area, and requires a dedicated reader — these chips are used in government IDs and corporate access control systems, not standard NFC visiting cards.

Sensitive personal data — Aadhaar numbers, bank account details, passwords — should never be stored on an NFC chip in plain text. The chip has no encryption on its NDEF area; anyone with an NFC-capable phone can read it within a few centimetres. Store a URL pointing to a secure authenticated page instead.

Choosing What to Program for Your Use Case

For an NFC visiting card: vCard if the primary goal is saving your contact, URL if the primary goal is driving traffic to a portfolio, profile, or booking page. For most professionals in India, a URL pointing to a WhatsApp chat link or a combined profile page covers more ground than a vCard alone.

For an NFC ID card (staff, student, visitor): URL pointing to a secure profile or directory page tied to the cardholder's ID. The chip can double as access credential data in the locked memory sector, handled by the access control system, alongside a readable NDEF URL in the open sector — two functions, one card.

For an NFC event pass: URL pointing to the event app or digital ticket, or a deep link into the event's ticketing system. For a vendor or exhibitor pass, a URL pointing to the company's product catalogue or contact form turns a badge into a lead generation tool every time an attendee taps it.

All PrintedCards RFID Visiting Cards and RFID ID Cards are programmed with your specified URL or vCard data before dispatch, with a UV-printed design on the card surface. If you are unsure what to program, share your use case when placing your order and our team will recommend the right NDEF record type for your situation.