An NFC card sample should be approved as a complete user experience. Review the chip specification, encoded information, printed design and intended device workflow together. A successful tap on one test phone does not establish that every intended user will have the same experience.
This checklist helps buyers prepare a custom RFID or NFC card order for a web link, contact-sharing campaign or another specifically agreed application.
1. Define the action after a tap
Write down the intended result: for example, opening a mobile web page. List the target devices, operating systems and any application required. Keep this brief separate from payment or hotel-access credential requirements, which need their own confirmed specification and approval process.
Choose the exact destination page and verify that its content is ready for customers. Record who owns the destination and who will maintain it after the cards are distributed.
2. Confirm the exact chip and encoding
Specify the chip manufacturer and model, the record type, the information to encode and the agreed memory requirement. NXP lists 144, 504 and 888 bytes of user memory for NTAG213, NTAG215 and NTAG216 respectively. These capacities describe those ICs; they are not a guarantee of a particular card’s performance with every device.
Ask the production partner to review the proposed NDEF record against the selected chip. Keep a confirmed encoding example with the order rather than a general instruction such as “add our website.”
3. Test the link and printed information
Check the exact URL, capitalization where relevant, redirects, mobile layout and final destination. Test through the intended tap workflow. If the printed card also includes a QR code, test that code separately on the finished design at its approved size.
Decide whether future updates will be made to the destination web page or to the information stored on the card. Record the agreed write-protection requirement before production; confirm that it fits the maintenance plan.
4. Test the finished card construction
Use a sample representing the proposed material, finish and inlay construction. Test the sample with the agreed device list and handling conditions. Do not use a loose chip test as the only approval for a finished printed card.
Review the front and back artwork, readable text, print placement, numbering and any additional personalization. Resolve changes before signing off the sample reference.
5. Keep a clear acceptance record
- Approved artwork version and physical sample reference.
- Exact chip model and card construction.
- Confirmed encoded record and destination URL.
- Test devices, software versions, test steps and results.
- Agreed write-protection and destination maintenance responsibilities.
- Quantity, packing instructions and delivery destination.
Use this record for the manufacturing handoff and repeat orders. If a test fails, report the device and test step so the cause can be reviewed before making a production change.
Frequently asked questions
Does choosing a larger NFC memory guarantee a better tap experience?
No. Memory should suit the information being encoded. The finished construction and intended device workflow still need sample testing.
Does a working NFC link mean the printed QR code is approved?
No. Test the QR code independently, including its destination, print size and readability on the finished sample.
Source and ordering support
Memory example checked on October 2, 2026: NXP NTAG213, NTAG215 and NTAG216 documentation. This checklist does not claim universal device compatibility.
Send Vigor Smartech your NFC card specification or ask about samples before a bulk production decision.