> 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-go/documentation/user-manuals/installation-and-operation-manual/introduction.md). # Introduction DynaFlex II Go and DynaFlex II Go with Barcode Reader (BCR) deliver the next generation of mobile payment solutions. Both models offer an integrated secure card reader authenticator for magnetic stripe cards, EMV chip cards (contact and contactless), and NFC enabled mobile wallets including Samsung Pay, Google Pay™ with support for Google VAS, and Apple Pay® with support for Apple VAS. Ideal for cafés, restaurants, boutiques, airlines, retail banks and other developers looking to build a secure payment solution that accepts contactless EMV and NFC payments. DynaFlex II Go is suited for deployment in many scenarios, including mobile handsets, tablets, and desktop computers. DynaFlex II Go and DynaFlex II Go BCR are equipped with MagneSafe® Security Architecture (MSA). The design and architecture meet the requirements for contactless EMV 3.1, PCI PTS POI v6.2, and support triple DEA encryption with DUKPT Key Management. #### Key Features and Components DynaFlex II Go and DynaFlex II Go BCR are easy to install and configure, with key features that include: * Contactless EMV 3.1 Approved. * Contact EMV 4.4a Approved. * PCI PTS POI v6.2 Approved. * Optical reading for many 2D and 1D barcodes including PayPal and Venmo (DynaFlex II Go BCR Model Only). * Transducer for audio alerts. * User configurable audio commands to play a sequence of tones. * Bluetooth® Low Energy (LE). * USB-C interface. * iAP2® Protocol Support. * Triple DEA encryption / DUKPT key management. * AES-128 and AES-256 encryption. * Ingress protection - IP 30. * Apple Pay® / Apple Wallet® (Apple VAS protocol support). * Google Wallet Smart Tap. (Google VAS protocol support). * Google Pay™. * NFC Compatibility: Smart cards and contactless IC products, including MIFARE Classic / MIFARE DESFire /MIFARE Plus cards, with the ability to send pass-through commands. * Optional OtterBox® uniVERSE® case. * Optional countertop stand. Figure 1-1 illustrates the major components of DynaFlex II Go (BCR model shown). Models without a barcode reader are identical to the illustration, but do not have a camera and do not have a QR code printed on the front face.

Figure - DynaFlex II Go Major Components

## Available Models and Accessories ## **Table - Available Models and Options**


Part No.	Description	Display	Connection(s)	Operating Systems
21078400	DynaFlex II Go, PCI, BCR, BLACK, BLUETOOTH LE	None	USB-C, Bluetooth® (LE), iAP2®	MS Windows, Mac OS, Linux; Android Phone
21078401	DynaFlex II Go, PCI, BLACK, BLUETOOTH LE	None	USB-C, Bluetooth® (LE), iAP2®	MS Windows, Mac OS, Linux; Android Phone
21078402	DynaFlex II Go, PCI, BCR, BLACK	None	USB-C, iAP2®	MS Windows, Mac OS, Linux; Android Phone
21078403	DynaFlex II Go, PCI, BLACK	None	USB-C, iAP2®	MS Windows, Mac OS, Linux; Android Phone
21078404	DynaFlex II Go, PCI, BCR, BLACK, BLUETOOTH LE, LOCKED MAGENSA BUNDLE LMB	None	USB-C, Bluetooth® (LE), iAP2®	MS Windows, Mac OS, Linux; Android Phone
21078405	DynaFlex II Go, PCI, BLACK, BLUETOOTH LE, LOCKED MAGENSA BUNDLE LMB	None	USB-C, Bluetooth® (LE), iAP2®	MS Windows, Mac OS, Linux; Android Phone
21078406	DynaFlex II Go, PCI, BCR, BLACK, LOCKED MAGENSA BUNDLE LMB	None	USB-C, iAP2®	MS Windows, Mac OS, Linux; Android Phone
21078407	DynaFlex II Go, PCI, BLACK, LOCKED MAGENSA BUNDLE LMB	None	USB-C, iAP2®	MS Windows, Mac OS, Linux; Android Phone

## Table - DynaFlex II Go Accessories


Part #	Description	Accessory Notes
1000005076	CABLE, USB-C TO USB TYPE A MALE USB 2.0, 20AWG	Optional, specify in order
1000006016	USB CABLE TYPE A – C, 6FT	Optional, specify in order
1000006017	USB CABLE TYPE C, 6FT	Optional, specify in order
21078408	DYNAFLEX II GO, KIT COUNTERTOP STAND	Refer to Appendix C Optional Accessories for additional information.
21078409	DYNAFLEX II GO ADAPTOR FOR OTTERBOX	Refer to Appendix C Optional Accessories for additional information.
21078410	DYNAFLEX II GO RUBBER SLEEVE	Refer to Appendix C Optional Accessories for additional information.
21078411	DYNAFLEX II GO RUBBER SLEEVE HALF SIZE	Refer to Appendix C Optional Accessories for additional information.
Note: At least one cable will be shipped with the device, specify when ordering.

## About Terminology In this document, DynaFlex II Go products are referred to as the device. They are designed to be connected to a host, which is a piece of general-purpose electronic equipment that can send commands and data to, and receive data from, the device. Host types include PC and Mac computers/laptops, tablets, and smartphones. Generally, the host must have software installed that communicates with the device and is capable of processing transactions. During a transaction, the host and its software interact with the operator, such as a customer service representative, while the device interacts with the cardholder (even if the cardholder is using a virtual representation of the card account, such as a smartphone). --- # 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-go/documentation/user-manuals/installation-and-operation-manual/introduction.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.