NTAG 213/215/216 NFC Cards and TagsCustom NFC Cards for OEM, Integration and Bulk Supply

The right NFC IC depends on what your project must prove, not only how many bytes it needs. NTAG 213/215/216 suits many standard NDEF applications. NTAG 223/224 DNA is worth evaluating when an application needs AES-128-protected Secure Unique NFC (SUN) message authentication; NTAG 224 DNA adds AES-128-based three-pass mutual authentication for protected memory access.

Quick answer

·Choose NTAG 213/215/216 when the main requirement is a standard NFC interaction—such as opening a URL, sharing a business profile or providing product information—and its memory capacity is sufficient.

·Consider NTAG 223 DNA when you need dynamic SUN message authentication and 144 bytes of user memory, with password-based memory protection.

·Consider NTAG 224 DNA when you need dynamic SUN message authentication plus AES-128-based mutual authentication for protected memory access.

A secure IC is one part of an authentication design. Verification software or backend logic, cryptographic key management, NDEF configuration and deployment testing still matter.

1. NTAG 223/224 DNA vs NTAG 213/215/216: At a Glance

All five ICs operate at 13.56 MHz and support NFC Forum Type 2 Tag / ISO/IEC 14443 Type A communication. Their principal differences are user memory and security functions. The NTAG 21x family includes a 32-bit password function and an ECC-based originality signature, but it does not provide the same AES-128-protected SUN dynamic message authentication mechanism available in NTAG 223/224 DNA.

Values above describe the ICs, not guaranteed finished-card or label performance. Configuration options and enabled functions should be confirmed against the selected IC's current NXP data sheet.

2. The Main Difference Is Authentication, Not Memory Size

It is easy to compare NFC chips by memory alone, but memory is not a reliable measure of security. NTAG 223 DNA has 144 bytes of user memory—the same as NTAG 213. NTAG 224 DNA has 208 bytes, which is less than NTAG 215's 504 bytes and NTAG 216's 888 bytes. The DNA variants are relevant when a project needs cryptographically authenticated NFC messages, not simply a larger NDEF payload.

What NTAG 213/215/216 already provides

The NTAG 21x family supports standard NDEF interactions, a 7-byte UID, a configurable 32-bit password protection function and an ECC-based originality signature. Depending on the selected IC and configuration, UID or NFC counter information can also be mirrored into an NDEF message. These are useful capabilities, but they should not be described as equivalent to verifying an AES-128-protected SUN message on each interaction.

What NTAG 223/224 DNA adds

NTAG 223 DNA and NTAG 224 DNA support Secure Unique NFC (SUN) message authentication using AES-128 cryptography. Dynamic information such as a UID and NFC counter can be mirrored into the NDEF message with a cryptographic message authentication code (CMAC), allowing a compatible verification process to check message authenticity and integrity. NTAG 224 DNA additionally supports AES-128-based three-pass mutual authentication for protected memory access.

3. How SUN Authentication Fits into a Product-Verification Workflow

1. Tap: A user taps an NFC-enabled phone or compatible reader on the card, label or tag.

2. Read: The NFC IC returns the configured NDEF content, which may include mirrored data such as a UID, counter and SUN authentication code.

3. Verify: A compatible application or backend validates the authentication code using the correct cryptographic key and checks relevant application rules, such as whether the counter is plausible or has already been used.

4. Respond: The application displays an appropriate result or connected-product experience, based on the verification outcome.

The chip provides the cryptographic capability; the project team must define how the message is configured, how the key is securely provisioned and stored, how the backend validates requests, and what happens when verification fails. A plain URL that opens successfully is not, by itself, proof that the physical product is genuine. NXP publishes separate technical documentation for configuring and verifying NTAG 22x authentication.

4. When Is Standard NTAG 213/215/216 Enough?

Choose an NTAG 21x IC when the objective is primarily to deliver information or trigger a simple connected experience, and the application does not require SUN dynamic message authentication.

·Digital business cards and contact sharing.

·Opening a website, landing page, digital manual or product-information page.

·Marketing campaigns, smart posters, coupons and interactive advertising.

·Membership or event experiences based on standard NFC data.

·Bluetooth or Wi-Fi pairing workflows supported by the target devices.

·Product identification where the required security level is met by the overall design and no SUN verification workflow is needed.

For many simple projects, select by payload size first: NTAG 213 for compact data, NTAG 215 for a larger record and NTAG 216 when the application needs the most user memory in this group. Validate actual NDEF length and encoding overhead rather than estimating from the URL alone.

5. When Should You Evaluate NTAG 223/224 DNA?

Evaluate NTAG 223/224 DNA when the NFC interaction needs a cryptographically authenticated message—for example, a verification workflow intended to make simple copying of a static URL or NDEF record insufficient.

·Product authentication and brand-protection programs.

·Authentication-enabled product packaging or labels.

·Warranty validation, product registration and after-sales checks.

·Connected-product experiences that rely on checking a dynamic authenticated message.

·Selected cosmetics, electronics, premium consumer goods or healthcare-related product applications, where the complete deployment meets applicable requirements.

NTAG 223 DNA or NTAG 224 DNA?

Both support SUN message authentication. NTAG 223 DNA provides 144 bytes of user memory and password-based protected memory access. NTAG 224 DNA provides 208 bytes and adds AES-128-based three-pass mutual authentication for protected memory access. Choose based on the access-control design and security requirements, not on a blanket assumption that one IC is always the right choice.

6. What the Chip Alone Does Not Guarantee

No NFC IC should be presented as a complete anti-counterfeiting system on its own. A secure deployment needs a defined threat model and a correctly implemented verification process. Before making a product-authenticity claim, confirm:

·Cryptographic key management: who creates, provisions, stores, rotates and controls access to keys.

·Verification logic: how the application checks CMAC data, counters, duplicate scans and failure cases.

·Backend and user experience: where the verification result is generated and how suspicious or offline scans are handled.

·Device compatibility: whether the intended phones, readers and application can read the tag and perform the required validation.

·Physical product design: how the antenna, IC, card or label material, adhesive, product surface and environment affect RF performance.

NTAG 21x originality-signature functionality can support verification that an IC originates from NXP, but that is not the same as proving that a particular finished product came through an authorized brand owner's supply chain. Likewise, a valid SUN message must be checked by a compatible verifier; its mere presence in a readable NDEF record is not enough.

7. Card or Tag Manufacturing: What Buyers Should Confirm

Chip specifications and finished-product specifications are different. An NFC card and an NFC label can use the same IC family but need different antenna layouts, substrates, assembly methods and environmental testing. For a card project, RFIDKST lists customization options such as chip selection, CR80 or custom dimensions, card materials, printing, surface finishes, identification elements, NDEF encoding and packaging on its product page. Tag and label constructions should be confirmed for the exact inlay, antenna, substrate, adhesive and finish before they are offered as a confirmed configuration.

For a B2B quotation, prepare the following information where available:

1. Chip preference: NTAG 213, 215, 216, 223 DNA or 224 DNA.

2. Form factor: card, label, sticker, inlay or another tag construction.

3. Target memory use: NDEF content, expected payload length and any serialization fields.

4. Security requirement: standard NDEF, originality-signature verification, SUN message authentication, or mutual authentication for protected memory.

5. Verification architecture: target smartphone or reader, mobile app or browser flow, backend availability and key-management owner.

6. Physical specifications: dimensions, material, thickness, printing, surface finish, adhesive and packaging requirements.

7. Order details: estimated quantity, sample requirement, target delivery date and destination market.

8. Sample Approval and Pre-Production Testing

Before approving bulk production, confirm both the physical product and the intended NFC workflow.

·Test samples on representative phones and/or readers used by your customers.

·Check read consistency on the finished card or label—not only on a bare IC or inlay.

·Verify NDEF payload, URL behavior, encoding, UID/counter mirroring and SUN validation where applicable.

·Test expected and failed authentication responses, including repeated scans and backend connectivity cases.

·Review print quality, dimensions, material, finish, packaging and any agreed serialization requirements.

·Agree how sample approval, production encoding, inspection records and acceptance criteria will be documented.

For security-sensitive work, define in writing which party is responsible for key injection, secret-key custody, software, backend verification and final security testing. Do not assume these are included in a card or tag manufacturing order unless the supplier has confirmed the scope.

9. Frequently Asked Questions

Does NTAG 213 support AES-128 SUN authentication?

NTAG 213 includes security-related features such as 32-bit password protection and an ECC-based originality signature, but it does not provide the same AES-128-protected SUN dynamic message authentication feature available in NTAG 223/224 DNA.

Is NTAG 224 DNA more secure than NTAG 216?

NTAG 224 DNA adds SUN message authentication and AES-128-based mutual authentication for protected memory access. NTAG 216 provides much more user memory—888 bytes versus 208 bytes. Whether NTAG 224 DNA is suitable depends on the required security functions, implementation and threat model, not on a universal “more secure” ranking.

Does NTAG 223 DNA have more memory than NTAG 213?

No. Both provide 144 bytes of user memory. The reason to evaluate NTAG 223 DNA is its additional SUN message authentication capability, not additional storage.

Can a normal NFC smartphone verify a SUN message?

A compatible smartphone can read the NFC content, but cryptographic verification requires software and access to the correct verification process and keys. A server-based workflow is common, but the project architecture must be designed and tested; opening a URL alone does not automatically validate a SUN message.

Does an NTAG DNA chip automatically prevent all counterfeiting?

No chip can guarantee that an entire product and supply chain are counterfeit-proof by itself. SUN can provide cryptographically authenticated dynamic data, but the verifier, key-management process, backend rules, tag deployment and response to suspicious scans are all part of the protection design.

Should I choose an NFC card or an NFC label?

Choose the format that fits the product, user interaction and physical environment. Cards are useful when the project needs a durable credential or hand-held card format. Labels may better suit packaging and individual items, but antenna geometry, adhesive, substrate and placement must be evaluated for the actual product.

10. Request a Quote for a Custom NFC Card or Tag

Shenzhen Kaisere Technology supports B2B buyers evaluating custom NFC card configurations. Share your chip preference, form factor, quantity, physical specifications and encoding requirements so the team can review the manufacturing scope for your project. If your application needs cryptographic verification, specify the required SUN or mutual-authentication workflow and identify who will provide the verification software and manage keys.

Planning a custom NTAG 223 DNA or NTAG 224 DNA card project?

Send your target application, quantity, card or tag format and security requirements for a project-specific quotation.

Request a Quote for NTAG 223/224 DNA Cards

Related Resources

·NTAG 223/224 DNA Cards Manufacturer | Secure NFC Card Supplier

·NTAG 213/215/216 NFC Cards | Custom OEM Manufacturer

·What Is NTAG 213/215/216 Used For?

·NFC Tag & Label Products

·RFID Anti-Counterfeiting Label Products