ACS Web APDU Tool: Send APDU Commands from a Browser
← Back to the ACS testing and utilities centre
What is the ACS Web APDU Tool? It is a free web page from ACS (Advanced Card Systems) that sends APDU commands to an ACS USB smart card reader from Google Chrome or Microsoft Edge, and shows the reply. The page itself is hosted on acs.com.hk, but it cannot reach the reader alone. You first add ACS's APDU Bridge browser extension and install a small APDU Bridge Host program on the computer; together they pass commands from the browser to the reader. Once both are installed, open the tool, choose the reader, place a card and send FF CA 00 00 00: a reply ending in 90 00 gives you the card's UID.
This guide explains what the tool is for, how it is set up according to ACS, which read-only commands are safe to try on each ACS reader we cover, what you should never send, what ACS says about privacy and security, and how it compares with the ACS Script Tool, QuickView and BSD's own reader utilities. The Web APDU Tool is ACS software; BSD Infotech is an independent ACS supplier and integrator and does not host or redistribute it.
Not yet tested by BSD. Everything on this page about the tool comes from ACS's own Web APDU Tool page, the extension's Chrome Web Store listing and the ACS reader manuals, checked on 17 Nov 2026. BSD has not yet run the Web APDU Tool with its own readers, so screen names and error messages are described in general terms. This page will be updated with screenshots after that test.
What the Web APDU Tool Is and When It Is Handy
An APDU (application protocol data unit) is one command sent to a smart card or to the reader, plus the card's or reader's reply. Most reader tests come down to a handful of APDUs: ask for the card's UID, ask the reader for its firmware version, read one block of a test card. ACS describes the Web APDU Tool as a browser-based utility for sending and checking such commands with its readers, with safeguards built into the browser extension, so you can test without a complicated setup.
Unlike the ACS utility tools, it is not a program you unpack and run. It is a web page on ACS's own site that you open in the browser. What you do install is the bridge that lets the page talk to the reader:
| Part | Where it runs | What it does |
|---|---|---|
| Web APDU Tool | A page on acs.com.hk, opened in Chrome or Edge | Where you pick the reader, type a command and read the reply |
| ACS APDU Bridge extension | Inside Chrome or Edge (installed from the Chrome Web Store) | Carries commands between the web page and the program on your computer. ACS says its safeguards sit here. |
| ACS APDU Bridge Host | A program installed on the computer (Windows, macOS or Linux version) | Talks to the reader through the operating system's smart card layer (PC/SC on Windows) |
| Reader driver and Smart Card service | Windows | The same layer every card program uses. If QuickView cannot see the reader, the Web APDU Tool will not either. |
When it is the right tool
- A quick command test without installing the Script Tool. For one or two commands (Get UID, firmware version) the browser tool is enough, and the ACS bridge downloads are offered directly on the tool page.
- A mixed office. The same steps work on Windows 10 or later, macOS and Linux, because ACS publishes the bridge for all three.
- Checking whether a web application could use the reader. ACS also offers a development kit for web-based smart card and NFC applications on request. If the tool can talk to your reader and card, a browser-based design is worth discussing.
It is the wrong tool for long command scripts you want to save and rerun, for changing reader settings, and for anyone who should not be typing raw commands at all. The comparison table below shows what to use instead.
What the PC Needs, and Which Readers ACS Supports
As listed on the ACS Web APDU Tool page on 17 Nov 2026:
| Requirement | What ACS lists |
|---|---|
| Windows | Windows 10 or later |
| macOS | 10.13 or later on Intel Macs, 11 or later on Apple Silicon |
| Linux | 64-bit, GLIBC 2.17 or later (Intel/AMD or ARM). ACS names Ubuntu 14.04+, Debian 8+, Fedora 30+ and CentOS/RHEL 7+. |
| Browser | Google Chrome or Microsoft Edge, latest version recommended. Edge works because it can install Chrome extensions. |
| Browser extension | ACS APDU Bridge, from the Chrome Web Store (linked from the ACS page) |
| Program on the PC | ACS APDU Bridge Host, one download per operating system. When we checked, the Windows link gave a ZIP file whose name says it contains a signed MSI installer. |
| Readers | "All ACS USB smart card readers". ACS recommends the ACR40T, ACR40U, ACR1552U and ACR1581U. |
| Registration | None seen. On 17 Nov 2026 the bridge downloads and the tool link on the ACS page were direct links, unlike the ACS utility tools (QuickView, Script Tool), which ask for a short registration first. |
Drivers. ACS does not list a separate driver for the tool. The bridge reaches the reader through the normal smart card layer, so the reader has to work there first: on Windows, it should appear under Smart card readers in Device Manager and the Smart Card service must be running. Our ACS driver installation guide for Windows 10 and 11 covers both, and links to the official ACS driver pages.
The four readers on this site. The ACR1252U, ACR1552U, ACR122U and ACR39U are all ACS USB readers, so they fall under ACS's "all USB readers" statement. Only the ACR1552U is on ACS's recommended list. BSD has not yet tested any of the four with the tool.
Set Up the Web APDU Tool, Step by Step
ACS gives three steps: add the extension, install the host program for your platform, open the tool. The steps below add the checks around them that save time later. Do them on a PC where you are allowed to install software and browser extensions.
- Make sure the reader works first. Plug in the reader, then check Device Manager (how to check that Windows detects the reader). If you already have ACS QuickView, confirm that it lists the reader and shows a card. Expected result: the reader appears under Smart card readers, with no warning sign.
- Open the official ACS page. Go to the ACS Web APDU Tool page on acs.com.hk. Start from this page rather than a search result, so the extension and downloads you get are the ones ACS links to.
- Add the ACS APDU Bridge extension. Follow the extension link in ACS's step 1. It opens the Chrome Web Store; in Edge you may first need to allow extensions from other stores. Before you click Add, check that the listing is named ACS APDU Bridge and that its developer contact is an acs.com.hk address. Expected result: the extension appears in the browser's extensions list.
- Download and install the ACS APDU Bridge Host. In ACS's step 2, pick Windows, macOS or Linux. On Windows, unpack the ZIP and run the installer inside it. Windows may ask for administrator permission. Expected result: the program installs without errors. ACS does not say whether it then runs in the background or must be started by hand; we will add this after our test.
- Restart the browser. Close every Chrome or Edge window and open it again, so the extension can find the newly installed host program. This is our own precaution, not an ACS step.
- Open the tool. Use the "access the tool" link in ACS's step 3. It opens a page on acs.com.hk. ACS's demo video, linked from the same page, shows a walkthrough.
- Select your reader and connect. Pick the reader from the tool's list. For a dual-interface or contactless reader, choose the contactless (PICC) entry for NFC cards, or the contact entry for a chip card. Place the card before connecting. Expected result: the tool connects without an error.
Send GET DATA FF CA 00 00 00 and Read the Reply
FF CA 00 00 00 is the first command to try on any contactless ACS reader. It is the PC/SC Get Data command, documented in the ACS manuals for the ACR122U, ACR1252U and ACR1552U. The reader answers it itself, from what it learned when the card arrived, so it needs no key and changes nothing on the card.
- Place one card on the reader and connect. One card only: two cards in the field confuse most readers.
- Type the command
FF CA 00 00 00in the tool's command field (spaces are usually optional in APDU tools; if the tool rejects them, typeFFCA000000). - Send it and read the reply. A typical reply from a MIFARE Classic 1K card looks like
A1 B2 C3 D4 90 00. A 7-byte card such as NTAG or DESFire gives seven bytes before90 00. - Split the reply. The last two bytes are the status word (SW1 SW2). Everything before them is the UID.
| Reply ends with | Meaning | What to do |
|---|---|---|
90 00 | Success. The bytes before it are the UID. | Note the UID and its length (4, 7 or another length). |
63 00 | The operation failed (ACR122U API manual) | The card probably moved. Hold it flat and still, reconnect and send again. |
6A 81 | Function not supported | Wrong interface or a card with no UID, such as a contact card in the contact slot. Select the contactless (PICC) reader. |
Another 6X XX code | The command failed (the ACR1552U manual treats any 6X XX as a failure) | Check the command bytes; see the full table below. |
Our UID reading guide explains each byte of the command, how byte order and decimal conversion change how a UID looks, and the full list of status words for Get Data. It applies to the Web APDU Tool exactly as to the Script Tool.
Safe Read-Only Commands for Each Reader
These commands only read. Each one is listed only for the readers whose ACS manual documents it. Commands for the reader itself (starting FF 00, FF 09 or E0) are reader-specific: do not assume one model's command works on another.
| What you want | Command | Documented for | Expected reply |
|---|---|---|---|
| Card UID | FF CA 00 00 00 | ACR122U, ACR1252U, ACR1552U (contactless) | UID + 90 00 |
| ATS of an ISO 14443-4 Type A card (for example DESFire) | FF CA 01 00 00 | ACR122U, ACR1552U | ATS + 90 00; an error on cards without ATS, such as MIFARE Classic |
| Firmware version | FF 00 48 00 00 | ACR122U; the ACR1252U manual lists it among its ACR122U-compatible commands | ASCII text such as "ACR122U201". The ACR122U manual shows no status word after it. |
| Firmware version | FF 09 00 00 11 | ACR39U (ACR39x reference manual), after connecting to an inserted card | 11 bytes of firmware version text |
| Firmware version | E0 00 00 18 00 | ACR1552U, ACR1252U, but as an escape command (SCardControl), not a normal APDU | ACS does not say whether the Web APDU Tool can send escape commands. Use QuickView or the SDK instead. |
| ATR and card status | None: the ATR is returned when the reader connects to the card, not by an APDU | All readers | ACS does not say whether the tool shows the ATR. QuickView shows it and our guide explains it. |
Not yet tested by BSD: which of these commands each reader answers through the Web APDU Tool. The ACR39U has no contactless interface, so FF CA does not apply to it. Reading data blocks of a MIFARE Classic test card with the factory key (FF 82, FF 86, FF B0) is also read-only; it is covered in our MIFARE card test guide.
What Not to Send from a Browser
An APDU tool sends exactly what you type. The card does not know the command came from a test, and some mistakes cannot be undone. Keep to the commands above unless you are working on a labelled spare card, and never send these to a card you need:
- Writes to a MIFARE Classic sector trailer. The last block of each sector (blocks 03, 07, 0B and so on on a 1K card) holds the keys and access bits. An Update Binary (
FF D6) to a trailer with a wrong key or wrong access bits can lock that sector for good. - Key changes of any kind. Do not change MIFARE keys, DESFire keys or DESFire settings, and do not format a DESFire card. Key management belongs in your application, with the keys stored safely, not in a browser text box.
- Writes to block 0 or to NTAG/Ultralight pages 0 to 3. They hold the serial number, lock bytes and one-time-programmable bits.
- Reader configuration commands. Escape commands that change polling, keyboard emulation or other reader settings belong in ACS's configuration tools, where the setting is explained.
- Real keys of live cards. Use factory keys and your own test cards. A web page is the wrong place to type the keys that protect a card system in use.
The five safety rules and a test-card log are on our MIFARE test guide. If you need writes, value blocks or DESFire work, use the Script Tool on a spare card or let your application do it.
Browser, Privacy and Security Notes
What ACS and the extension listing say
- ACS calls the tool secure and says the browser extension provides built-in safeguards for a controlled test environment. The ACS page does not explain what those safeguards are.
- The Chrome Web Store listing of ACS APDU Bridge (version 1.2, updated 28 May 2026 when we checked) describes it as a bridge between web applications and ACS readers, for ACS USB readers only. Its privacy section states that the developer will not collect or use your data, and links to the ACS privacy policy. That policy covers the ACS website in general and does not mention the tool.
- ACS does not publish which websites the extension accepts commands from. BSD has not checked this.
Practical precautions (BSD's advice, not ACS's)
- Install only from the links on the ACS page. Lookalike extensions exist for many tools. Check the extension's name and developer contact before adding it.
- Remember what you installed. The extension and the host program together let a web page reach your card reader. On a shared or company PC, remove both when the test is finished, through the browser's extensions page and Windows Installed apps.
- Check your company's policy. Managed Chrome or Edge installations often block extensions that are not on an approved list, and installing the host program may need administrator rights. Ask IT first, or use the Script Tool on a test PC.
- Treat card data as data. UIDs are not secret on their own, but in an access control or payment system they identify people. Do not paste live UIDs or keys into screenshots, tickets or chat without need.
- Close other card programs. Only one program can hold a card with exclusive access. Close QuickView, the Script Tool, BSD utilities and your own program before testing in the browser.
Web APDU Tool Problems and How to Fix Them
| What you see | Likely cause | What to do |
|---|---|---|
| The tool says the extension is missing, or does nothing at all | Extension not installed or turned off, or an unsupported browser (Firefox, Safari) | Use Chrome or Edge, check that ACS APDU Bridge is installed and switched on, then reload the tool page. |
| Extension installed, but the tool cannot reach the PC | APDU Bridge Host not installed, installed for the wrong platform, or the browser was open during installation | Install the host program for your operating system from the ACS page, close every browser window and open the tool again. |
| No reader in the tool's list | Driver missing, reader not detected, Smart Card service stopped, or a Remote Desktop session | Check Device Manager, the Smart Card service, and Remote Desktop and smart card readers. Then confirm the reader in QuickView. |
| Reader listed, but connecting fails or the card is "not present" | No card on the reader, wrong interface (SAM or contact instead of PICC), or another program holds the card | Place the card first, choose the PICC entry, close other card software and connect again. The reader states guide explains in-use and exclusive states. |
| An ACR1552U types numbers into Notepad, and the tool sees no card | The reader is in keyboard emulation mode | Switch it back to its normal mode with the ACS configuration tool (see the ACR1552U guide). |
FF CA 00 00 00 returns 6A 81 | Function not supported for this card or interface | Select the contactless reader. Contact cards have no UID to return. |
| Firmware command returns an error | That command is not documented for this reader, or it is an escape command | Use the command listed for your model in the safe commands table, or read the version in QuickView. |
| Blocked by company IT | Extension or installer not allowed by policy | Ask IT, or use the ACS Script Tool or a BSD utility instead. |
Web APDU Tool vs Script Tool, QuickView and BSD Utilities
Each tool answers a different question. The test tool chooser on our testing centre sets them side by side for every test; this table compares them from the point of view of sending commands.
| ACS Web APDU Tool | ACS Script Tool | ACS QuickView | BSD reader utilities | |
|---|---|---|---|---|
| Main job | Send single APDUs from a browser | Send APDUs and saved scripts | See readers, card arrival and the ATR | Read the UID with buttons (free); read and write cards on factory keys with a BSD licence key |
| Install | Browser extension + bridge program | Desktop program | Desktop program | Desktop program (Windows) |
| Getting it | Direct from the ACS page | ACS registration form | ACS registration form | One-time email check (OTP) |
| Platforms | Windows 10+, macOS, Linux; Chrome or Edge | Windows (separate macOS and Linux versions listed by ACS) | Windows, macOS, Linux | Windows 10 and 11 |
| Free-typed commands | Yes | Yes | No | No (fixed functions only) |
| Best for | A quick command check on any OS | Repeatable tests and developer work | "Does the reader see the card?" | Non-developers; cards on factory keys |
| Guide | This page | ACS Script Tool guide | ACS QuickView guide | BSD utilities |
When the command test works and you are ready to write code, the same commands go into SCardTransmit. Our SDK guides show this in C# for the ACR1252U, ACR1552U and ACR122U, and the smart card SDK and developer hub lists the rest.
Sources
The tool description, setup steps, system requirements and supported readers were checked on the official ACS page on 17 Nov 2026; the extension details on its Chrome Web Store listing the same day. Commands and status words come from the ACS reader manuals, summarised in our own words. Requirements change, so check the ACS page before you install.
- ACS Web APDU Tool (steps, downloads, system requirements, supported and recommended readers, demo video)
- ACS APDU Bridge in the Chrome Web Store (version, platforms, privacy declarations)
- ACS Utility Tools (Script Tool and QuickView, for comparison)
- ACR122U NFC Reader API v1.4 (Get Data, response codes, firmware version), ACR1552U Series Reference Manual v1.05 (Get Data, escape command E0 00 00 18), ACR39x Reference Manual v1.03 (GET_READER_INFORMATION) and ACR1252U API v1.17 (ACR122U-compatible commands): ACS manuals supplied with the ACS SDK kits and on the ACS driver pages
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. Chrome is a trademark of Google LLC; Windows and Edge are trademarks of Microsoft Corporation.
