RFID Smart Card Manufacturer

Smart card chip options and security features

A smart card specification starts with the chip, because the chip determines what security the system can ever achieve — no amount of backend hardening compensates for a credential that can be cloned at the doorstep. The four families below cover nearly every security-grade card program we manufacture. All are current-production parts sourced through direct allocation channels, and all support diversified per-card keys rather than a single shared secret.

• AES-128Encryption standard
• 28DESFire EV3 apps
• DualContact + contactless
• AN10922Key diversification

• MIFARE DESFire EV3 — AES-128 encryption, up to 28 independent applications, transaction MAC for secure offline verification, and proximity check against relay attacks. The default recommendation for transit, campus and corporate badge systems.
• MIFARE Plus SE: AES-128 security in a MIFARE Classic-compatible memory layout, for upgrading legacy access control without replacing every reader — the cost-effective security migration path.
• Java Card: GlobalPlatform-compliant multi-application platform supporting custom applets for government ID, healthcare cards, transport and PKI-based authentication.
• NTAG 424 DNA — AES-128 authentication with SUN (Secure Unique NFC) messaging for smartphone-verified authentication, digital product passports and tamper-evident credentials.
• Dual-interface architecture: a single chip module wired to both a contact pad (ISO 7816) and an embedded antenna (ISO 14443) for programs that need tap convenience and contact-level security on one card.

Where security-grade cards get deployed

Chip choice follows the deployment, not the other way around. The application families below account for most of the smart card volume leaving our Shenzhen lines — including transit programs we ship millions of cards into annually across multiple countries. Each has a different balance of offline operation, transaction speed and revocation requirements, which is exactly the conversation to have before locking a chip family.

• Transit and fare collection: DESFire EV2/EV3 cards with multi-application layouts, transaction MAC for offline validation, and high-volume encoding on dedicated lines.
• Corporate and enterprise badges: AES-128 credentials replacing broken MIFARE Classic estates, with diversified keys so one compromised card never exposes the population.
• Campus and student ID: multi-application cards combining door access, library, canteen payment and attendance on a single credential.
• Closed-loop payment and stored value: DESFire-based cards that can hold encrypted balance data for offline-capable cashless programs, plus gift and loyalty stored-value formats.
• Hotel and hospitality locks: DESFire and MIFARE Plus cards encoded for compatibility with major lock platforms — covered in depth on our hotel-lock compatibility pages.
• Brand authentication: NTAG 424 DNA cards whose per-tap SUN cryptograms let a backend verify authenticity and detect cloning.

Secure personalization and key handling at the factory

The difference between a smart card vendor and a smart card manufacturer shows up in personalization. We run encoding and key management as a documented production discipline: customer key material moves over encrypted channels, loads onto air-gapped encoding stations, and is deleted after production per your retention instructions — with optional escrow of master keys only on explicit customer instruction. Every personalized card is functionally verified before it ships.

1. 1. Key exchange

   Key hierarchies and personalization scripts transferred via encrypted channels under NDA.

2. 2. Scheme lock

   Application structure, file access rights and diversification method locked on the production traveler.

3. 3. Personalization run

   Key loading and data writing on air-gapped stations in a controlled environment.

4. 4. Verification

   100% functional test including authentication handshake on every card.

5. 5. Disposal & records

   Key material deleted per instruction; encoding logs retained for traceability.

• Key diversification for MIFARE Plus, DESFire and NTAG 424 DNA following the NXP AN10922 method, so every card carries unique derived keys.
• Application setup: DESFire application directories, file structures, access conditions and initial data values created to your personalization script.
• Air-gapped key loading: encryption keys are never stored on networked systems; transfer is via encrypted channels and material is deleted after production completion.
• Sector keys and access conditions locked before issuance — an unlocked card can be rewritten by anyone with a USB reader.
• 100% verification: every card is tested for contactless response, authentication handshake and memory operations, with results documented in the shipped test report.

Migration paths off legacy cards

Most smart card purchases are migrations, not green-field deployments — usually away from MIFARE Classic, whose CRYPTO-1 cipher has been publicly broken since 2008 and can be cloned with commodity tools. The wrong move is changing cards and readers simultaneously. The options below are the migration sequences that keep a live estate working while security improves, and we supply sample cards for compatibility testing before any volume order.

• Classic to MIFARE Plus SE: AES-128 in a Classic-compatible layout means existing readers keep working while cards upgrade — replace readers later on their own budget cycle.
• Classic or EV2 to DESFire EV3: EV3 is backward compatible with EV2 infrastructure and adds transaction MAC, proximity check and SUN messaging; we recommend EV3 for all new deployments.
• Mixed estates: dual-interface or dual-chip cards bridge sites where some doors read contact modules or legacy LF while new infrastructure reads ISO 14443.
• Do not specify MIFARE Classic for new secure deployments — we still produce it for low-risk legacy programs, but for anything guarding value, start at MIFARE Plus SE or DESFire.
• Compatibility validation: free samples of candidate chips let your integrator test against the actual reader fleet before committing — included with every program.

Compliance posture for security programs

Security-grade card programs get audited harder than any other card purchase, so the paper trail is part of the product. Production runs under an ISO 9001:2015 quality system with records retained for at least seven years and retrievable by encoding lot. Shipments carry the compliance documentation buyers need at customs and at security review, and third-party attestation can be commissioned when a program requires it.

• Standards conformance: ISO/IEC 7810 physical format, ISO/IEC 14443 contactless interface, ISO/IEC 7816 contact interface for dual-interface cards.
• Per-shipment documentation: commercial invoice and packing list with chip family and encoding lot, Certificate of Origin, radio-compliance conformity documents (FCC / CE as applicable) and RoHS / REACH material declarations.
• Functional test report on the encoded lot included with every shipment, with full batch traceability of date, operator and equipment.
• Quality records retained at least seven years per ISO 9001 — retrievable by SKU or encoding lot if a field issue or audit requires it.
• Third-party audit accommodation: TÜV, SGS, Intertek and Bureau Veritas visits supported; programs requiring a specific certification framework (for example ISO 27001) can have the audit path scoped into an annual-volume agreement.

FAQ