> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/export-card-serial-numbers.md).

# Export card serial numbers

Export the card serial numbers of cardholders' cards from a Command Centre report.

Export the Card Serial Numbers (CSN) of cardholders' cards with a Cardholder report in Command Centre Client. If some cards show no CSN, see [CSN not listed against some or all cardholders](#csn-not-listed-against-some-or-all-cardholders).

### Create the export

1. In Command Centre Client, select **Report Configuration** (the big cog in the top right corner) and create a new **Cardholder** report.
2. Add a filter called **Cardholder is**, then select either **Specific Cardholder** or **Any Cardholder**. Extra filters can be added after this; they are not covered here.
3. In the right pane, select **Configure Layout**.
4. Add the layout of the report, and make sure the **CSN** option is ticked. You can choose **Hexadecimal**, **Hexadecimal Reverse Bytes**, **Decimal** and **Decimal Reverse Bytes**; one or more can be output in the report.

   ![Configure Layout column list with Card Number and Card Serial Number (CSN), MIFARE Card Serial Number, ticked; Display options Hexadecimal, Hexadecimal Reverse bytes, Decimal (ticked) and Decimal Reverse bytes](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5038f11450924e6159dd9891a9a724659d0a6dfb%2FSECHUB-TS-CSN-EXPORT-01-configure-layout.jpg?alt=media)
5. After selecting the format, the preview shows in the right pane. If it is not as you want it, change the layout, add more output options, or add filters.

   ![Report preview with the columns Card Number, Cardholder Name, CSN Decimal and Card Type for seven test cards (MIFARE Classic, DESFire and MIFARE 4k); the CSN values are covered](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c572c7c203c5cd56da48e099cfc6c65227fd8168%2FSECHUB-TS-CSN-EXPORT-02-report-preview.jpg?alt=media)
6. To run the report and save it as a file, follow **Finding a Report** in the Command Centre Client help.

### CSN not listed against some or all cardholders

If the cards have not been encoded on site, the CSN for those cards may not be in the system to export. Whether Command Centre has it depends on the version:

| Version                   | How the CSN reaches the database                                                                                                                |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| From version 7.20 onwards | When a card is encoded, the CSN is captured against the card in the database.                                                                   |
| From Version 8.60 onwards | T series readers connected via HBUS should capture the CSN from the card as it is presented for access, and add it to the card in the database. |
| Prior to version 8.60     | Only by one of the two USB encoder options below.                                                                                               |

MIFARE DESFire CSN capturing was introduced in 8.60.

The two options before version 8.60:

1. Connect a USB encoder to a workstation, open **Configuration Client** and select **Monitor/Read MIFARE Card**. Present the card to the USB reader; the CSN is added to the database.
2. Connect a USB encoder to a workstation, open **Command Centre Client** and select **Viewers**, then a **Cardholder Viewer**, then **Search using Card**. Present the card to the USB reader; the CSN is added to the database.

   ![Cardholder Viewer with Place Card on Encoder shown and Search using Card selected](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-a92dea63be78183e018b21b9677e9bdae0b11072%2FSECHUB-TS-CSN-EXPORT-03-search-using-card.jpg?alt=media)

### Import CSNs into the database

The only way a CSN list can be imported into Command Centre is through the REST API, from version 8.00 and above. See [Representational state transfer (REST) API](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api.md).

### Fobs encoded by Bureau encoding

Fobs are encoded on the Bureau encoding system. This does not capture the CSN of the cards, so it cannot be supplied. See [Bureau encoding reference information](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/bureau-encoding/bureau-encoding-reference-information.md).

To read a card's CSN as its card number at a reader, see [Use a card CSN as the card number](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-using-card-csn-as-the-card.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/export-card-serial-numbers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
