> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-1-hardware-and-software-requirements/optional-hardware-components.md).

# Optional Hardware Components

### Optional hardware components and manufacturers

Below is a list of optional hardware components and manufacturers supported by Maitre'D.

***

### Magnetic Card Reader

* USB
* Keyboard wedge
* RS-232 (serial)
* OPOS

***

### Customer Display

* AEDEX
* Epson ESC/POS compatible
* Mintronix
* Tekvision
* OPOS

***

### Scale

* Toledo 8213, 8217
* Weigh-Tronix 6710

***

### Cash Drawer

* RS-232 (serial) with or without status
* Through a parallel or serial printer
* OPOS

***

### Kitchen Monitor

* KDS Kitchen Display System from PayFacto
* QSR ePIC (QSR Automation)

***

### Barcode Scanner

* USB
* Keyboard wedge
* RS-232 (serial)

***

### Fingerprint Recognition (biometric devices)

* Digital Persona U.are.U 2000, 2000b and 2400b

***

### Cash Card Reader

* ITC System 1015 or 2015

***

### Fiscal Printer

* Epson TMu200AF for Venezuela
* Québec Sales Recording Module (SRM) – Module d’Enregistrement des Ventes (MEV)
* Belgium Black Box

***

### Surveillance Camera

* Kodicom I3DVR
* Generic XML interface

***

### Bar Dispenser

* Azbar
* Berg
* Auper
* Scanabar

***

### Remote Display

* Texas Digital Accuview
* Delphi Display Systems

***

### EMV Credit/Debit Payment Devices

* See the documentation specific to your processor of choice for detailed lists of supported EMV Credit/Debit Payment Devices.


---

# 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://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-1-hardware-and-software-requirements/optional-hardware-components.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.