Compatible Retail Hardware


PlugnPay supports a range of third-party hardware devices to enable card-present transactions.

Devices can be used with:

  • Virtual Terminal
  • Smart Screens
  • Custom applications

Most supported devices connect via USB or Bluetooth and work across modern operating systems and browsers.


Supported Hardware Types

1. Keyboard-Emulated Card Readers

Recommended for most users

  • Works as a keyboard input device (no special integration required)
  • Compatible with Virtual Terminal, Smart Screens, or custom apps
  • Supported from any manufacturer if keyboard emulation is enabled

Includes:

  • Non-encrypted readers → may be used immediately
  • Encrypted readers → requires key injection

Supported encrypted brands:

  • MagTek
  • ID Tech

2. Mobile Card Readers

For mobile/tablet applications only

  • Supported only for MagTek devices
  • Requires:
    • Key injection (Key ID: 90125100)
    • Integration with MagTek SDK

Important:

  • Not compatible with Virtual Terminal or Smart Screens
  • Requires custom development

3. POS Terminals

  • Must follow the same rules as card readers:
    • Keyboard-emulated or SDK-based integration
  • Developers are responsible for firmware/software integration

Limitations:

  • Swipe (magstripe) only
  • EMV (chip) and NFC (contactless) are not supported

4. Receipt Printers

  • Any standard printer is supported
  • Must be accessible through your system’s print function

Compatibility Guidelines

Card Reader Compatibility Test

  1. Open a text editor (e.g., Notepad)
  2. Swipe a card
  3. If card data appears as typed text → compatible

Printer Compatibility Test

  1. Print any document or webpage
  2. If it prints correctly → compatible

Key Requirements

  • MagTek encrypted devices:
    • Request Key ID 90125100 at purchase
  • ID Tech encrypted devices:
    • Contact us for key configuration guidance

Important Notes

  • Keyboard-emulated readers work across desktop and mobile (via USB OTG adapters)
  • Mobile SDK-based readers require development effort
  • Mobile-specific readers will not function without SDK integration