What this reader is, and when it still matters
The UniMag II is an audio-jack magnetic-stripe reader used with the Mindbody business app to take card payments away from a fixed terminal. It is a stripe-only device: there is no chip slot and no contactless antenna. That single fact drives most integration decisions, so it is worth stating up front rather than discovering during a pilot.
Ambimat is asked about this class of device when a customer is planning a mobile point-of-sale rollout and wants to know what the audio-jack generation can and cannot do compared with a modern Bluetooth or USB-C reader. The short answer: it works, it is cheap, and it is constrained by the headphone jack in ways that newer readers are not.
Hardware profile
| Form factor | 30 mm × 11 mm × 45 mm, black |
| Read head | Two-track magnetic stripe, bi-directional |
| Host interface | 3.5 mm stereo audio jack |
| Card technologies | Magnetic stripe only — no EMV contact, no contactless |
| Encryption | Reader-level encryption of track data; keys are injected by the reader vendor, not by the merchant |
Two engineering consequences follow. First, the reader draws its power and carries its signal over the audio path, so host audio behaviour — sample rate, gain, automatic level control — affects whether a swipe decodes. Second, because track data is encrypted in the read head, the phone never handles cleartext card data; that is what keeps the phone out of the cardholder data environment.
Prerequisites, both platforms
- The Mindbody business app, and a Mindbody merchant account with integrated processing enabled. The reader will not work against a third-party processor.
- A mobile device — the reader is not supported by the Mindbody desktop software.
- An accessible 3.5 mm headphone jack, directly or through an adapter.
Readers sourced from other vendors are not interchangeable here even where the physical connector matches, because the app expects the key and encoding scheme its own reader was provisioned with.
iOS notes
- Requires the Mindbody business app on iOS 9 or later.
- Devices without a 3.5 mm jack need Apple’s Lightning-to-3.5 mm headphone adapter. Plan for this on any recent iPhone — it is the most common reason a deployment stalls on day one.
- Device support is comparatively predictable, because the hardware and audio stack vary far less across the iPhone range than across Android.
Android notes
Android is where the audio-jack design shows its age, and where most support effort goes.
- The reader is compatible with most, but not all, Android handsets, and it requires an open headphone jack.
- Compatibility is handled by a per-model settings profile. The reader vendor publishes an XML file keyed by device model number, holding the audio parameters known to decode reliably on that handset. Profiles are added either from vendor testing or from merchants who found working settings and reported them back.
- A model absent from the file is not necessarily unsupported — it may simply be untested. Search the file for your exact model number.
- If your model appears under a different carrier variant, the profile is usually still valid.
- After a handset changes or a profile is updated, reload the XML in the UniMag utility so the app picks up the current parameters.
For a fleet rollout, the practical advice is to standardise on one or two handset models, confirm both are in the profile file, and keep spares of the same model. A mixed-handset estate turns a solved problem into a recurring support queue.
Taking a payment
The flow is the same on both platforms. The business app detects the reader when it is plugged in, so there is no pairing step. At checkout, choose Credit/Debit; if the reader is seated correctly the swipe prompt appears within a few seconds. If it does not, the fault is almost always physical or profile-related rather than an app problem.
When a swipe will not read
- Seat the plug fully. A partially inserted jack is the single most common cause, especially through a phone case.
- Remove the case. Thick cases stop the plug reaching full depth.
- Check the adapter. Third-party Lightning adapters are frequently the culprit on iOS; test with Apple’s own.
- Reload the settings profile. On Android, refresh the XML before assuming a hardware fault.
- Swipe steadily. Two-track bi-directional heads tolerate either direction but not an inconsistent speed.
- Try a known-good card. Worn stripes fail on any reader; rule the card out before the device.
Choosing this or something newer
If a customer is specifying mobile acceptance today, the audio-jack generation is rarely the right starting point: handsets are dropping the jack, and stripe-only acceptance carries the liability position that came with the EMV shift. It remains reasonable where an existing estate already runs it and stripe acceptance is genuinely sufficient. Where chip or contactless acceptance is needed, that is a different device class — see our notes on EMV liability shifts and fallback transactions and NFC card emulation mode.
Authoritative reference
Mindbody’s own support documentation is the normative source for app behaviour, ordering and account setup, and it changes independently of this page: Mindbody — Mobile credit card swiper. The device compatibility profile file is maintained by the reader vendor and should be checked directly for current model coverage.
This page is Ambimat’s own engineering summary and does not reproduce Mindbody’s support documentation.
