> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-6.2.md).

# PA-DSS requirement 6.2

Secure transmissions of cardholder data over wireless networks

Since Maitre’D version 7.08.000, cardholder data is encrypted with strong encryption before being sent from the POS to the main Back-Office for processing. This encryption is enabled by default and cannot be disabled. There are no settings or options in the Maitre’D software that would allow for this encryption process to be disabled, either accidentally or on purpose.

If your wireless network is protected by WPA2 as it should, this means that there are now two layers of encryption protecting the cardholder data. First, a potential attacker would need to breach your wireless network, which should be very hard to achieve if it is properly protected. In the unlikely event that an attacker succeeds in breaching your wireless network, the cardholder data would still be protected by strong AES-128 encryption.

As a reminder, in order to use wireless communications in a secure manner, make sure to:

* Securely implement wireless technology as outlined in PA-DSS requirement 6.1 above.
* Use and manage wireless technology in a secure manner as outlined in PA-DSS requirement 6.3 below.


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-6.2.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.