> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/compliance/pci-pts-poi-v6.2-security-policy.md). # PCI PTS POI v6.2 Security Policy

Document Number: D998200520-104 REGISTERED TO ISO 9001:2015 Copyright © 2006 - 2025 MagTek, Inc. MagTek® is a registered trademark of MagTek, Inc. MagnePrint® is a registered trademark of MagTek, Inc. MagneSafe® is a registered trademark of MagTek, Inc. Magensa™ is a trademark of MagTek, Inc. AAMVA™ is a trademark of AAMVA. American Express® and EXPRESSPAY FROM AMERICAN EXPRESS® are registered trademarks of American Express Marketing & Development Corp. Apple Pay® is a registered trademark to Apple Inc. D-PAYMENT APPLICATION SPECIFICATION® is a registered trademark to Discover Financial Services CORPORATION MasterCard® is a registered trademark and PayPass™ and Tap & Go™ are trademarks of MasterCard International Incorporated. Visa® and Visa payWave® are registered trademarks of Visa International Service Association. ANSI®, the ANSI logo, and numerous other identifiers containing "ANSI" are registered trademarks, service marks, and accreditation marks of the American National Standards Institute (ANSI). ISO® is a registered trademark of the International Organization for Standardization. PCI Security Standards Council® is a registered trademark of the PCI Security Standards Council, LLC. EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo, LLC. The Contactless Indicator mark, consisting of four graduating arcs, is a trademark owned by and used with permission of EMVCo, LLC. UL™ and the UL logo are trademarks of UL LLC. All other system names and product names are the property of their respective owners. ## Table - Revisions


Rev Number	Date	Notes
10	Feb 10, 2022	Initial Release
12	Nov 02, 2022	Update for PCI-6.1 Add image to Periodic Inspection. Add WLAN related content for firmware identification, available interfaces, CAPK’s, and guidance. Update pictures and images to latest version. Change PCI HW ID structure.
13	Dec 16, 2022	Remove no display option. Add additional cryptographic algorithms. Update screenshots for latest firmware
14	Feb 16, 2023	Update PCI version to 6.2. Add extra info about HW ID. Add pictures of card slot and images of kiosk mounting. Update section 3.2 Installation. Update section 4.1 Periodic Inspection. Add image of product installed into Kiosk environment; 4.2. Update image to show direct image of ICCR card slot
15	Mar 22, 2023	HW ID revision change (position 11). 2.3.1Hardware Identification, update images to show correct HW ID and Firmware Identification and \ change PCI ID Tag revision (position 11) to ‘B’.
16	Apr 26, 2023	Add AES-256 to data protection algorithms Section 5.1
17	June 6, 2023	Add a picture showing the bottom view of device with both BCR and Kiosk options. Remove some wording in the preface. Add detail on retrieving the firmware versions. Change some language describing the DynaFlex II PED device and the hardware configurations.
18	October 3, 2023	Update Main FW in Firmware Identification, Update Device Information Screenshots in Device Information Page, Update PCI Hardware Label Images in Hardware Identification, Self-Test updated with revised 23/24 hour reset guidance.
19	October 18, 2023	Update WLAN FW in 2.3.2 Firmware Identification, added FW major revision description note to 2.3.2 Firmware Identification, Update Device Information Screenshots in 2.3.3 Device Information Page.
1A	October 26, 2023	Add previous descriptions of 17 position Main FW version and 17 position WLAN FW to 2.3.2 Firmware Identification
1B	November 2, 2023	Update Tables Table 2-4 - Main Firmware Version and Associated Variables Table 2-7 - WLAN Firmware and Associated Variables with updated version descriptions, changed from A to AA.


Rev Number	Date	Notes
100	June 19, 2024	Update device images in Title page, in Figure 2-1 and Figure 4-2; Update Table 2-1 - PCI Hardware Identifier, Table 2-2 – Hardware Versions with Description of Associated Variables with current HW ID numbers; Update Table 2-4 - Main Firmware Version and Associated Variables , Table 2-5 – Boot Firmware Version and Associated Variables with current FW versions; Change revision number to correct 3 digit numeric revision convention, from 1B to 100, Update Figure 2-2 - Bottom views of DynaFlex II PED, DynaFlex II PED (Kiosk), DynaFlex II PED (BCR), and DynaFlex II PED (BCR & Kiosk) and Figure 2-3 - DynaFlex II PED Device Label Location with updated labels.
101	October 28, 2024	Added new ID for Main FW with newer EMV Kernels to 2.3.2 Firmware Identification
104	May 15, 2025	Added new ID for Main FW and Updated HW IDs to 2.3.2 Firmware Identification and 2.3.1 Hardware Identification. Update device information screenshots in 2.3.3 Device Information Page; Add MQTT to 3.4 Communications and Security Protocols.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/compliance/pci-pts-poi-v6.2-security-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.