General Chipper / EMV Reader Troubleshooting
Here are some general EMV Reader / Credit Card Chipper troubleshooting steps not specific to any one device.
- Reseat Cable (unplug / replug)
- Hard / Soft reset chipper (either with power button or in some cases small reset button)
- Plug cable directly into chipper if previously in cradle
- Try same reader on other terminal (or cradle if applicable)
- Swap cable connecting EMV reader and terminal with a new one. You can use this picture to determine cable type.
Most chippers use a standard Micro-USB to USB-A
Cables for chippers are not proprietary, meaning they are not particular to any one device, and you can purchase a replacement from anywhere that sells cables.
Just be sure that the cable has the ability to transfer data. Most modern cables, unless they are very cheap, have this ability and will often be denoted as not data transfer capable if they are not - meaning this is really not a concern, but just something to keep in mind if purchasing a replacement cable
One side of the cable, the side that goes into the terminal, needs to be Type A or USB 3.0, check your USB slots in your terminal to determine which is best (use picture for reference)
Be sure to consider cable length as you don't want a cable that is too short to allow the chipper to be freely moved around or a cable that is too long and can create a mess. The standard cable included with most chippers are about 1 meter / 3.3 feet which works for most locations. If anything, measure the current cable in use and get a replacement that is the same size.
- Check if Uniterm is running (use task manager, advanced)
- Relaunch onePOS software on the terminal chipper is connected to (be sure to see if white uniterm screen appears briefly on launch)
- Relaunch Terminal 1 / main terminal
- Check Windows hardware devices to see if device appears as connected
If none of these steps work, it is possible the EMV Reader is faulty and needs to be replaced.
If the issue is occuring with ALL readers and / or all errors say something like COMM error, try restarting the router.