13.56 MHz secure HF

High-security AES Metal RFID Cards

High-security AES HF is the secure end of the 13.56 MHz family: AES-128 cryptography, 2K, 4K, or 8K of memory, and a file system that lets one card carry several independent applications — door access, cashless spend inside a venue, print release — each with its own keys. Current estates specify a recent generation, and the integrator, not the card maker, defines the application map.

High-security AES route brief

Frequency	13.56 MHz secure HF
Best use	Secure enterprise, campus, premium hotel, club, and multi-application credential programs.
Chip route	high-security AES HF with 2K, 4K, or 8K memory, selected by integrator requirement and application structure.
Phone behavior	Not chosen for public NFC marketing; it is generally a secure reader credential route.
Encoding	Application IDs, files, keys, secure personalization, UID exports, cardholder mapping, and box labels.
Approval check	The integrator defines keys and encoding, then validates finished samples on the target reader.

Visual references

Brushed metal NFC card tapping a smartphone

Champagne-gold metal NFC card beside a smartphone

Gunmetal metal RFID card at a secure reader

Copper metal RFID credential on a contactless reader

Brushed metal RFID card on an LF reader test bench

Gunmetal metal credential in front of UHF gate antennas

Metal RFID card encoding and QA workstation

The integrator owns the keys — the build follows their spec.

high-security AES HF projects run in a fixed order: the access integrator specifies chip generation, application IDs, and key handling; personalization happens under their rules; the finished metal card is then validated on the target readers. What the metal changes is the RF stack around the chip — the security model stays exactly where the integrator put it.

Approve a working sample in the real environment.

The integrator defines keys and encoding, then validates finished samples on the target reader.

Best uses

Secure enterprise, campus, premium hotel, club, and multi-application credential programs.
Metal card programs that can validate a finished encoded sample on the target reader
Projects that need print, serial, QR, packaging, and data handling reconciled in one approved brief

Frequently asked questions

When does a metal card program need high-security AES HF?

When the estate requires cryptographically secure credentials or one card carrying several applications — enterprise access, campus, premium hotels, clubs with cashless spend. If the platform only checks a UID, high-security AES HF is more chip than the program needs.

What is the difference between modern AES generations?

Both use AES-128 and the same application model; The newer generation is current, with improved performance and security certifications. In practice the integrator's platform specification decides which generation is ordered.

Who defines the high-security AES HF encoding?

The access integrator: application IDs, file structures, and key handling are theirs. Cards are personalized under those rules and validated as finished metal samples on the target readers before the batch.

Specification

Format	CR80 85.6 x 54 mm by default; custom outlines after RF review
Thickness	0.3 mm to 0.8 mm depending on construction
Minimum order	None — single samples to production runs
Production time	About one week after artwork and sample approval
RF construction	Antenna, ferrite or hybrid shielding, chip, metal faces, and edge stack specified together
Chip routes	NFC tag, standard HF, high-security AES HF, LF compatibility, and selected UHF by reader test
Marking options	Laser etch, deep engraving, UV print, white ink, enamel fill, QR, serial, and controlled cut-through
Approval flow	Finish sample, encoded working sample, reader check, pre-production approval
Frequency	13.56 MHz secure HF
Chip route	high-security AES HF with 2K, 4K, or 8K memory, selected by integrator requirement and application structure.
Phone behavior	Not chosen for public NFC marketing; it is generally a secure reader credential route.
Encoding	Application IDs, files, keys, secure personalization, UID exports, cardholder mapping, and box labels.
Approval check	The integrator defines keys and encoding, then validates finished samples on the target reader.