MagicTerminal
The true AFT terminal. Built for card-present money movement on Android POS, with a deliberately simple integration — just two APIs to push a transaction.
After the Visa AFT mandate, card-present money movement needs a terminal that classifies Account Funding Transactions correctly at the point of sale — not a retail POS with AFT bolted on. MagicTerminal was built for exactly that: AFT-native by design, running on conventional Android POS hardware, integrated in two API touchpoints.
To the best of our knowledge, it is the only AFT-native terminal solution on the market today.
Two APIs. That is the integration.
One POST wakes the terminal with an amount, an order ID, and a terminal ID. The customer taps, dips, or swipes. A webhook fires when the payment completes. No device SDK, no firmware, no PCI project on your terminals. Most teams integrate in days.
AFT-native by default
The correct AFT indicator, MCC, and sender-data handling are applied automatically on every applicable transaction. There’s no per-device configuration to remember and no compliance guesswork in the field. Read the Visa AFT mandate guide for the regulatory backdrop.
Runs on conventional Android POS hardware
NFC-ready devices, contactless / chip / magstripe on mainstream models. No proprietary hardware lock-in, no long procurement cycles. The compact form factor fits a counter, a kiosk, or a mobile agent bag.
Fleet management: API or portal
Activate or deactivate devices in a single click. Bind each terminal to a GPS geofence. Set per-device authorization limits. Push OTA updates to a pilot subset, then to the whole fleet. Manage it all programmatically via the fleet API, or through the Inyo portal — whichever fits your team.
Frequently Asked Questions
What is MagicTerminal?
MagicTerminal is Inyo’s card-present payment solution built for Account Funding Transactions (AFTs) on Android POS hardware. It is AFT-native by design and integrates in just two API touchpoints.
How simple is the integration really?
One POST request wakes the terminal with an amount, order ID, and terminal ID. A webhook fires when the payment completes. No SDK on the device, no firmware to ship, no PCI certification project on your terminals.
What hardware does MagicTerminal run on?
Conventional Android POS terminals from mainstream vendors, with NFC, chip, and magstripe support. No proprietary hardware lock-in.
Do I need to build a fleet management system?
No. MagicTerminal exposes a fleet management API for programmatic control, but you can run the entire fleet from the Inyo portal instead — activate/deactivate devices, set GPS perimeters, configure limits, push OTA updates — without writing code.
Is MagicTerminal really the only AFT terminal solution?
To the best of our knowledge, yes. Most smart POS terminals are built for retail checkout and cannot classify a card-present transaction as an AFT at the point of sale. MagicTerminal was designed for this from the start.
Related reading
MagicTerminal: The Full Article
The deep technical guide to MagicTerminal: why AFT-native matters, the two-API integration, fleet management, security controls, and OTA updates.
Smart Terminals for Money Transfer Agents
The complete guide to card-present account funding for agent networks: NFC, smart routing, and AFT compliance.
AFT-compliant card-present payments — in two APIs
Talk to the Inyo team about MagicTerminal for your agent network.
Talk to Sales