> 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/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/operation.md). # Operation ## About Operating Modes During operation, DynaProx devices transition between distinct operating modes, which are important for operators to understand so they can properly control the device: * Powered Off Mode is the shipping and storage mode of the device. No external power is applied to the device through the USB cable or RS-232 cable. In this mode, the device consumes practically no power. To set the device from Powered Off mode to Active mode, connect the device to USB power or RS-232 power. * Active Mode is the device’s normal “awake” state when it is in use. In this mode, LEDs are powered on, and the device is ready to receive commands from the host. To set the device from Active mode to Powered Off mode remove power. ## Operation Overview During normal operation, the operator initiates a transaction from the host, and the cardholder interacts with the device. Transaction types may include new accounts, teller window applications, checking, savings, mortgages, retail transactions, or any other type of transaction where there is interaction between the cardholder and the operator. For each transaction type, the host software directs the cardholder, and the transaction flow on the device may differ depending on what the host software specifies and what the cardholder does. [**About Maintenance Reset**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/maintenance) For full host control, the device should not be allowed to run for > = 23 hours without a reset. To accomplish this, have the host application send a reset command twice a day separated by at least one hour. **Example:** Host software resets the device at 1 AM and 3AM. This keeps the device from initiating its own reset. Card Reading provides examples of the cardholder experience for each type of payment. If the device cannot read payment data, the host software may prompt the cardholder to repeat the action or reject the transaction. ## Introduction to User Interface As mentioned in [**About DynaProx Components**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/introduction#id-1.4_about_dynaprox_components), DynaProx models equipped with a barcode reader (BCR) have a similar physical appearance as models without a BCR, as shown in Figure 6-1. BCR models are equipped with a camera and a QR code located on the front side of the device. * DynaProx devices have a user interface composed of two elements: a visual indicator consisting of four mono LEDs and a beeper that produces audible alerts. * DynaProx BCR devices have a user interface composed of three elements: a visual indicator consisting of four mono LEDs, a barcode reader, and a beeper that produces audible alerts. * DynaProx devices do not feature any input components such as buttons or touch screens.

Figure 6-1 – DynaProx and DynaProx BCR

### Component Details #### LED Ordering The arrangement of the four mono LEDs on DynaProx and DynaProx BCR devices is illustrated in Figure 6-1. The LEDs are labeled LEDs 1 to 4 and are ordered from left to right on the device. #### LED Status When DynaProx is powered on, its LEDs will illuminate green, when it is powered off, the LEDs will remain unlit. Figure 6-3 illustrates the on/off status of the LEDs.

Figure 6-3 - LED ON/OFF

#### BCR Status DynaProx devices equipped with a bar code reader have a status light that indicates whether the barcode feature is powered on or off.

Figure 6-4 - BCR Light

#### Beeper Alert All DynaProx devices are equipped with a beeper that produces a short beep lasting for half a second and a long beep that lasts for one second. ## Modes of Operation This section contains information regarding the operational modes of DynaProx's LEDs, beeper, and BCR light. It is important to note that DynaProx devices are not equipped with batteries. If there is no power supply to the device through the USB cable or RS-232 serial port, all LEDs, along with the BCR light, will not illuminate. In such instances, the user interface will resemble the device as it appears in Figure 6-1. #### Power On via USB Cable When the device USB cable is connected to the host USB port, a brief beep will sound and all four LEDs will turn on for half a second, as shown in Figure 6-5. Following this, LED 1 and LED 2 will remain illuminated, while LED 3 and LED 4 will remain unlit. After a duration of 10 seconds, all LEDs will turn off, and the device will enter an idle state. This occurs because the host sets the USB port into suspension mode, prompting the device to enter an idle state.

Figure 6-5 – LED Power on Sequence – USB Power On

#### USB Enumeration When DynaProx is in an idle state, it can be detected by a host through the USB HID port see Figure 6-6. After the host has connected to DynaProx, LED 1 and LED 2 will stay on. The device is in Ready State.

Figure 6-6 - LEDs Status (Idle State) Before Host Detection and LED Status (Ready State) After Connecting to Host

## Payment Transaction When the device is in ready state, two LEDs will be illuminated see Figure 6-7. When a card is detected only LED 1 will be on. If the device has a BCR and it is enabled, the BCR light will also be turned on see Figure 6-8.

Figure 6-7 - Ready State

Figure 6-8 – Card detected.

#### Payment Transaction Successful When a card is read, all four LEDs will turn on in sequence (1, 2, 3, and 4) followed by a long beep, indicating a successful transaction, see Figure 6-9. After a successful transaction, the device will return to the ready state when the transaction is complete, see Figure 6-10.

Figure 6-9 – LED Sequence – Payment Transaction Successful

Figure 6-10 – Return to Ready State After Successful Transaction

#### Payment Transaction Unsuccessful When the device is in ready state, two LEDs will be illuminated see Figure 6-11. When a card is detected, only LED 1 will be turned on. If the device has a BCR and it is enabled, the BCR light will also be turned on see Figure 6-12.

Figure 6-11 - Ready State

Figure 6-12 – Card Detected

In the event of a failed or canceled transaction, LED 1 will stay illuminated, and the device will emit two short beeps. If the device is equipped with a BCR, its light will also be on, as shown in Figure 6-13. The device will then return to the ready state, as demonstrated in Figure 6-14.

Figure 6-13 - Payment Transaction Failed

Figure 6-14 - Ready State

#### USB Power Supply Upon being connected to USB power (after a delay of three seconds), the device will emit a short beep, and all four LEDs will turn on for half a second, as shown in Figure 6-15. The device will then return to the Ready State.

Figure 6-15 - Device Connected to USB Power

#### RS-232 Power Supply Upon being connected to RS-232 power (after a delay of three seconds), the device will emit a short beep, and all four LEDs will turn on for half a second, see Figure 6-16. The device will then return to ready state.

Figure 6-16 - Successful Connection to RS-232 Power Supply

Figure 6-17 - Device in Idle State Before RS-232 Power Supply Connection

When the device is in a ready state, as explained in section 6.3.2.1 Power On , connecting an RS-232 power supply to it will not change its state and it will remain in the ready state see Figure 6-18.

Figure 6-18 - Ready State

#### Event Notification Mode When the device is configured in Event Notification Mode, the user interface will have the same appearance as depicted in [**Payment Transaction**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/operation#payment-transaction). #### Bar Code Read Only At present, no user interface elements such as LEDs or beeper sounds have been established for DynaProx. ### About the Status LEDs DynaProx provides four Mono LEDs (see [**About DynaProx Components**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/introduction#id-1.4_about_dynaprox_components)), numbered LED1 through LED4, which report the device’s current operating status. * The meaning of each LED depends on the device’s operating mode. See [**About Operating Modes** ](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/operation#about-operating-modes)and Error! Reference source not found. Most of the time, operators will check the device’s status using the LEDs when it is in Active Mode while the device is not performing a transaction. * LED blinking patterns have specific meanings as well, as described in DynaProx LED Allocation. A blinking LED generally means the device is actively doing something to change the state that the LED is indicating, and solid indicates a persistent state that would require an operator or cardholder to take action to change. One major exception is a device-wide functional failure state, such as a tamper state, where all LEDs flash urgently to call the attention of an advanced operator to intervene. In this manual, specific blinking patterns are described in more detail in the sections where they are relevant. For example, information about how the LEDs show the device’s connection status is in section [**Connecting to a Host**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/installation#id-4.3_connecting_to_a_host)**.** **DynaProx LED Allocation**
In This ContextLED1LED2LED3LED4
Active Mode, not armed for a tap transactionPowerConnectionReservedCard Read Result
Active Mode, armed for a tap transaction

Armed for Tap

Tap Read Progress

Tap Read Progress

Card Read Result

In This ContextLED1LED2LED3LED4
Device-wide failureDuring major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.
**DynaProx LED Patterns**
ColorMeans

Solid

Solid LEDs generally require an operator or cardholder to take action to change the state the LED is reporting.

Example: Host is connected. Cardholder or host would have to disconnect. Example: Host is disconnected. Host would have to initiate connection.

Blinking

Blinking LEDs generally indicate the device is in the process of doing / attempting something. Blink duty cycle and blink period are generally selected to show urgency or ongoing progress through a series of steps.

Example: Device is attempting to connect to the 802.11 access point.

Short time

LEDs sometimes light for a short time to indicate some process has ended (success or failure) and the device is going to transition to another state soon.

Example: Successful card read.

## About Sounds DynaProx products have a beeper that provides feedback to operators and cardholders about the internal state of the device: * The device sounds one short beep after it has successfully read a contactless tap, and the cardholder can safely remove the card or device from the contactless landing zone. * The device emits two beeps when reading a card or contactless payment device to indicate a card read error occurred. * The device sounds two beeps when an operator cancels a pending EMV transaction. The device provides an internal setting the host can use to adjust the global system volume. The device does not provide an interface to change the volume setting directly via buttons. If the device is too quiet or too loud: * Make sure the device is being ordered from the manufacturer with the desired volume setting. * Check to see whether the host software you are using provides a feature to check and/or adjust the volume setting. * If the host software does not provide that feature, request help from the development team that built the host software to check / change the volume setting. For details, see [**DynaProx Programmer’s Manual**](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual)**.** #### How to Play a Sequence of Tones To play a sequence of tones, follow these steps: * Make sure the device is in idle state. * Send an audio command to the device for playing a sequence of tones. For details, see [**DynaProx Programmer’s Manual**](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual)**.** ## Power Management #### About Power When properly powered through its USB port or RS-232 port, the device powers on automatically. For USB mode it will remain full powered mode to provide power to device. This device does not support USB suspend mode. The minimum required current and voltage are very important to the proper operation of the DynaProx reader. During contactless card reading, the NFC field is activated and the required current will rise from less than 100 mA to less than 800 mA for typically around 1 second. If the momentary current draw causes the supplied voltage to drop below 4 VDC, the DynaProx reader may reset and fail to complete the card read. Embedded systems and Single Board Computers (SBC) may find use in a wide range of card tending terminals. If the DynaProx will be supplied power through a USB port from one of these SBCs, it is important to be aware of the USB port current limitations, such as all USB ports may share a given amount of current, or the upstream current limitation of the system power supply. An optional power/ground connection is available on the DynaProx RS-232 connector, even if the actual RS-232 signals are not in use. #### How to Power On / Wake Up from Standby Mode / Power Off To power on the device connect the device to USB power or RS-232 Power. Recommended 800 mA available current during transactions. To power off the device, disconnect the device from USB power or RS-232 Power. If all LEDs are off, the device is in Powered Off mode. #### About Maintenance Reset For full host control, the device should not be allowed to run for > = 23 hours without a reset. To accomplish this, have the host application send a reset command twice a day separated by at least one hour. Example: Host software resets the device at 1 AM and 3AM. This keeps the device from initiating its own reset. ## Card Reading #### About Reading Cards The steps for starting a transaction and reading a contactless payment device are different depending on the device’s configuration and on the design of the host software. Host software developers should see [**Developing Custom Software**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/developing-custom-software) for implementation references. The solution developer should provide solution-specific instructions for operators to follow. A transaction generally follows this essential flow: * An advanced operator has already made sure DynaProx is configured properly and is connected to the host (see [**Connecting to a Host**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/installation#id-4.3_connecting_to_a_host)). When the device is connected to the host via USB and powered by the USB-C connector or RS-232, the host software may always keep a connection open to the device. * The operator makes sure DynaProx is receiving power either from the USB connection or from the RS-232 connection, and is awake and powered on (see [**How to Power On / Wake Up from Standby Mode / Power Off**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/operation#id-6.6_power_management) and [**About the Status LEDs**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/operation#id-6.4_about_the_status_leds)). * The operator uses the host software’s user interface (for example, a point of sale) to finalize a transaction amount, then initiates a transaction. In solutions that are designed to respond to cardholder input events that occur when the device is idle, such as unprompted tapping of a card or electronic payment device, the host software may respond to those inputs by notifying the host, and the host software may trigger other operations without being initiated by an operator (for example, the host software may immediately start a transaction, or alert the cardholder or operator to take action). * The host communicates with the device, and reports to the operator when the device is ready. * The operator guides and assists the cardholder in presenting payment. * The cardholder interacts with the device to present payment. The following sections provide additional details about presenting each of the available payment methods. * The host monitors the progress of the transaction, and when necessary, should report issues to the operator, who may need to relay the messages to the cardholder. * The device reports the success or failure of the transaction to the cardholder and to the host. #### How to Tap Contactless Cards / Devices To tap a contactless card or smartphone, follow these steps: * Check LED status: * The device shows the transaction status using the LEDs. LED1 lights solid and all other LEDs are off, per EMV standards, to indicate it is ready for a tap. * All devices report detailed transaction status to the host, and host software may report that information to operators so they can guide cardholders through the transaction (for example, “please tap your card now”). * If the cardholder is using an electronic payment device, such as a smartphone, make sure the payment device has NFC turned On and has a payment app configured to process transactions. For details, see the documentation provided by the smartphone manufacturer and payment app publisher. * Briefly hold the card, smartphone, or other contactless payment device over the contactless landing zone, indicated by the EMVCo Contactless Indicator symbol on the device’s face (see Figure 6-19). Because each smartphone model may have its NFC antenna placed differently, the ideal tap position may vary by make and model. For example, Samsung users may need to center the phone on the contactless landing zone, while Apple users may need to tap the top of the phone on the contactless landing zone. * Wait for LED status: * The device quickly lights the second LED to show it is processing, then lights the third LED to show it has successfully read the tap, then lights the fourth LED to show the read is complete (see Figure 6-20). * The device beeps once. * If the transaction requires a signature, the device sends a notification message to the host that includes the status Signature Capture Requested. In this case, the solution design collects the cardholder’s signature via a different method. * The device ends the transaction and reports the transaction status to the host. * If the device cannot communicate with the card, smartphone, or other contactless payment device: * The device ends the transaction. * The device lights LED4 for a short time. * The device beeps twice. * The device notifies the host that the transaction failed. If this occurs, the host software may choose to retry the transaction or revert to prompting the operator to perform another operation that is specific to the solution design.

Figure 6-19 - Tapping a Contactless Card / Smartphone

Figure 6-20 – Contactless Read LED Sequence

#### How to Scan Barcodes To scan a barcode, follow these steps: 1. Make sure you are using a DynaProx model that includes a barcode reader, indicated by QR code markings on the face of the device surrounding the barcode reader lens (see [**About DynaProx Components**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/introduction#id-1.4_about_dynaprox_components)). 2. If the barcode being scanned is not on a self-illuminated source such as a smartphone, make sure there is enough ambient light for the camera to read the barcode. In low light conditions, the barcode reader will only be able to read self-illuminated sources. 3. In some solutions, the operator may have to perform an operation in the host software to enable the barcode reader, or to start a transaction with the barcode reader enabled. 4. Wait for the device, the host, or the operator to prompt for a barcode read: 1. The device lights the barcode reader indicator LED next to the barcode reader lens. 5. Hold the barcode in front of the barcode reader camera: 1. If possible, use the light from the barcode reader indicator LED to align the barcode within the barcode reader’s field of view, which extends 16 degrees above / below and 21 degrees to the left/right of a line perpendicular to the barcode reader lens. 2. Hold the barcode as close as 1 inch from the lens. For smaller barcodes, the device will read immediately. If it does not, gradually move away up to 14 inches from the lens until the device reports a successful read. Larger barcodes must be far enough away from the device that the whole barcode is within the camera’s field of view; if a large barcode is too close, the barcode reader can only see a zoomed in portion of the barcode. 3. Do not tilt the barcode more than 60 degrees from parallel to the device’s face. 6. Wait for the device or the host to report the barcode has been read successfully: 1. The device beeps once. 2. The device turns off the barcode reader indicator LED.

Figure 6-21 - Scanning a Barcode

#### Apple VAS for DynaProx DynaProx products support Apple Value Added Services (Apple VAS) protocol. Contactless transactions using the Apple VAS protocol permits the device reader to perform the following supported operations: #### VAS App and Payment Mode (Dual Mode) The device reads both Apple VAS data and EMV payment data from a tapped smartphone or reads EMV payment data from a tapped card. When device sends ARQC to the host to conclude the transaction, it includes EMV payment data in container FC and includes VAS data, if available, in container FE #### AS App Only Mode (VAS Mode) The device reads only Apple VAS data from a tapped smartphone and does not read data from a tapped card. If the tapped smartphone does not support VAS, the device does not detect or read from the smartphone. When the device send ARQC to conclude the transaction, it includes VAS data in container FE and does not include EMV payment data in container FC. #### VAS App or Payment Mode (Single Mode) The device reads only Apple VAS data from a tapped smartphone or reads EMV payment data from a tapped card. When the device sends ARQC to conclude the transaction, it only includes either EMV payment data in container FC for cards, or includes VAS data in container for smartphones. #### Payment Only Mode (Payment Mode) The device operates the same as EMV mode (01). It reads only EMV payment data from a tapped smartphone or a tapped card. When the device sends ARQC to conclude the transaction, it includes EMV payment data in container FC and does not include VAS data in container FE. For details, see [**DynaProx Programmer’s Manual**](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual)**.** ## How to Tap Contactless NFC Tags / MIFARE Classic / MIFARE DESFire /MIFARE Plus Cards and Send Pass-through Commands DynaProx is compatible with near field communication (NFC) technology such as MIFARE Classic / MIFARE DESFire /MIFARE Plus contactless IC products (smart cards). To tap an NFC Contactless IC Product and Send Pass-through commands, follow these steps: 1. Check LED status: 1. Per EMV standards, the device indicates transaction status through its LED indicators, located on the front face of the device. When ready for a tap, LED 1 shines steadily while all other LEDs remain unlit. 2. All devices communicate transaction details to the host. The host software will relay this information to operators, allowing them to direct cardholders during the transaction, such as prompting "please tap your card now". 2. Place the card over the device's designated contactless landing zone, marked by the EMVCo Contactless Indicator symbol on the front face of the device. 3. Wait for LED status: 1. Initially, LED 2 illuminates, signaling the device is processing. The device subsequently illuminates LED 3 and LED 4, indicating card detection. Notifications are then sent to identify the card type and UID. 2. The Host application can further interact with the NFC Tag using pass-through commands. For details, see [**DynaProx Programmer’s Manual**](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual)**.** 3. If the pass-through command is the last successful command, the device will end the transaction, emitting a single beep signaling a successful transaction. The user then needs to remove the card. 4. If an error is detected, the device will end the transaction and emit two beeps to signal the error. The user then needs to remove the card. 4. The device notifies the host that the transaction has ended with the NFC Tag removed. --- # 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/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaprox-manuals/installation-and-operation-manual/operation.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.