
MIFARE cards and NFC: a practical guide to choosing the right card
A MIFARE card contains a contactless chip from NXP’s MIFARE product family. The family name alone does not tell you whether a card will work with your door reader, ticketing system or phone. You need the exact chip variant, the right encoding and a compatible system.
This guide separates MIFARE Ultralight EV1 and AES, Classic, Plus and DESFire from the broader term NFC. Start with what the card must do, then check the technical requirements before choosing the printed design.
Sources checked: . This is a buying guide, not a security assessment or a compatibility guarantee for a particular installation.
What is a MIFARE Card?
MIFARE is NXP’s family of contactless ICs used in applications such as tickets, passes and access credentials. A card combines the chip with an antenna and a physical construction; the reader and software determine how it is used.
Cards that look identical may use different chips or data structures. Equally, the same chip can be configured for different applications. For a replacement or expansion project, obtain the existing system specification rather than ordering from a photograph or a generic “MIFARE compatible” label.
For a printed-card project, explore RFID card printing after your system provider has confirmed the technical requirements.


MIFARE Ultralight EV1 and AES are different variants
Ultralight EV1 is designed for applications including limited-use transport tickets, event passes and loyalty. Its 32-bit password feature protects memory operations; NXP explicitly cautions that this is not high-security protection. Do not describe EV1 as having AES authentication.
Ultralight AES is a separate variant with AES authentication using 128-bit keys and 144 bytes of user memory. Whether it fits a project still depends on the reader, application and configuration.
References: NXP Ultralight EV1 data sheet, revision 3.3 and NXP Ultralight AES product information.
Classic, Plus and DESFire: what to check
- MIFARE Classic EV1: check existing-system requirements carefully. NXP labels the product as not recommended for new designs and points designers towards DESFire Light. That is not an instruction to replace a deployed credential without an integration plan.
- MIFARE Plus EV2: offers AES-128 authentication and secure messaging, with migration features for Classic-based infrastructure. Confirm the required security level and reader/software support; compatibility is not a blanket guarantee.
- MIFARE DESFire EV3: supports multiple applications and files, with cryptographic options including AES. It can be considered for more complex credential systems, but chip features alone do not establish the security of an installation.
References: NXP’s Classic EV1, Plus EV2 and DESFire EV3 product pages.


MIFARE versus NFC: will a smartphone read the card?
NFC describes short-range contactless communication, not one interchangeable chip. A phone detecting a card is different from reading its application data, opening a website or acting as an authorised access credential.
For a link-sharing tag, NDEF is a standard way to structure the stored message. Android documents NDEF support and separate APIs for other tag technologies. The chip, encoding, phone hardware, operating system and app support all affect the result.
For example, NXP’s NTAG213/215/216 products are NFC Forum Type 2 tags; that does not make a protected MIFARE access credential equivalent to a public website tag. Test the actual finished card and intended phones.
References: Android NFC basics and NXP NTAG213/215/216 data sheet. For the networking use case, see NFC business cards.
Quick comparison: match the card to the system
| Variant | Distinction | Confirm before ordering |
|---|---|---|
| Ultralight EV1 | Password-protected memory; not AES authentication | Exact ticket/application format and reader support |
| Ultralight AES | AES authentication; separate from EV1 | Application setup and reader support for this variant |
| Classic EV1 | Legacy-system requirements; NXP does not recommend new designs | Existing configuration and future migration plan |
| Plus EV2 | AES features and migration options | Security level and infrastructure compatibility |
| DESFire EV3 | Multi-application/file features | Application, key management and system integration |
Use the linked manufacturer documents above for exact specifications. None of these entries promises FDS stock, pricing or compatibility with a named third-party system.


What to include in your card specification
- Purpose: public link sharing, membership identification, ticketing or controlled access.
- Existing system: reader model, software provider and the required chip variant.
- Data: encoding format, personalisation fields and who will supply approved data.
- Administration: who enrols, replaces or revokes cards and controls any keys or accounts.
- Physical requirements: material, dimensions, printing, numbering and expected handling.
- Acceptance test: a sample checked against the real reader/software or intended phones before a larger run.
Do not send secret keys or customer/member data through a public enquiry form. Agree a suitable data-transfer and integration process with the responsible provider.
Test before you print a full batch
Ask your system provider to approve a representative sample. Test more than basic detection: does the card perform the intended action, use the right identifier and behave correctly after enrolment or replacement?
For a public profile or website link, test the destination as well as the tap. For an access or ticketing project, let the authorised system operator perform the relevant checks. Record the card specification, system version and result so that a reorder uses the same approved configuration.


Choose the complete solution, not just the family name
MIFARE Ultralight, Classic, Plus and DESFire are not interchangeable labels. Start with the system specification and the required action, confirm the exact variant, and approve a sample before production.
For manufacturing enquiries, see RFID card printing. For sharing a contact profile, see NFC business cards. You can also contact FDS Cards with your non-sensitive requirements to discuss the next step.
Choose your MIFARE card in three steps
The right MIFARE card starts with your reader and application, not the printed design. Use this short specification checklist before requesting samples or placing a card-printing order.
- Confirm the systemAsk the operator for the supported chip family, exact variant and required data format. A shared frequency alone does not establish compatibility.
- Agree the card setupConfirm personalisation, encoding, enrolment and replacement requirements. Keep public NFC links separate from protected access credentials.
- Test a finished sampleCheck the actual card with the intended reader, software and phones where relevant. Approve the tested construction before ordering the full quantity.
Discuss the physical card through RFID card printing. For a public digital profile, compare NFC business cards.
Need a simpler explanation of public-link tags? Read how NFC contactless technology works. A completed checklist is a planning aid, not a compatibility certificate.
By FDS Cards · Editorial update
Frequently Asked Questions
A contactless card containing a chip from NXP’s MIFARE family. The exact variant and system configuration determine its function; the family name alone does not prove compatibility.
No. EV1 uses password protection for memory operations. Ultralight AES is a separate variant with AES authentication. Check the exact product specification.
Do not assume so. Detecting a card, reading a public NDEF message and accessing a protected application are different tasks. Chip, encoding, device and software support must be checked.
Ask the authorised system provider for the exact supported chip and application requirements. Approve a sample on the intended reader/software; a generic chip-family recommendation is not enough.
Ask for the current construction and supplier evidence for the specific card. This guide does not verify FDS availability or environmental claims for a material.