RFID Card Printing Checklist: Chips, Encoding and Sample Approval

For custom printed RFID cards, approve the reader requirements, exact chip, encoding plan, artwork and tested sample before a bulk order. A card that looks right can still fail in the intended system. This checklist helps purchasing teams, card printers and resellers prepare a clear brief for an RFID card manufacturer.

1. Describe the application and installed readers

State what the card must do: hotel access, staff identification, membership or an NFC link to a website. Record reader or lock models, encoder details and the relevant software version. Ask the system provider to confirm its credential requirements.

A requirement such as “13.56 MHz card” is incomplete. Frequency does not specify the full protocol, memory, application configuration or reader workflow. For hotel projects, also use the hotel key card compatibility checklist.

2. Specify the chip and physical card

Give the chip manufacturer, full model, revision where relevant, required memory and the specification approved by your system provider. Record whether the order needs blank, printed or prepared cards. If a model is undecided, mark it for technical review before production approval.

For example, NXP lists different memory capacities, file structures and configurable access rights for MIFARE DESFire EV3. Its product documentation describes the chip; it does not establish that a finished card will work with every installed reader or application.

• Confirm finished dimensions, thickness and material against the project drawing.
• List surface finish, any magnetic stripe, holes or other physical features.
• Agree how chip sourcing and the approved specification will be documented. See our MIFARE chip specification and authenticity guide.

3. Separate printed data from chip encoding

A printed serial number, barcode and chip identifier are different data items. State which values must match and provide the mapping format. Agree who supplies the data, who prepares the chip and who verifies the final result.

For encoded orders, define the approved data structure, required read/write behavior and acceptance method with the authorized system team. Keep production keys and private credentials out of public inquiry forms; arrange their handling with the responsible team through an agreed secure process.

For an NFC website card, confirm the final destination and NDEF record requirements. Apple describes background tag reading using an NDEF URI record. Test the actual card on the intended phones and software; a printed QR code does not prove the NFC function. Read our iPhone NFC and sample-testing guide.

4. Approve artwork and a functional sample

Prepare separate front and back files using the card artwork templates. Show print colors, finishes and variable-data positions. Request a proof for text, layout and numbering, then agree whether a physical sample is needed for color and finish approval.

A digital artwork proof checks the design. Functional approval requires a representative card tested through the intended reader, encoder and application workflow.

• Check the agreed reading and encoding operations on the actual equipment.
• Verify printed numbers or barcodes against the approved data mapping.
• Test handling conditions relevant to the project and record any failed step.
• Keep the approved sample, specification version and written acceptance result.

5. Record packing, delivery and repeat-order details

List quantities by artwork version, bundle sizes, carton labels and any split destinations. Give the delivery country and required arrival date so the team can review production and shipping separately. Confirm the final schedule after specification and sample review.

For repeat orders, reference the previous purchase order and approved sample. Check for changes to readers, software, artwork, data ranges or chip requirements before assuming the previous specification still applies. Overseas printers can include their work split and packing requirements when requesting trade and subcontract card manufacturing.

Buyer questions

Can I order using only the RFID frequency?

Frequency alone is insufficient for an installed system. Confirm the exact credential specification and sample acceptance before approving a replacement or bulk order.

Does printing a card also encode it?

Printing and chip preparation are separate operations. State whether cards should be supplied unencoded or with a specifically reviewed encoding process.

What if the chip model is not known yet?

Share the application, reader model and existing specification with the manufacturer and system provider. Keep chip selection open for review rather than approving an assumed equivalent.