> 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/command-centre-supported-printers.md).

# Supported printers

#### How do you know if a printer works with Command Centre?

The Printer Integrations matrix is the authoritative resource for any site that wants to use a printer with Command Centre to print and/or encode cards. It details the make, model, and other specifications of each printer, and the Command Centre versions each is tested and supported against.

📄 [**Printer Integrations matrix (PDF)**](https://media.gallagher.com/m/e8cc9202ec88ed0/original/Printer-Integrations.pdf). This matrix is updated periodically; for the current version check the live source: [media.gallagher.com](https://media.gallagher.com/m/e8cc9202ec88ed0/original/Printer-Integrations.pdf)

#### What to check before buying a printer?

* **Check the list, then check the spec.** Confirm the printer is listed **and** that the specifications on the right-hand side of the matrix match exactly the printer you are buying. Even minor build variances can cause incompatibility.
* **Newer firmware/drivers is not the same as unsupported.** If the printer is listed but its firmware or drivers are newer than the matrix shows, it does not necessarily mean the printer will not work, only that that version has not been tested as working by Gallagher.
* **When unsure, ask.** Contact Gallagher Technical Support with any questions before purchasing.

Gallagher also provides Printing and Encoding services for sites. Enquire with the Security Sales team for more information.

***

#### Which printers are nearing or past end of support?

Some printers are no longer supported or are nearing end of support. Check this table before specifying an older model. This table reflects the source as of the 2026-07-01 ingestion; re-verify against the live advisory for models added since.

| Manufacturer | Model                     | Variant  | EOS Date   |
| ------------ | ------------------------- | -------- | ---------- |
| Fargo        | DTC550                    | USB      | 01/01/2025 |
| Zebra        | P110iM                    | USB      | 01/01/2025 |
| Zebra        | P310iM                    | USB      | 01/01/2025 |
| Zebra        | P330iM                    | USB      | 01/01/2025 |
| Zebra        | P330i                     | USB      | 01/01/2025 |
| MagiCard     | RioPRO                    | USB      | 01/01/2025 |
| MagiCard     | RioPRO V2                 | USB      | 01/05/2026 |
| Nisca        | C101                      | USB      | 01/01/2025 |
| Nisca        | PR5350                    | USB      | 01/01/2025 |
| EDIsecure    | XiD440                    | USB      | 01/01/2025 |
| EDIsecure    | XiD580                    | USB      | 01/01/2025 |
| Entrust      | CD800                     | USB      | 30/04/2025 |
| Entrust      | SD360 & SD460 Single-Wire | Ethernet | 30/04/2025 |
| Entrust      | SD460 Single-Wire         | Ethernet | 30/04/2025 |
| Entrust      | SD260L Single-wire        | Ethernet | 30/04/2025 |
| Entrust      | SD360                     | USB      | 30/04/2025 |
| Entrust      | SD360 Single-wire         | Ethernet | 30/04/2025 |
| Entrust      | Duplex CD800 Single-Wire  | Ethernet | 30/04/2025 |

***

🔗 **Related**

* [Command Centre - Licencing](/knowledge-hub/products/cc-software/reference/command-centre-licencing.md). Card printing and encoding are licensable features.


---

# 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/command-centre-supported-printers.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.
