How the DynaProx protects cardholder data and manages keys. These are shared DynaFamily concepts, documented in the Guides Section:
Applies to: DynaProx
Reference Section
Information Available
DUKPT: 3DES/TDEA --> AES Migration
How DUKPT derives a unique key per transaction, and the path (and reasons) for moving from legacy 3DES/TDEA DUKPT to AES DUKPT on your devices and host.
Key Serial Numbers (KSN)
What a KSN is, how it's structured, and how it identifies the unique key used to encrypt a given transaction under DUKPT.
Message Authentication Codes (MAC)
How a MAC lets the host and device confirm a message hasn't been altered in transit, and when one is required.
Encryption & Decryption
How the reader encrypts data at the point of read (SRED), how to determine which key was used, and how to decrypt the output on your host.
TR-31 Key Blocks
The ANSI TR-31 key-block format used to transport and load keys securely into the device.
PCI requirements (24-hour Reset, device lock)
The operational requirements the device enforces for PCI compliance: the 24-hour automatic reset and the device lock feature.
Reference Section
Information Available
This section covers how DynaFamily readers protect cardholder data and manage keys.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-800-788-6835 (US) | +1-562-546-6616 (International)
🕐 Hours: Monday-Friday, 6:00 AM - 5:00 PM PST
Online Resources:
🌐 Official Site:
💬 Developer Forum:
Documentation Feedback:
Help us improve this documentation!