How to Read an NFC Card UID Using an ACS Reader (No Code)
← Back to the ACS reader testing and utilities centre
How do you read an NFC card's UID with an ACS reader without writing code? Place the card on the reader and either open a free BSD reader utility, which shows the UID as soon as it identifies the card, or send the standard PC/SC command FF CA 00 00 00 from the ACS Script Tool or Web APDU Tool. The reply is the UID followed by 90 00. An ACR1552U can also be set to type the UID into any program, like a keyboard.
The harder part is matching the UID between systems. The same card can appear as A1B2C3D4, D4C3B2A1, 2712847316 or 3569595041 depending on byte order and whether the software shows hexadecimal or decimal. This guide explains which is which, so the number your reader shows matches the number your attendance, access or canteen software expects.
BSD Infotech is an independent ACS supplier and integrator in New Delhi, not the manufacturer. ACS tools are linked to acs.com.hk. Reading the UID in your own program is covered on the smart card SDK pages; this page needs no programming.
What a Card UID Is
Before a contactless card can exchange any data, the reader has to pick it out from any other cards in the field. In ISO/IEC 14443 (the standard behind MIFARE, NTAG and DESFire cards) this selection step is called anti-collision, and the identifier the card reports during it is the UID. The reader learns the UID before any key or password is involved, which is why every reader can show it and why so many attendance, door and canteen systems use nothing else.
NXP, the maker of MIFARE chips, points out in its application note on UIDs that a UID is an identifier, not a serial number, and that some UIDs are not even unique. Keep that in mind if you plan to use it as a person's ID: it is fine for recognising a card, but it is not a security feature, because the UID can be read by any reader without a key.
UID length: 4, 7 or 10 bytes
ISO/IEC 14443 allows three sizes for Type A cards. NXP calls them single size (4 bytes), double size (7 bytes) and triple size (10 bytes). In the 2018 revision of that note, NXP said no card used a 10-byte UID yet, but every reader must support one. Other card families report different identifiers, and the PC/SC standard lists their lengths for the Get Data command.
| Card or tag | Identifier you get | Worth knowing |
|---|---|---|
| MIFARE Classic 1K / 4K | 4 bytes, or 7 bytes on 7-byte UID versions | Older cards use 4-byte UIDs. NXP has run out of unique 4-byte values, so newer 4-byte cards may carry a re-used or fixed non-unique ID (NUID). 7-byte versions exist too. |
| MIFARE Ultralight and NTAG21x | 7 bytes | The first byte is the chip maker's code: 04 means NXP. So NXP tags all start with 04, and the useful variation is in the later bytes. |
| MIFARE DESFire EV1 / EV2 | 7 bytes, or a random 4-byte ID | If the card's random ID option is switched on, it shows a new 4-byte value starting with 08 every time it is powered up (see below). |
| ISO 14443 Type B cards | 4-byte PUPI | Type B cards report a "pseudo-unique PICC identifier" rather than a UID. |
| ISO 15693 (vicinity) tags | 8 bytes | Only on readers that support ISO 15693, such as the ACR1552U. See the note on byte order below. |
| FeliCa | 8 bytes | The ACR122U API manual says this ID is read with the same Get Data command. |
Contact cards such as the SLE memory cards used in an ACR39U do not have a UID in this sense. The PC/SC standard says a reader answers 6A 81 when the card has no UID.
Random UIDs: when a card never shows the same number twice
NXP defines a random ID (RID): a 4-byte UID whose first byte is 08, with the other three bytes generated fresh each time the card powers up. Taking the card off the reader and putting it back gives a new value. NXP lists the random ID as an option on MIFARE Classic EV1, MIFARE Plus and MIFARE DESFire EV1 and EV2 cards. The real UID can then only be read with card-specific commands after the card is selected, which in practice means software that holds the card's keys. A UID that starts with 08 and changes on every tap is a card setting, not a reader fault.
Hex, Decimal and Byte Order: Why the Same Card Shows Different Numbers
This is the most common UID problem in real projects. The card is fine and the reader is fine, but the number printed on the card, the number in the old system and the number in the new reader do not match. There are three separate causes, and it helps to check them one at a time.
1. The bytes and their order
A UID is a list of bytes, not a number. The PC/SC standard (Part 3), which ACS readers follow, fixes how a reader must return it: the bytes come back in the same order the card sent them during anti-collision, with the first byte received first. The reader must not turn the bytes into an integer. So FF CA 00 00 00 gives the same byte order on any PC/SC reader, and that order is the safest one to store.
Trouble starts when some software reverses that list. ACS's own ACR1552U reference manual has a setting for exactly this in keyboard mode: default order (UID byte 0 first, the order the card sent) or reverse order (last byte first). A reader or program set to reverse order shows D4 C3 B2 A1 for a card that the Get Data command reads as A1 B2 C3 D4. Both are the same card.
2. Hexadecimal or decimal
ACS tools and BSD utilities show the UID in hexadecimal (digits 0 to 9 and letters A to F, two characters per byte). Many attendance and access systems, and the number printed on some cards, use a decimal number instead. Converting is simple, but NXP's note says plainly that there is no standard rule for turning the bytes into one number, so different systems do it differently:
| How the system reads the bytes | Example UID A1 B2 C3 D4 becomes | Where you see it |
|---|---|---|
| Hex, as read | A1B2C3D4 (or A1 B2 C3 D4, a1:b2:c3:d4: same value) | ACS Script Tool, Web APDU Tool, BSD utilities |
| Decimal, first byte as the most significant | 2712847316 | Software that converts the hex string as written |
| Decimal, first byte as the least significant (bytes reversed, then converted) | 3569595041 | Software that treats the UID as a little-endian number. The ACR122U API manual labels the first returned byte "LSB", so this reading is common. |
| Decimal, byte by byte | 161 178 195 212 | Each byte converted on its own. The ACR1552U keyboard mode lists this as a display option. |
A 7-byte UID works the same way, with longer numbers. For example 04 A2 2B 5A 3C 5E 80 converts to 1304206988041856 as written, or 36132410322821636 with the bytes reversed. (These are example values, not real cards.)
3. Leading zeros and shortened numbers
- Leading zeros: the UID
0A 1B 2C 3Dis169552957in decimal, only nine digits. A system that stores ten digits writes it as0169552957. If one side drops the zero and the other keeps it, a text comparison fails even though the number is the same. In hex, keep both digits of every byte:0A, notA. - Part of the UID only: some systems were built for 4-byte cards and keep only four bytes of a 7-byte UID, or only the last few digits of the decimal number. ACS's ACR1552U keyboard settings include a "4-byte UID only" option and fixed-length formats with names such as
8H-10Dand14H-17D. The names appear to give the number of hex digits taken and decimal digits output, but the reference manual does not explain them in words, so try your own card before you rely on one.
The format we meet most often
In the attendance, access control and membership systems BSD Infotech connects ACS readers to, the most common card number is a 10-digit decimal number made from a 4-byte UID, padded with leading zeros (like 0169552957 above). The usual reason for a mismatch is byte order: one system converts the bytes as read, the other converts them reversed. Try both orders with the steps below before changing any settings.
How to match a UID between two systems, step by step
- Read the card with
FF CA 00 00 00(method 3 below) and write the reply down in hex, without the final90 00. This is your reference value. - Compare it with what the other system shows. If that is also hex, check whether it is the same bytes in reverse order.
- If the other system shows decimal, open the Windows Calculator, choose Programmer mode, select HEX, type the reference value without spaces and read the DEC line. Then type the bytes in reverse order and read DEC again. One of the two should match, apart from leading zeros.
- If neither matches, check the length: the other system may use only part of the UID, or the card may have a random ID (it starts with
08and changes on every tap). - Write down the rule you found (for example "decimal, bytes reversed, 10 digits with leading zeros") and give it to whoever sets up the next reader or software, so new cards are enrolled the same way.
ISO 15693 tags: these UIDs are usually printed with the first byte E0, but the tag sends the bytes the other way round. If a Get Data reply ends in E0, you are looking at the same UID in the order the tag sent it. The BSD ACR1552U utility shows these UIDs starting with E0. Not yet tested by BSD with an ACS reader.
Before You Read a UID
- The reader must be installed and seen by Windows. If you are not sure, run the step-by-step NFC reader test on Windows first, or the driver guide for your model: ACR1252U, ACR1552U or ACR122U.
- Pick the contactless reader, not the SAM slot. Readers with a SAM slot, such as the ACR1252U and ACR1552U, appear as two readers in Windows. Cards are read through the one whose name contains PICC (or "CL").
- One card at a time. Keep other cards, phones and wallets away from the reader, and hold the card flat and still in the middle.
- Close other card programs. If another program is connected to the card, a second one may be refused. See checking PC/SC reader status for the "sharing violation" error.
Not yet tested by BSD. The steps on this page follow the ACS manuals, the PC/SC specification and the behaviour of BSD's own utilities. BSD has not yet recorded the results with each ACS reader and card type; they will be added after our hardware test.
Method 1: The Free BSD Reader Utility
BSD Infotech's Windows utilities for ACS readers show the card's identity, including the UID, as soon as a card is placed on the reader. Card identity is free; only reading and writing card data needs a BSD licence key in the ACR1252U and ACR1552U utilities. They are BSD software, not ACS products, and are downloaded after a one-time email check (OTP).
- Download the utility for your reader: ACR1252U, ACR1552U or ACR122U. Install it on Windows 10 or 11 with the reader plugged in.
- Open the utility and place one card on the reader. Expected result: the card type and the UID appear, for example
A1B2C3D4. - Note the UID. The utility shows it in uppercase hex with no spaces, in the same byte order as the
FF CA 00 00 00command in method 3, because that is the command the utility sends. (ISO 15693 tags are the exception: see the note at the end of the byte order section.)
Which cards: the ACR1252U and ACR1552U utilities identify MIFARE Classic, NTAG and Ultralight, DESFire and other ISO 14443 cards (the ACR1552U one also ISO 15693 tags). The ACR122U utility is built for MIFARE Classic 1K cards. The full list for each is in the BSD utilities table on the testing hub.
Method 2: ACS QuickView
ACS QuickView is a free ACS tool for Windows, macOS and Linux. ACS describes it as a tool that reads and displays reader and card details and watches for cards arriving and leaving. It is the quickest way to confirm the card is detected.
- Download QuickView from the ACS utility tools page (acs.com.hk, opens in a new tab) and open it with the reader plugged in.
- Select the contactless (PICC) reader and place the card on it. Expected result: QuickView shows that a card is present, with its details.
- Look for the UID or serial number in the card details. If your QuickView version shows it, note it in hex. If you see only the ATR, use method 3.
Do not use the ATR as the card's ID. For contactless memory cards the ATR is built by the reader from the card type, not from the card itself. The ACR1552U reference manual, for example, lists one fixed ATR for every MIFARE Classic 1K card. Two different 1K cards therefore give the same ATR but different UIDs.
Not yet tested by BSD: which card details QuickView v2.18 (the version ACS listed on 17 Nov 2026) shows for each card type, and whether it labels a UID field. This section will be updated after our hardware test.
Method 3: Send FF CA 00 00 00 from the Script Tool or Web APDU Tool
This is the reference method, because it shows exactly what the reader returns. FF CA 00 00 00 is the Get Data command defined in the PC/SC specification (Part 3) and documented in the ACS manuals for the ACR122U, ACR1252U and ACR1552U. The reader answers it itself, so it works the same way for MIFARE Classic, Ultralight, NTAG, DESFire and the other cards the reader supports, with no key.
ACS Script Tool
A Windows program that sends APDU commands and scripts to ACS PC/SC readers. Separate macOS and Linux versions exist.
Free · ACS utility tools page
ACS Web APDU Tool
Runs in Chrome or Edge. It needs the ACS APDU Bridge browser extension and the APDU Bridge Host program installed first. ACS lists Windows 10 or later and all ACS USB readers.
Free · ACS Web APDU Tool page
Steps
- Open the tool and choose the contactless (PICC) reader.
- Place one card on the reader and leave it there, then connect to the card if the tool asks.
- Send
FF CA 00 00 00. Expected result: a reply such asA1 B2 C3 D4 90 00. - Remove the last two bytes.
90 00is the status word; everything before it is the UID. Count the bytes: 4, 7 or another length from the table above.
What each byte of the command means
| Byte | Value | Meaning |
|---|---|---|
| CLA | FF | Class byte that PC/SC readers use for commands the reader handles itself, rather than passing to the card. |
| INS | CA | Get Data. |
| P1 | 00 | Return the UID. (01 asks for the ATS of an ISO 14443-4 Type A card instead.) |
| P2 | 00 | No other option. |
| Le | 00 | Return the full length, whatever it is. Leave it at 00 so 4-, 7- and 8-byte identifiers all come back complete. |
Status words: what the last two bytes mean
The table lists only codes documented for this command in the ACS manuals (ACR122U API manual v2.03, ACR1552U Series reference manual v1.05) and in PC/SC Part 3. The ACR1552U manual documents 90 00 for success and says any 6X XX reply means the command failed.
| Reply ends with | Meaning | Documented in | What to do |
|---|---|---|---|
90 00 | Success. The bytes before it are the UID. | ACS manuals, PC/SC Part 3 | Note the UID. |
63 00 | The operation failed. | ACR122U API manual | Usually the card moved or left the field. Hold it flat and still in the centre and send again. |
6A 81 | Function not supported. | ACR122U API manual, PC/SC Part 3 | PC/SC says this is the reply when the card has no UID, such as a contact card. Check the command bytes and that you selected the PICC reader. |
62 82 | Warning: end of data reached before Le bytes. | PC/SC Part 3 | You asked for more bytes than the UID has. Send Le 00. |
6C XX | Wrong length. XX is the real UID length. | PC/SC Part 3 | You asked for fewer bytes than the UID has (for example Le 04 on a 7-byte card). Send again with Le 00. |
67 00, 68 00, 6B 00 | Wrong length, wrong class byte, wrong P1-P2. | PC/SC Part 3 (common error codes) | The command was mistyped. Retype FF CA 00 00 00. |
| No reply, "no card" error | No card was connected when the command was sent. | Windows PC/SC | Place the card first, connect, then send. |
Not yet tested by BSD: which of these status words each ACS reader actually returns in each case. The ACR1252U and ACR1552U also document FF CA 00 02 00 for extra card data (ATQA, UID and SAK); it is not needed for reading the UID.
Method 4: A Reader That Types the UID (Keyboard Mode)
Some ACS readers can act like a USB keyboard: tap a card and the reader types the UID into whichever program has focus, such as Notepad, Excel, a web form or existing attendance software. No driver, tool or code is needed on the PC once the reader is set up. ACS sets this mode with its ACR15XX Keyboard Configuration Tool, and lists the ACR1552, ACR1555U-A1 and ACR1581 among the supported readers. In this mode the reader reads ISO 14443 Type A and Type B cards and sends the UID as keyboard input, not through PC/SC.
Which readers can do it
| Reader | Keyboard mode | What to use |
|---|---|---|
| ACR1552U | Yes, with the ACS Keyboard Configuration Tool | Steps in the ACR1552U guide's keyboard tool section. |
| ACR1581U | Listed by ACS for the same tool | Not yet tested by BSD. |
| ACR1252U | No | Methods 1 to 3, or software that reads the UID through PC/SC. |
| ACR122U | No | Methods 1 to 3. |
ACS also makes a dedicated UID reader, the ACR1281U-C2 Card UID Reader, which only types UIDs and has its own configuration tool on the ACS utility tools page.
Settings that change the number the reader types
The ACR1552U Series reference manual (v1.05) lists the keyboard-mode settings below. They are the reason one ACR1552U types A1B2C3D4 and another types 3569595041 for the same card, so check them before you blame the card.
- Output order: default (the order the card sent) or reverse.
- Display mode: hex, decimal, decimal byte by byte, or one of the fixed-length formats such as
8H-10D. - UID length: 4-byte UIDs only, or 4, 7, 8 and 10 bytes.
- Letter case of hex output: upper or lower case.
- Characters typed before the UID, between bytes and after it, for example a separator or an Enter key at the end.
- Keyboard layout: English, French or Lithuanian. If Windows uses a different layout, typed characters can come out wrong.
- Host interface: keyboard only, PC/SC (CCID) only, or both. If it is set to keyboard only, PC/SC tools such as QuickView and the BSD utilities can no longer see the reader.
Which of these settings the Configuration Tool shows on screen may depend on its version. To test, open Notepad, click inside it and tap a card: the UID should appear as typed text. Compare it with method 3 using the step-by-step check in the byte order section.
Not yet tested by BSD: the keyboard output formats on the ACR1552U and ACR1581U. Results will be added after our hardware test.
Troubleshooting UID Problems
The same card reads different UIDs
| What you see | Likely cause | What to do |
|---|---|---|
A new 4-byte value on every tap, always starting with 08 | The card's random ID option is on (DESFire EV1/EV2, MIFARE Plus, MIFARE Classic EV1) | The UID cannot be used as an ID for this card. Use cards with the random ID switched off, or software that reads the card's real ID with its key. BSD can build that software. |
| A phone gives a different value on each tap | Phones emulating a card often do not present a fixed UID | Do not enrol phones by UID. Use a physical card or an app-based method. |
| Two programs show different numbers for one card | Different byte order, hex vs decimal, or leading zeros | Follow the step-by-step matching check; both numbers are usually the same UID. |
| Sometimes one UID, sometimes another | Two cards in the field, for example a second card in the same wallet | Present one card at a time. |
| An ACR1552U types a different number than before | Keyboard-mode settings changed (order, display mode or length) | Check the settings with the ACS Keyboard Configuration Tool. |
The bytes are in reverse order
| What you see | Likely cause | What to do |
|---|---|---|
New reader shows D4C3B2A1, old system has A1B2C3D4 | One side reverses the byte list | Decide which order your system stores, then set the reader (ACR1552U keyboard mode: output order) or the software to match. Do not re-enrol cards one by one. |
| Decimal numbers do not match at all | One side converts the bytes as written, the other reversed | Convert both ways in the Windows Calculator (Programmer mode). One of them will match. |
An ISO 15693 UID ends in E0 | The UID in the order the tag sent it; the printed form starts with E0 | Reverse the bytes to compare with the label. |
No UID at all
| What you see | Likely cause | What to do |
|---|---|---|
Reply 63 00, or "no card" | The card moved, or was placed after connecting | Hold the card flat and still, connect again and resend. |
Reply 6A 81 | Contact card, wrong reader selected (SAM instead of PICC), or a mistyped command | Select the PICC reader; retype FF CA 00 00 00. Contact cards have no UID. |
| The card is not detected at all | A card type the reader does not support, such as an ISO 15693 tag on a reader without ISO 15693 | Check the supported cards on the model page; try a MIFARE Classic or NTAG card to prove the reader. |
| No reader in the tool's list | Driver, Smart Card service, or an ACR1552U set to keyboard-only output | Follow the NFC reader test on Windows from step 1; for the ACR1552U, check its host interface setting. |
| "Sharing violation" or "in use" error | Another program is connected to the card | Close it. See PC/SC reader status checks. |
| Keyboard mode types nothing | Focus is not in a text field, the reader is in PC/SC-only mode, or the card is not ISO 14443 | Click inside Notepad first; check the host interface setting; use an ISO 14443 card. |
Sources
Tool names, versions, platforms and supported readers were checked on the official ACS pages on 17 Nov 2026. Command and status-word details come from the ACS manuals and the PC/SC specification listed below; UID facts come from NXP's documentation.
- ACS utility tools (QuickView v2.18, Script Tool 5.2, ACR15XX Keyboard Configuration Tool, ACR1281U-C2 Configuration Tool)
- ACS Web APDU Tool (requirements and supported readers)
- ACS ACR122U Application Programming Interface v2.03 (Get Data command and status words) and ACS ACR1552U Series Reference Manual v1.05 (Get Data command, PICC ATR, keyboard-mode output settings), from the ACS download pages for ACR122U and ACR1552U
- PC/SC Workgroup specifications, Part 3 v2.01.09: Get Data command, UID format and byte order, status words
- NXP AN10927, MIFARE product and handling of UIDs (Rev. 4.1): UID sizes, random ID, NUID, manufacturer code
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, DESFire and NTAG are trademarks of NXP B.V.
