> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-outside-emv/revision-history.md).

# Revision History

| Date       | Description                                                                                                                    |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------ |
| 03/22/2019 | Initial Documentation Release.                                                                                                 |
| 03/29/2019 | Updated the Acumera phone number.                                                                                              |
| 06/05/2019 | Updated Appendix B with Wayne/Dover phone number.                                                                              |
| 07/16/2019 | Updated Hardware and Software sections. Updated Gilbarco, Secure PumpPAY, Wayne, and Troubleshooting chapters.                 |
| 08/06/2019 | Added references to Appendix A in the Overview section and added Shell notes to the Gilbarco and Wayne sections.               |
| 08/13/2019 | Updated Appendix B > MNSP Availability sections.                                                                               |
| 11/06/2019 | Updated the Gilbarco and Wayne EMV Configuration tabs.                                                                         |
| 11/12/2019 | Updated Gilbarco and Wayne Dispenser Requirements section.                                                                     |
| 02/03/2020 | Updated contact address, changed notes about Wayne DCR IP addresses.                                                           |
| 04/08/2020 | Added note to the introduction regarding upgrading PIN pad software to be used with the new EMV Kernel.                        |
| 04/14/2020 | Added a note to the Local Area Network Configuration section in the Wayne Chapter.                                             |
| 05/07/2020 | Added a STOP note to the Supported Software section regarding Quick Chip.                                                      |
| 05/14/2020 | Added a Shell note to the STOP note in the Supported Software section regarding Quick Chip.                                    |
| 05/15/2020 | Updated AvaLAN MNSP support information.                                                                                       |
| 10/20/2020 | Added informational note about NFC Readers for Gilbarco and Wayne dispensers, and added "RFID" entry to the Glossary of Terms. |
| 01/18/2021 | Updated the Isolated NIC Payment sections in the Gilbarco and Wayne chapters and added Appendix D.                             |
| 01/27/2022 | Removed SPP. Added Contactless settings. Added Invenco and Bennett.                                                            |
| 02/16/2022 | Updated the diagram chapter and system requirements section.                                                                   |


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-outside-emv/revision-history.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.
