# MIFARE DESFire EV3 Cards — AES-128 Transit & Access URL: https://proudtek.com/products/rfid-cards/mifare-desfire-ev3-card/ Source URL: https://proudtek.com/products/rfid-cards/mifare-desfire-ev3-card/ Generated: 2026-03-16T01:42:30.697Z Kind: product Publisher: Proud Tek Co., Limited Author: Proud Tek Co., Limited Credentials: ISO 9001:2015, ISO 14001:2015, RoHS Compliant, CE Marking, REACH Compliant Image: https://proudtek.com/landing-images/mifare-desfire-ev3-card.jpg Image Alt: MIFARE DESFire EV3 contactless smart card in CR80 PVC format for transit, campus access and government ID deployments ## Description MIFARE DESFire EV3 is NXP's AES-128 contactless smart card platform (ISO/IEC 14443 Type A + ISO/IEC 7816-4 APDU file system) certified to Common... ## Procurement Snapshot - Best fit: MIFARE DESFire EV3 Cards — AES-128 Transit & Access is suitable for RFID or NFC identification, access, and OEM customization projects. - Key options: Form Factor: Card format compatible with common access-control, ID, or NFC workflows. - Customization: Confirm artwork, encoding, material, chip, and finish requirements before quoting. - Quote checklist: Reference MIFARE DESFire EV3 Cards — AES-128 Transit & Access in your inquiry so the matching product page stays attached to the quote. Card format compatible with common access-control, ID, or NFC workflows. Share target chip or... ## Key Specs - Form Factor: Card format compatible with common access-control, ID, or NFC workflows. ## FAQ - Q: Is MIFARE DESFire EV3 backward compatible with our existing DESFire EV2 readers? A: Yes. DESFire EV3 keeps the full EV2 command set and AES-128 mutual authentication, so EV3 cards enrol on EV2 reader firmware without change. EV3-only features (Secure Dynamic Messaging, improved transaction timing, delegated application management) require a reader firmware update, but basic access and transit workflows continue to work on day one. We recommend pilot-testing a small EV3 batch on the existing reader estate before committing a full production run. - Q: Can DESFire EV3 cards work with our legacy MIFARE Classic readers? A: Only by running EV3 in MIFARE Classic emulation mode, which drops the card back to the CRYPTO-1 cipher and loses the AES-128 benefit — effectively a Classic card with DESFire packaging. For any new deployment we recommend upgrading the reader firmware (or, for older readers, the reader hardware) to native DESFire support before issuing cards. HID iCLASS SE, ASSA ABLOY Aperio and SALTO readers have supported native DESFire for years. - Q: What memory size should we specify — 2 KB, 4 KB or 8 KB? A: Choose 2 KB for single-purpose access-only credentials, 4 KB for two applications (access plus canteen or printing), and 8 KB for multi-application campus or government cards carrying access, meal plan, library, printing and exam authentication. The per-card chip cost difference is modest compared to the card body, printing and personalisation cost, so it is usually cheaper to specify one size larger than the current roadmap needs than to re-tool halfway through a multi-year rollout. - Q: Do DESFire EV3 cards support NFC tap-to-verify from a smartphone without an app? A: Yes. DESFire EV3 implements NFC Forum Type 4 Tag NDEF messaging plus Secure Dynamic Messaging (SDM), so every tap can generate a unique, server-verifiable URL. Any NFC-enabled iPhone (iPhone 7 and later) or modern Android device reads the URL directly in the browser — no app install. This is the same SUN-style mechanism NTAG 424 DNA uses for brand authentication, on a chip that also carries the full enterprise access credential. - Q: What Common Criteria assurance level does DESFire EV3 hold? A: NXP's DESFire EV3 chip is certified to Common Criteria EAL5+ (augmented with AVA_VAN.5 and ALC_DVS.2) per its published security target on the Common Criteria Portal. That places it above the EAL4+ level typically required for payment EMV contactless and within the range accepted for government employee credentials. The certification applies to the chip itself; the overall card product inherits the assurance provided card-body lamination, inlay bonding and pre-encoding remain under an ISO/IEC 27001 controlled process. - Q: What is the MOQ and lead time for custom-printed DESFire EV3 cards? A: Blank white DESFire EV3 cards: 100-piece minimum, ships from stock in 2–3 business days. Custom 4-colour offset printed cards with overlay lamination: 500-piece minimum, typical lead time 12–18 business days from artwork approval. Cards with pre-encoded AES-diversified application structures add 3–5 business days for encoding and QC. Every production lot ships with chip batch certificates, ISO/IEC 14443 conformance test reports and UID lists for integrator pre-loading. - Q: Can DESFire EV3 carry both an RFID credential and a magnetic stripe? A: Yes. Combi cards laminate the DESFire EV3 inlay into the PVC body and apply a HiCo 2750 Oe or LoCo 300 Oe magnetic stripe per ISO/IEC 7811-2 to the back. The two subsystems operate independently — the RFID antenna sits around the card perimeter, the magstripe lies on the rear face — so there is no electromagnetic interference. This is the standard form factor for hotel-room keys in properties still running magstripe-only doors alongside newer DESFire-capable locks. ## Machine Routes - JSON: https://proudtek.com/machine/products/rfid-cards/mifare-desfire-ev3-card.json - Text: https://proudtek.com/machine/products/rfid-cards/mifare-desfire-ev3-card.txt