Lean HF ticketing

MIFARE Ultralight Wooden RFID Cards

MIFARE Ultralight wooden RFID cards are a lean 13.56 MHz route for event tickets, simple guest credentials, limited-use access, transit-style programs, and lightweight loyalty. The exact generation matters: Ultralight EV1 supports password protection, counters, and NFC Forum Type 2 Tag behavior, while legacy Ultralight C should only be retained where an installed platform specifically requires its 3DES authentication route.

MIFARE Ultralight route brief

Frequency	13.56 MHz
Best use	Event tickets, simple guest credentials, lightweight loyalty, transit-style tickets, and programs that need a lean HF/NFC card route.
Chip route	MIFARE Ultralight or Ultralight EV1; Ultralight C only where an existing platform specifically requires its 3DES route.
Phone behavior	Can be read by NFC phones when formatted for NFC Forum Type 2 Tag behavior, but it is usually selected around a platform or reader specification.
Encoding	NDEF, UID reference, one-time or limited-use ticket data, counters, password protection, or a legacy 3DES route by chip and platform.
Approval check	Confirm the exact Ultralight generation, memory, authentication method, lock bytes, and reader or app behavior before production.

Visual references

MIFARE Ultralight wooden event credentials at check-in

Ultralight ticket data counters and lock-byte setup

Choose Ultralight from the platform specification.

Ultralight is usually selected because an event, ticketing, loyalty, or guest platform already expects its memory structure and commands. Confirm the exact product generation rather than ordering against the family name alone.

EV1 is the practical current route for lean programs.

MIFARE Ultralight EV1 supports limited-use tickets, configurable counters, lock bits, and password-protected memory. It can also support NFC Forum Type 2 Tag behavior when the phone or app workflow needs it.

Treat Ultralight C as a compatibility requirement.

Ultralight C uses 3DES authentication and is retained for installed systems that specifically require it. For a new AES-authenticated program, the dedicated Ultralight AES route should be assessed instead.

Approve the ticket logic in the final wood body.

Confirm memory size, counters, one-time data, authentication, lock bytes, app behavior, and reader response on a working wooden sample before artwork and production are released.

Best uses

Event tickets and day passes
Simple guest and visitor credentials
Lightweight loyalty programs
Transit-style and limited-use ticket routes

Frequently asked questions

What are MIFARE Ultralight wooden cards used for?

Limited-use event tickets, day passes, simple guest credentials, lightweight loyalty, and reader-led ticketing programs that need a lean 13.56 MHz credential.

Which Ultralight generation should I choose?

Use the exact platform specification. Ultralight EV1 is the practical current route for password protection, counters, lock bits, and optional NFC Forum Type 2 Tag behavior. Ultralight C is retained only where an installed system requires its legacy 3DES route.

Can phones read MIFARE Ultralight cards?

They can when the chip, NDEF layout, and app flow are configured for NFC Forum Type 2 Tag behavior. Most projects still choose Ultralight from a ticketing platform or reader requirement rather than public phone tap alone.

Specification

Card size	CR80 and custom dimensions by drawing
Card body	Plastic-free, FSC-certified wood body options
Thickness	0.80 mm to 2.0 mm by wood species and chip
Minimum order	None — single samples to production runs
Production time	About one week after artwork and sample approval
RF planning	Chip, antenna, thickness, and finish approved together
Approval route	Material sample, working RF sample, production proof
Frequency	13.56 MHz
Chip route	MIFARE Ultralight or Ultralight EV1; Ultralight C only where an existing platform specifically requires its 3DES route.
Encoding	NDEF, UID reference, one-time or limited-use ticket data, counters, password protection, or a legacy 3DES route by chip and platform.
Approval check	Confirm the exact Ultralight generation, memory, authentication method, lock bytes, and reader or app behavior before production.
Typical generations	MIFARE Ultralight EV1; legacy Ultralight C only by installed-system requirement