How to Test MIFARE Cards with ACS Readers

How do you test a MIFARE card with an ACS reader? First identify the card type from the ATR, or from the SAK, the ATS or the card's version data. Then run the read test that suits that type. For MIFARE Classic, load the factory key FF FF FF FF FF FF, authenticate one data block and read the sector's data blocks. For MIFARE Ultralight and NTAG, read the pages directly, because no key is needed, and check the NDEF area. For MIFARE DESFire, confirm the card type and its version only, and leave key tests to a tool built for DESFire.

This is a test procedure for cards you own, using the factory keys or keys you already know. It works with ACS PC/SC readers such as the ACR1252U, ACR1552U and ACR122U. You can send the commands from the free ACS Script Tool, or use the BSD NFC Card Utility instead of typing commands. If a card fails authentication, this page explains what that means. It does not cover finding or recovering a key you do not have. Need cards rather than a test? See our MIFARE cards page.

Not yet tested by BSD. The commands on this page follow the ACS reader manuals (ACR1252U API manual v1.17, ACR1552U reference manual v1.09, ACR122U API manual v2.04) and the NXP documents listed under Sources. BSD has not yet recorded hardware results for this page. We will add them after our test session.

  • A working reader. The ACS driver must be installed and Windows must see the reader. If you are not sure, start with installing the ACS driver on Windows and checking the PC/SC reader status.
  • A tool that sends commands. The ACS Script Tool or the ACS Web APDU Tool both work. Free ACS QuickView is enough for the identification step. All three are on the tool chooser on our testing hub. If you prefer buttons to commands, use the BSD NFC Card Utility for the ACR1252U or ACR1552U.
  • Spare test cards you own. Use a new MIFARE Classic 1K card, an NTAG sticker and a new DESFire card. Never test with a card that is in use in a live system, such as an access, canteen or membership card.
  • The card's UID first. Read and note the UID before anything else, so every result in your log belongs to a known card. Our guide to reading an NFC card UID with an ACS reader covers that step.
  • Connect to the contactless (PICC) interface. The ACR1252U and ACR1552U show two readers in Windows, a contactless one (its name contains "PICC") and a SAM slot. Send these commands to the PICC reader.

The commands below that start with FF are pseudo-APDUs. The ACS reader carries them out itself and turns them into the card's own MIFARE commands. Responses end in a status word. 90 00 means success. 63 00 means the operation failed. On the ACR1552U, other 6X XX codes are also possible.

Each card type needs a different test, so find out what the card is before you send any key or read command. Use the methods in this order.

A. Read the ATR the reader builds

When a contactless card is placed on the reader, the ACS reader builds an ATR for Windows. QuickView and the Script Tool both display it. For cards that do not use the ISO 14443-4 protocol, such as MIFARE Classic and Ultralight, the ATR has a fixed layout. It contains the PC/SC registered ID A0 00 00 03 06, a standard byte (03 = ISO 14443A part 3), and a two-byte card name. The ACS manuals give this example for a MIFARE Classic 1K card:

3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 01 00 00 00 00 6A

Reading from the left: A0 00 00 03 06 is the registered ID, 03 is the standard (ISO 14443A part 3) and 00 01 is the card name (MIFARE Classic 1K). The last byte is a checksum.

Card name bytes in the ATRCard type (ACS manuals)Test to run
00 01MIFARE Classic 1KMIFARE Classic test
00 02MIFARE Classic 4KMIFARE Classic test (larger sectors from sector 32 on)
00 26MIFARE MiniMIFARE Classic test (a smaller card)
00 03MIFARE Ultralight (the ACS tables have no separate NTAG entry)Ultralight / NTAG test
00 3AMIFARE Ultralight C (ACR1252U and ACR1552U manuals)Ultralight page read. Its protected pages need a 3DES key, which this page does not cover.
Short ATR such as 3B 81 80 01 80 80An ISO 14443-4 card. The ACS manuals give this ATR as the MIFARE DESFire example.DESFire detection

For ISO 14443-4 cards the ATR carries the historical bytes from the card's ATS instead of a card name, so the ATR alone does not prove a card is a DESFire. Use part C as well.

B. Read the SAK (where the reader supports it)

The SAK is the byte the card sends while it is being selected. NXP's MIFARE type identification note (AN10833) lists these values for cards that do not support a version command:

SAKMeaning (NXP AN10833)
08MIFARE Classic 1K (MIFARE Plus in security level 1 can also use 08)
18MIFARE Classic 4K (or MIFARE Plus 4K in security level 1)
00MIFARE Ultralight family, which includes NTAG. NXP notes the whole Ultralight family uses the same SAK.
20ISO 14443-4 card (bit 6 set), for example DESFire. Use the version check in part C.

How you read it depends on the reader. The two manuals use different P1/P2 bytes for this command:

  • ACR1252U (firmware 110.0 or later): FF CA 00 02 00 returns ATQA (2 bytes) + UID + SAK + 90 00.
  • ACR1552U: FF CA 02 00 00 returns ATQA + UID + the last SAK + 90 00.
  • ACR122U: its API manual has no SAK command, so use the ATR.

NXP itself does not recommend SAK or ATQA for exact identification. On newer cards such as DESFire EV3, the SAK can be configured. Treat the SAK as a quick check, not as proof.

C. ATS and version data (the reliable check)

  • FF CA 01 00 00 asks the reader for the ATS of an ISO 14443-4 Type A card. If an ATS comes back, the card speaks ISO 14443-4, as DESFire cards do. MIFARE Classic and Ultralight cards have no ATS.
  • NXP recommends the card's own GetVersion command for exact identification. In the second byte of the reply, the lower half gives the family: 1 = MIFARE DESFire, 3 = MIFARE Ultralight, 4 = NTAG. For DESFire this is part of the DESFire detection step. For NTAG and Ultralight EV1, the GetVersion command is not one of the ACS pseudo-APDUs, so use the BSD utility's automatic detection or the capability container check below.

D. Or let the BSD utility detect it

The BSD ACR1252U and ACR1552U NFC Card Utilities have an Auto-detect card type setting. It reads the ATR first and then sends a few read-only commands: the UID, the Ultralight/NTAG header pages, and the ATS plus GetVersion for ISO 14443-4 cards. It then opens the right tab (MIFARE Classic, NTAG / Ultralight or DESFire) and shows the card name, its UID and its memory size. Card identity is free in these utilities. Reading and writing card data needs a BSD licence key.

A MIFARE Classic 1K card has 16 sectors of 4 blocks, with 16 bytes in each block. In each sector, the last block is the sector trailer: it holds key A, the access bits and key B. Block 0 is the manufacturer block, with the UID. The test reads the data blocks of sector 1 (blocks 04, 05 and 06). It never touches block 0 or a sector trailer.

  1. Load the factory key into the reader. Send FF 82 00 00 06 FF FF FF FF FF FF. This stores the key in the reader's volatile key location 00. It does not talk to the card yet. Expected: 90 00. ACS readers have two volatile locations (00 and 01), and they are cleared when the reader is unplugged, so load the key again after a reconnect.
  2. Authenticate block 04 with key A. Send FF 86 00 00 05 01 00 04 60 00. The data bytes are: version 01, 00, block 04, key type 60 (key A; 61 = key B), and key location 00. Expected: 90 00. One successful authentication opens every block in the same sector.
  3. Read the data blocks. Send FF B0 00 04 10 (16 bytes from block 04), then FF B0 00 05 10 and FF B0 00 06 10. Expected: 16 data bytes followed by 90 00. A new card usually returns all zeros, but the manufacturer may have put other data there.
  4. Try a second sector. Authenticate block 08 (sector 2) the same way and read blocks 08 to 0A. If two sectors pass, the reader, the card and the factory key all work.
  5. Log the result. Note the UID, the sectors read, the key type and 90 00 or the error code (see test log).
// MIFARE Classic 1K read test, sector 1 (blocks 04-06). Send to the PICC reader.
FF 82 00 00 06 FF FF FF FF FF FF      -> 90 00   load key FF..FF into location 00
FF 86 00 00 05 01 00 04 60 00         -> 90 00   authenticate block 04, key A, location 00
FF B0 00 04 10                        -> 16 bytes + 90 00
FF B0 00 05 10                        -> 16 bytes + 90 00
FF B0 00 06 10                        -> 16 bytes + 90 00
// Do NOT read or write 07 (the sector 1 trailer) in this test.

MIFARE Classic 4K

Sectors 0 to 31 are laid out like a 1K card, with 4 blocks and the trailer in the 4th block. Sectors 32 to 39 have 16 blocks each: for example, sector 32 is blocks 80 to 8F, and its trailer is 8F. To test a large sector, authenticate block 80 and read FF B0 00 80 10. Only on the ACR1252U, the manual also allows reading 240 bytes (15 data blocks) at once, with FF B0 00 80 F0.

Differences between ACS readers

ReaderRead length per command (MIFARE Classic)Note from the ACS manual
ACR122UUp to 16 bytes (one block)Same FF 82 / FF 86 / FF B0 layout. ACS advises a 2-second delay when reading NDEF data on MIFARE Classic 4K cards.
ACR1252U16 bytes, or up to 48 bytes (3 data blocks) on a 1K card and 240 bytes on a 4K cardThe trailer must be read in single-block mode only.
ACR1552UAny length up to 255 bytes (short form)The upper half of P1 picks the mode: 0 = skip trailers, 8 = include trailers. Keep P1 = 00 so trailers are skipped.

Optional write test, on a spare card only

Only if you need to prove writing works. Pick a data block, for example 04. Authenticate it, then write 16 bytes with FF D6 00 04 10 followed by 16 data bytes. Read the block back and compare. Then write zeros back. Never point this command at block 00 or at a trailer block. ACS warns in the ACR1552U manual that wrong data in a sector trailer can lock the card. The BSD utility does this write-and-read-back test for you on factory-key cards.

Ultralight and NTAG tags store data in 4-byte pages. There is no MIFARE Classic key: the ACS manuals say Ultralight memory needs no authentication, so do not send FF 82 or FF 86. One FF B0 command reads 16 bytes, which is 4 pages (the ACR122U and ACR1252U manuals give 16 bytes as the maximum for Ultralight).

  1. Read pages 0 to 3. Send FF B0 00 00 10. Expected: 16 bytes + 90 00. Pages 0 to 2 hold the 7-byte serial number, its check bytes and the static lock bytes. Page 3 is the one-time-programmable area, which on NTAG holds the capability container.
  2. Read the first user pages. Send FF B0 00 04 10 (pages 4 to 7). Expected: 16 bytes + 90 00.
  3. Do the NDEF check (below).
  4. Tap it with a phone. If the tag holds an NDEF link or text, an NFC phone should show it. An empty but NDEF-formatted tag shows nothing or "empty tag", depending on the phone.

The NDEF read check

NFC phones read NDEF data, the NFC Forum format for links and text. A tag is ready for NDEF when its capability container (page 3) starts with E1. NXP's NTAG213/215/216 datasheet gives these values for new tags:

TagPage 3 at delivery (CC)NDEF areaUser pagesPages 4-5 at delivery
NTAG213E1 10 12 00144 bytes04 to 2701 03 A0 0C 34 03 00 FE
NTAG215E1 10 3E 00496 bytes04 to 8103 00 FE 00 00 00 00 00
NTAG216E1 10 6D 00872 bytes04 to E103 00 FE 00 00 00 00 00

How to read pages 4 onward. The data is a list of blocks, each made of a type byte, a length byte and the value (a TLV). Skip any block that is not type 03: on a new NTAG213, the first block is 01 03 A0 0C 34. Then find 03, the NDEF message:

  • 03 00 followed by FE means the tag is formatted but empty. This is normal for a new tag.
  • 03 followed by a length such as 0F means an NDEF message of that many bytes follows. Read enough pages to cover it. The BSD utility decodes it and shows the link or text.
  • If page 3 is 00 00 00 00, or there is no 03 block at all, the tag is not NDEF-formatted. It still works for UID-based systems, but a phone will not read data from it.

The CC and the lock bits are one-time programmable: bits can be set but never cleared. Never write to pages 2 or 3 in a test. If a read of some pages fails while pages 0 to 3 read, part of the tag may be password-protected. This guide does not cover password-protected tags.

DESFire cards do not use MIFARE Classic sectors or the FF 82 / FF 86 / FF B0 commands. Their files sit inside applications, protected by DES, 3DES or AES keys, and access needs encrypted authentication. A manual test should therefore stop at detection and version:

  1. Check the ATR. ACS gives 3B 81 80 01 80 80 as the DESFire ATR example: a short ATR for an ISO 14443-4 card.
  2. Read the ATS. Send FF CA 01 00 00. Expected: the ATS bytes + 90 00. This confirms an ISO 14443-4 Type A card.
  3. Read the version. GetVersion is the DESFire command 60. In an ISO 7816 wrapper, send 90 60 00 00 00. The card answers in three parts: send 90 AF 00 00 00 while the reply ends in 91 AF (more data). The last part ends in 91 00. In the first part, a second byte whose lower half is 1 means a MIFARE DESFire card (NXP AN10833). The last part includes the card's UID. GetVersion needs no key.
  4. Stop there. Listing applications, authenticating and reading files are DESFire-specific tasks. Use the BSD utility for factory-key cards, or your own application for cards with your keys. Our smart card reader SDK hub lists the developer resources.

Windows note from the ACR1552U manual: when a card is placed on the reader, Windows Smart Card Plug and Play may send it an APDU. That can switch a DESFire card into ISO APDU mode, so native (unwrapped) DESFire commands fail until the card is reset. Windows usually resets it after about 10 seconds of inactivity. If native commands fail on a fresh card, lift it and present it again, or use the wrapped form above.

The BSD utility's DESFire factory-key test

The DESFire tab of the BSD ACR1252U and ACR1552U NFC Card Utilities has a Test Card (read-only) button. It writes nothing to the card. It:

  1. confirms the card is a MIFARE DESFire (GetVersion) and shows its UID;
  2. lists the applications on the card ("none" on a blank card);
  3. tries the card's master key with the factory default (all-zero DES) key;
  4. if that works, reads the key settings and the free memory, and reports that the card still has its factory keys and is ready for a write test.

If step 3 fails, the utility reports that the key is not the factory key. The card has been issued with its own keys, and the Default Key edition stops there by design (see what a failed authentication means).

If FF 86 returns 63 00 (or a 6X XX code on the ACR1552U), the reader could not prove it knows the key for that sector. Go through these points in order:

  1. Was the key loaded? The volatile key locations are cleared when the reader is unplugged or the PC sleeps. Send FF 82 again, then authenticate.
  2. Is the card really MIFARE Classic? Ultralight, NTAG and DESFire cards do not accept a MIFARE Classic authentication. Repeat step 1.
  3. Right block, key type and location? Check that the block is in the sector you mean, that 60 is used for key A, and that the key location matches the one you loaded.
  4. Did the card stay on the reader? Moving the card resets it, and you must authenticate again. Keep it flat and still.
  5. Key B fails but key A works? Whether key B may be used depends on the sector's access bits. A key B failure on a new card does not necessarily mean the key is wrong.

If all of these check out, the most likely reason is simple: the card has its own key. Cards issued for access control, canteen, transport or membership systems usually have their keys changed from the factory value. That is the point of the keys.

  • If it is your card system, use the key your system or card supplier gave you. The BSD utilities' Custom Key edition works with your own keys and is supplied on request: ask for the Custom Key edition.
  • If it is not your card, stop. Testing is for cards you own or are authorised to manage, with keys you already know. This page and BSD's tools do not cover finding or recovering card keys.
  • Need new cards with known keys? Use new cards, which come with the factory keys. See MIFARE cards from BSD Infotech.

Five rules that keep test cards usable

  • Never write a sector trailer. On a 1K card these are blocks 03, 07, 0B, 0F, 13, 17, 1B, 1F, 23, 27, 2B, 2F, 33, 37, 3B, 3F. A 4K card has the same up to 7F, then 8F, 9F, AF, BF, CF, DF, EF, FF. A wrong key or wrong access bits there can lock the sector for good.
  • Never write block 0 (the manufacturer block with the UID), or pages 0 to 3 of an Ultralight or NTAG tag (serial number, lock bytes and the one-time-programmable CC).
  • Write only to a spare card, only to data blocks, and one block per command.
  • Do not change DESFire keys or format a DESFire card while testing. Leave key management to your application.
  • Label every test card and keep it apart from live cards.

A test log turns "it worked yesterday" into evidence you can show a supplier or a developer. Keep one row per card per test:

ColumnExample
Date and tester2026-12-02, initials
Card label and typeT-01, MIFARE Classic 1K
UIDAs returned by FF CA 00 00 00
ATR / SAK / ATSATR card name 00 01, SAK 08
Reader, firmware, WindowsACR1252U, firmware as shown by QuickView, Windows 11
Test and key usedRead sector 1, key A factory (never write the key itself into a shared log for real keys)
Result90 00, data all zeros / 63 00 at authentication
NotesCard moved once, re-authenticated
CardIdentifyRead test with commandsRead test without commands
MIFARE Classic 1K / 4KACS QuickView (ATR)ACS Script Tool or Web APDU Tool: FF 82, FF 86, FF B0ACS Smart Card and Reader Tool (ACS lists MIFARE Classic), or the BSD utility (factory key)
MIFARE Ultralight / NTAGQuickView (ATR), then page 3Script Tool: FF B0 00 00 10, FF B0 00 04 10Smart Card and Reader Tool (Ultralight), or the BSD utility (NTAG tab: read and write links or text)
MIFARE DESFireQuickView (ATR), FF CA 01 00 00Script Tool: GetVersion 90 60 00 00 00 onlyBSD utility: Test Card (read-only), factory keys

The ACS tools are free from ACS. The BSD utilities are a free download after a one-time email check, and reading or writing card data in them needs a licence key. Details and download links are in the BSD utilities section of the testing hub. Model guides: ACR1252U driver, software and test guide, ACR1552U driver and test guide, ACR122U driver and software guide.

What you seeLikely causeWhat to do
No ATR, or the tool says no cardCard not in the field, wrong reader selected (SAM instead of PICC), or the card is not a 13.56 MHz cardSelect the PICC reader, place the card flat on the marked area, and check the reader with our PC/SC status guide.
FF 82 returns 63 00Wrong length or wrong key locationUse Lc = 06, exactly 6 key bytes and location 00 or 01.
FF 86 returns 63 00Key not loaded, wrong card type, or the card has its own keyWork through what a failed authentication means.
FF B0 returns 63 00 on a MIFARE Classic cardThe block is not authenticated, or it is in a different sector from the one authenticatedAuthenticate a block in the same sector, then read.
FF B0 fails on an Ultralight or NTAG tagLength is not a multiple of 4 or is over 16 bytes, the page is beyond the tag's memory, or the page is password-protectedRead 10 (16 bytes) from a page inside the user range in the NTAG table.
Commands work and then suddenly failThe card was moved, or another program (for example, an ACS or BSD tool left open) connected to itClose the other tools, present the card again, and repeat from the key load.
DESFire native commands fail on a fresh cardWindows Plug and Play put the card into ISO APDU modeUse the wrapped 90 60 00 00 00 form, or lift the card and present it again.
6A 81The reader or card does not support the command, for example a SAK request on a reader without itCheck the command bytes against your reader's manual (they differ between models, see step 1).

Commands, response codes, ATR layouts and memory maps were checked in the ACS reader manuals, and card identification and NTAG memory facts were checked in NXP documents, on 17 Nov 2026:

BSD Infotech is an independent ACS supplier and integrator, not the manufacturer. ACS, the ACS logo and ACS product names belong to Advanced Card Systems Ltd. MIFARE, MIFARE Classic, MIFARE Ultralight, MIFARE DESFire and NTAG are trademarks of NXP B.V.

MIFARE cards not reading as expected?

Tell us the reader, the card type and the error code. We help with ACS reader testing, card selection and MIFARE or DESFire integration.