Blog

You have ordered thousands of custom NFC cards, and each card needs to open a distinct web landing page, verify a unique member account, or trigger a specific device action. How does that communication actually work on the silicon level? This engineering guide breaks down the physical architecture of programmable NFC cards — from chip memory structure and NDEF payload encoding to write protection and factory serialization workflows.

What Makes an NFC Card "Programmable"?

A programmable NFC card is built with an integrated circuit containing writable EEPROM memory. Operating at the international 13.56 MHz high frequency (ISO/IEC 14443 Type A), the microchip draws power via magnetic induction when placed within the RF field of an NFC-enabled smartphone or commercial reader.

Upon power-up, the chip transmits its stored data payload: opening a browser URL, importing a contact card, authenticating a member ID, or launching a dedicated application. Explore our factory catalog of customizable NFC Cards.

The NDEF Standard: The Universal Language of NFC

NDEF (NFC Data Exchange Format) is the global data specification established by the NFC Forum. It ensures consistent, interoperable data exchange across diverse hardware, operating systems (iOS and Android), and reader chipsets.

Core NDEF Record Types

• URI Record (Type 'U'): Encodes web URLs with standardized compression prefix bytes (e.g., 0x04 for https://), maximizing user memory efficiency. This is the industry standard for digital business cards, interactive product packaging, and Google review stands.
• Text Record (Type 'T'): Encodes plain text accompanied by an ISO language code for localized messaging.
• MIME Type Record: Encodes structured data packages such as vCard contact records (text/vcard) or JSON payloads.
• Android Application Record (AAR): Forces an Android device to launch a specific package name, redirecting to Google Play if the app is not currently installed.

Chip Memory Sizing: NTAG213 vs NTAG215 vs NTAG216

Selecting the correct chip capacity prevents paying for unused silicon or running out of memory during automated encoding:

NDEF URL Encoding vs UID-Based Cloud Lookup

When engineering high-volume NFC deployments, clients choose between two fundamental architectural models:

Write Protection: Securing Your Deployed NFC Cards

Leaving NFC cards unlocked in the field introduces serious operational risks: any passerby with a free smartphone app can overwrite the memory. Union Smart configures multi-tiered memory lock protocols during automated factory production:

1. 32-Bit Password Protection (PWD / PACK)

The standard deployment for enterprise cards: reading remains completely open to all smartphones, while write operations require a confidential 32-bit password and 16-bit password acknowledge (PACK). System administrators can update or repurpose the card later, while unauthorized users are blocked from overwriting data.

2. Permanent Hardware Lock (OTP Lock Bits)

Setting the chip's internal lock bits permanently converts specified memory blocks into read-only memory. This operation is physical and irreversible: once locked, no software command or password can unlock the chip, guaranteeing absolute data integrity for brand authentication and legal compliance.

3. Cryptographic Hardware Security (Beyond NTAG)

For applications involving financial value or high-security physical door locks where password protection is insufficient, upgrade to hardware-encrypted platforms like MIFARE DESFire EV3 Cards featuring certified AES-128 encryption.

Industrial Production Encoding: What to Specify with Your OEM

To ensure zero errors across mass-production runs, provide your card manufacturer with the following technical parameters:

• Target Silicon Model: Confirm NTAG213, NTAG215, or NTAG216 based on total payload size.
• Serialization Database: Provide a structured CSV file mapping each printed serial number or barcode to its unique NDEF URI string.
• Locking Level: Specify open rewritable, password-protected (with encrypted 32-bit key), or OTP permanently locked.
• Quality Deliverables: Require automated 100% read-back verification logs matching chip UID to programmed data.

B2B Technical & Engineering FAQ

Q1. What happens if an encoded NFC card is deployed without write protection?

Any consumer with an NFC-enabled Android or iOS phone and a standard tag-writing application can overwrite the URL or erase the chip. In public or commercial environments, production cards should always be configured with password protection or OTP permanent locks.

Q2. How does Union Smart handle high-volume unique URL encoding?

We utilize automated high-speed roll-to-roll and sheet-fed encoding lines. The machine reads each chip's unique 7-byte factory UID, queries your provided serialization dataset, writes the corresponding unique URL, locks the memory according to specification, and verifies the write in under 150 milliseconds per card.

Q3. Can NTAG cards be read through metal surfaces or mobile phone casings?

Direct contact with metal surfaces absorbs the 13.56 MHz magnetic field and prevents reading. When deploying cards inside phone cases or on metal assets, Union Smart integrates a specialized anti-metal ferrite shielding layer to maintain standard read distances.

Q4. Can NDEF data be updated on a password-protected card?

Yes. By presenting the correct 32-bit password via NFC commands, an authorized system or administrator can authenticate with the chip, rewrite the NDEF message, and re-lock the configuration.

Planning an enterprise rollout of custom-printed, serialized NFC smart cards? Contact Union Smart to speak with our smart card engineering team about custom antenna tuning, automated encoding, and volume OEM manufacturing.