What's new is the changelog for this documentation — new guides, new device hubs, expanded reference sections, and notable corrections, most recent first. Check here to see what's changed since your last visit.

What's New Pages

Need More Help?

Site Revisions - August, 2026

This documentation is built to be read by AI tools as well as people. If you're using an AI assistant, coding agent, or LLM to build against MagTek readers, the resources below let it read and reason over this site directly.

llms.txt

MagTek publishes an llms.txt — a machine-readable index of this documentation. Point your AI tool at it to give it a complete map of the guides, command reference, and product pages.

Markdown for any page

Every page on this site is available as raw Markdown: add .md to the end of any page URL (for example, a page at /guides/emv-acceptance is also available at /guides/emv-acceptance.md). This gives an AI tool clean, structured text without the surrounding site formatting.

Ask a page a question

You can query any page directly. Send an HTTP GET to a page's .md URL with an ask parameter — for example:

The response returns a direct answer drawn from that page, along with the relevant excerpts and sources. Add an optional goal parameter to describe what you're ultimately trying to do, and the answer will be tailored toward it.

Need help, or want to tell us something? This page brings together the ways to reach MagTek support, check whether our services are running, and send feedback on the documentation or products. For how-to help building an integration, start with the Guides or a product hub; use the contacts below when you need a person, a service status, or want to report an issue.

Status Pages

Help us improve this documentation!

For additional support, please contact MagTek 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

• 🌐 Official MagTek Site:

• 💬 Developer Forum:

Resources is the reference shelf for the documentation site itself — what's changed, how to search it effectively, machine-readable indexes, and how to get help. It's the catch-all for the things that support your work here but aren't tied to a specific product or command.

In This Section

Stop Searching. Start Asking.

MagTek Support & Developer Site · Search

The new Magtek developer site is not just a repository of user documentation; it's designed to help you find exactly the information you need through its AI search mechanism. This is a bit different than the standard keyword searches you may be used to. The site works best when it answers questions rather than searches for words.

You ask the site for information it the way you'd ask a colleague and be sure to always name the product you're working with.

Here's why this changes everything.

Two ways to search the same thing

❌ Keyword search — the old habit

You type:

MagneSafe decrypt

You get a stack of pages — several for products you don't own:

• DynaFlex — Decrypting MagneSafe Data · /products/dynaflex/security

• tDynamo — MagneSafe Decryption Guide · /products/tdynamo/security

• eDynamo — Working with Encrypted Output · /products/edynamo/dev

You do the reading, the comparing, and the guessing about which page actually applies to you.

You ask:

How do I decrypt a MagneSafe swipe from a DynaFlex using the Universal SDK?

Synthesized answer

For the DynaFlex, read the encrypted track data from the swipe message, then decrypt it with the device's DUKPT key using the DecryptData() call in the Universal SDK. The KSN travels in the same message…

You might also ask

• Where does the KSN appear in the message?

• How is DynaFlex DUKPT different from tDynamo?

Sources it used

• DynaFlex — Decrypting MagneSafe Data

• Universal SDK — DecryptData Reference

You get an answer written for your device, the questions you'd ask next, and the exact in-site pages behind it — so you can open each one and verify.

1. Ask a question. Write a full question, not a pile of nouns. Start with "How do I…", "Why is…", or "What's the command to…". The more it reads like a sentence, the better the answer.

2. Name the product. Always say which reader, scanner, or SDK you mean — DynaFlex, tDynamo, eDynamo, RMS, Universal SDK. No product name, no precise answer.

Why naming the product matters so much: one topic — say, decrypting a swipe — has its own page for almost every device, and the steps differ in small but breaking ways. Leave the product out and the AI has to guess, or it blends instructions from hardware you don't even have.

If you could paste it into a message to a colleague, it's a good query.

• ❌ MagneSafe decrypt

• ✅ How do I decrypt a MagneSafe swipe from a DynaFlex with the Universal SDK?