Skip to content

RFIDAK / Custom contactless credentials

Custom RFID cards.
Matched to
your system.

RFIDAK supplies plastic, clamshell, wood, paper and custom-shape RFID cards for access, hotel keys, membership, ticketing and NFC interactions. Choose the card body here, then confirm the chip, printing and encoding against your reader or phone workflow before sampling.

RFID card samples with printed artwork, wood grain and a visible antenna inlay
One card body can contain different chips.
Appearance alone does not establish compatibility.

Five physical formats

How will the card be carried?

Choose the surface, shape and handling.
Confirm the electronics separately.

ABS clamshell cards

Thicker proximity credentials

ABS clamshell cards ↗

A rigid body for projects that need a thicker card and a badge attachment point.

Confirm: Reader protocol, holder fit and slot position.

Confirm print method; check printer thickness limits.

Wood & bamboo cards

Hospitality & tactile branding

Wood & bamboo cards ↗

A natural-grain surface for engraved or printed branding. Approve grain, edge finish and flatness on a physical sample.

Confirm: Chip compatibility, species, thickness and moisture exposure.

Engraving or printing matched to the selected wood.

Paper RFID cards

Tickets & temporary credentials

Paper RFID cards ↗

A paper-based format for a defined service period, with the chip and data plan matched to the ticketing system.

Confirm: Handling, moisture, ticket life and issuer requirements.

Artwork and variable ticket data by specification.

Custom-shape & epoxy cards

Branded NFC interactions

Custom-shape & epoxy cards ↗

A shaped credential with an optional domed finish. Specify the NFC experience, shape and attachment before sampling.

Confirm: Target phone or reader, dimensions, dome and mounting.

Custom artwork with a reviewed outline and antenna layout.

Converting your own cards? Explore card inlays / prelam. For hands-free carrying, compare RFID wristbands or key fobs.

The compatibility check

A matching frequency
is only the start.

“125 kHz” or “13.56 MHz” describes a frequency. It does not confirm the chip protocol, data format or permission to use an installed system.

Swipe to compare the system checks.

Card workflow, starting point and required compatibility checks
Your workflowStart hereConfirm before ordering
Existing access or hotel systemMatch the current credential and issuance process.Reader / lock model, software version, current chip and operator approval.
New access or campus projectDefine application and security needs with the integrator.Supported chip, data layout, provisioning and a complete sample transaction.
NFC phone interactionPlan the content and experience after a deliberate tap.Target phones, NDEF content, memory and any application or verification service.
UHF reading workflowUse a compatible UHF reader and a suitable card construction.Country, reader, antenna, mounting and required reading distance.

Approve issuance and use.

Test the proposed sample through the actual issuer, then the intended reader or lock. For protected credentials, the system operator should confirm the approved provisioning process. A successful UID scan is only one check.

From design to issued credential

Three approvals.
One usable card.

Keep physical fit, visible artwork and chip data in the same specification. Approve a representative sample before releasing the production order.

Common ID-1 footprint85.60 × 53.98 mm

Often called CR80. Confirm thickness and finished construction separately.

ISO/IEC 7810:2019 reference ↗
  1. Card body & equipment fit

    Confirm finished width, height, thickness, material, corners and any slot. For on-site printing, check the exact printer, surface and feed limits. Locate punches outside the approved antenna area.

  2. Artwork & visible data

    Approve front and back proofs, colors, finish, photo or name placement, numbering, barcode or QR readability. Specify quantities per artwork and how each card maps to your source records.

  3. Encoding & acceptance

    Define writable fields, numbering format, issuer setup and read-back criteria. Keep manufacturer-set identifiers separate from project data. Agree handling of duplicates and failed records, then approve the sample with the system operator.

Build a useful inquiry

Start with what
you already know.

Choose the application, card body and supply format. Your choices become an editable inquiry draft, with space for the reader model, artwork, quantity and delivery requirements.

Request separate sample, setup, unit price and freight costs. Availability, MOQ and timing depend on the reviewed configuration.

Skip these choices and contact us →

Review and complete the draft on the next page. Nothing is sent until you submit the contact form.

Buyer questions

Before you order.

Reviewed September 9, 2026.

How do I choose an RFID card for an existing reader or hotel lock?

Start with the exact reader or lock model, issuer software and current working credential. Matching 125 kHz or 13.56 MHz alone is insufficient: the chip protocol, data format and provisioning must also match. A reader detecting a chip does not prove it can authorize the credential. Have the system operator approve an end-to-end sample test before a bulk order.

What size and thickness should I specify?

The ID-1 footprint commonly called CR80 is 85.60 × 53.98 mm. Thickness and construction must be specified separately: a clamshell, wood card or epoxy shape may not fit equipment intended for a flat plastic card. Confirm the finished drawing, holder, slot position, printer feed and surface requirements. The card footprint does not establish electronic compatibility.

Should I choose MIFARE Classic, Plus or DESFire?

Use the installed system and its security requirements to define the chip choice. NXP directs security-relevant MIFARE Classic applications toward its DESFire and Plus families. These are not universal drop-in replacements: readers, issuance software, application data and key management must support the intended mode. Ask the integrator to approve the migration and test the complete issuance-to-use workflow.

Can a phone read every 13.56 MHz RFID card?

No. Phone support, protocol, data layout and permissions all matter. For a tap that opens a web page, specify an NFC-capable chip, the NDEF content and target phones. A protected access application may require its own software and credentials. An NFC website tap is a different task from opening a hotel door, even when both credentials operate at 13.56 MHz.

Can cards be supplied with a custom UID or encoded numbering?

Distinguish the chip identifier from writable application data and visible print. For example, NXP NTAG213/215/216 have manufacturer-programmed UIDs. A project number or URL can instead be placed in suitable writable memory and matched to a printed serial or QR code. Define the required field, byte order, output file and read-back check; agree protected provisioning with the system operator.

Can I print blank RFID cards on my own card printer?

Confirm the printer model, supported card material, thickness, surface and ribbon or retransfer process. A printer that prints the card face may not encode its RFID chip. Test feeding, print adhesion and any encoding module with the proposed blank stock. Approve artwork and variable-data mapping before ordering preprinted cards, and keep any punch clear of the antenna.

Are wood and paper RFID cards recyclable or compostable?

A wood or paper face does not establish the disposal route for the complete RFID card. The chip, antenna, adhesives, coatings and local collection rules all matter. If an environmental claim is required, request documentation covering the exact finished construction and order. Treat material appearance, sourced-fibre certification and finished-product compostability as separate questions.

What are the price, MOQ, sample terms and lead time?

The chip, card body, artwork, encoding, quantity per design and packing determine the quote. State the sample and production quantities, destination and required arrival date. Ask for sample, setup, unit price and freight separately. Stock availability, custom-sample charges, any credits and the production schedule are confirmed after the specification is reviewed; use the sample policy when planning a trial.

Technical references: NXP MIFARE Classic guidance · DESFire EV3 capabilities · NTAG UID and writable memory. Chip documentation does not establish compatibility or certification of a finished card.

WhatsAppGet a Quote