1 of 6

Programmer's Manual

The DynaProx uses the shared DynaFamily Multi-Interface Card Reader Platform (MMS) command set. This manual is a device-scoped map into the with the sections this device relies on linked below.

Message Format & Structure

Every exchange with the DynaProx — the commands you send and the responses and notifications it returns — uses the standard Multi-Interface Card Reader Platform (MMS) message format. This section defines how requests, responses, notifications, and file messages are framed and parsed. The format is the same across DynaFamily readers and is documented once in the shared reference.

Applies to: DynaProx

Settings & Information - Group 0xD1nn

Reference Section

Information Available

The host and the device communicate with each other by exchanging blocks of data called Messages, which are standardized wrappers containing a payload that is either a command Request, a command Response, an unsolicited Notification, or a File.

Data Types & Shared TLV Objects

This section defines the primitive and composed data types, TLV (Tag-Length-Value) data objects, file structures, and cryptographic key formats used throughout the device command set, including track data, display strings, EMV configuration file types (ARQC, ARPC, Batch, CA Public Keys), security parameters, TR‑31 key blocks, certificate and CSR file structures, and card emulation.

Notifications

MMS notifications are the asynchronous messages the DynaProx reader sends while a transaction is running, reporting progress, state changes, and completion. Find the Notification Group you are looking for below and follow the links in the table to jump to a specific notification.

Applies to: DynaProx

From Transactions - Source 0x01nn

Reference Section

Information Available

This notification reports information about progress and state changes that occur during a transaction.

Configurations

This section focuses on properties, which the host can either read from the device to retrieve device information (such as its PCI hardware ID, serial number, firmware revision numbers, etc.), or write to the device to change device behavior, or to store values for future reference.

Appendices

These sections detail a variety of information on OIDs, codes, tips & taxes and more.

Applies to: DynaFlex II SCR

System Status Information - Property Group 2.3.1.nnn

Reference Section

Information Available

For modular management of device functions, information, and settings, this standard makes extensive use of Object Identifiers (also known as Object IDs or OIDs) as defined in ITU-T X.660 | ISO/IEC 9834-1.

Message Format & Structure

Applies to: DynaProx

Settings & Information - Group 0xD1nn

Reference Section

Information Available

Reference Section

Information Available

Configure how the device runs financial transactions — EMV terminal and kernel parameters, supported entry methods, and amount, currency, and timeout handling.`

Continues the transaction group with the remaining financial/EMV properties, such as contactless and additional processing options.

Configure the USB interface on USB-connected devices, including communication mode and power behavior during USB suspend. Applies only when connected over USB.

Programmer's Manual

Message Format & Structure

Settings & Information - Group 0xD1nn

Data Types & Shared TLV Objects

Notifications

From Transactions - Source 0x01nn

Configurations

Appendices

System Status Information - Property Group 2.3.1.nnn

Message Format & Structure

Settings & Information - Group 0xD1nn

Programmer's Manual

In this manual

See Also

For More help

Data Types & Shared TLV Objects

Data Types and Shared TLV Data Objects

Information in this group

Appendices

System Status Information - Property Group 2.3.1.nnn

For More Help

Notifications

From Transactions - Source 0x01nn

Firmware Updates - Source 0x09nn

From Device - Source 0x10nn

User Interface - Source 0x18nn

For more help

Configurations

About Configuration

Financial Settings - Property Group 1.1.nnnn

SRED Settings - Property Subgroup 1.1.2.nnn

Device Settings - Property Group 1.2.nnnn

Firmware Identification Information - Property Group 2.1.2.nnn

Hardware Information - Property Group 2.2.1.nnn Device

System Status Information - Property Group 2.3.1.nnn