> 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/configuration-client/site-installation/universal-card-format.md).

# Universal Card Format

### Introduction

The Universal Card Format item allows users to define their own card formats and transfer them to Controller(s). This is in addition to the manufacturer's Gallagher card formats and certain Wiegand formats that have been pre-defined in Command Centre.

The Universal Card Format item can be defined as Wiegand or ABA (American Banking Association) compatible. It can be used with either Gallagher 125 readers or Wiegand compatible readers connected to Universal Reader Interfaces or Reader I/O Interfaces.

Operators define Universal Card Formats by specifying significant parameters, (i.e. bit position, card number length, [facility code](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#facility-code), issue level and parity check bits for Wiegand formats, or digit positions and lengths for ABA formats). The Universal Card Format is passed to the Controller as properties of a Reader Part in the Controller, which uses the format when interpreting card data.

**Note:** The process of defining and configuring Universal Card Formats requires a technical knowledge of ID Card systems, and will normally be configured by your dealer. It is recommended that you contact your dealer prior to modifying or creating Universal Card Formats.

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Adding a new Universal Card Format](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/universal-card-format/adding-a-new-universal-card-format.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Deleting a Universal Card Format](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/universal-card-format/deleting-a-universal-card-format.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Universal Card Formats for 'Use MIFARE Serial Number as Card Data' (CSN mode)](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/universal-card-format/universal-card-formats-for-use-mifare-serial-number-as-card-data-csn-mode.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/configuration-client/site-installation/universal-card-format.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.
