Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel2
maxLevel2
outlinefalse
typelist
separatorpipe
printablefalse

FAQ - Frequent Asked Questions

How do I connect the card reader to the phone/tablet?

Pairing should be easy with the HiLite card reader, however the steps below are a good reference.

  1. First, though it may seem obvious, don't forget to make sure that Bluetooth is enabled on the device.

  2. Enable location permissions for the app if prompted. Detailed instructions are here.

  3. After that, Bluetooth pairing is simply carried out through the Handpoint Payments mPOS App or through the device settings.

Is it possible to pair more than one phone with my card reader?

It certainly is, but only one at a time. Each time you connect the card reader to a new device, you need to pair it. 

Can we exchange readers between merchants?

Certainly. It is advisable to do a flash reset after assigning the reader to the new merchant in Handpoint’s Portal TMS.

If a card reader is set up with a merchant who then changes their name or email address, their merchant account needs to be updated in Handpoint's Portal TMS.

Experiencing problems with iPhone or iPads?

It may be necessary to first unpair the card reader with the previous phone before attempting to pair it with another. This is a common issue that iPhone/iPad users run into, and it's not exclusive to our card readers. 

Other advice to troubleshoot is included in the Quick Fixes section, such as:

  • Restart the mpos Payments app on the phone / tablet and the card reader

  • Check the network connection, restart if necessary. Be aware that Firewalls might prevent the solution from working correctly.

  • mPOS: Disconnect and reconnect the Bluetooth connection

  • mPOS: Restart the phone / tablet running the Handpoint Payments mPOS app.

  • Perform a Flash reset of the HiLite card reader.

  • Pair the card reader via BT through the device settings instead of through the mpos app.

Possible errors

Thankfully your merchants will not face errors frequently. We have listed below the common error messages that could be displayed on the terminal or on the mPOS application as a guide to quickly provide support to your merchants.

...

Although the text of the screenshots might look different in your app, the suggestions are the same.

Communication Error / COMM ERROR

This means that there was an error in communication between the card reader and the mPOS app. 

The app might request permission to turn on Bluetooth

Image Removed
Image Added

suggestions:
  • Ensure that you are within Bluetooth range

  • Restarting the card reader

  • Disconnecting/reconnecting the Bluetooth connectivity

  • Remove the card reader from the saved Bluetooth devices and re-pair the device

Network Error/Send Error

Frequently, this means that the internet connection is not working properly or, in rarer cases, Handpoint's back-end system or the systems it connects to are temporarily out of service. 

Image Removed
Image Added

suggestions:
  • Check internet settings

  • Connect to a cellular hotspot point, rather than WiFi, to avoid firewalls

  • Restart the internet connectivity

Processing Error

An unexpected error was encountered during transaction processing.

Image Removed
Image Added

suggestions:
  • Please retry the operation

Device Not Initialized

The card reader didn't fetch its configuration settings during the initial setup, or there was an error registering the device in the Handpoint system.

suggestions:
  • Try updating the card reader

Bad Request

This is a response message from the processor/acquirer, and could have multiple causes.

suggestions:
  • Please proceed escalate to Handpoint following the providing support guide (step 4)

System Error! Invalid Keys

This is a message that may appear on the device screen. This is because the device has been dropped or has been turned off for a long time.

suggestions:
  • The reader must be replaced or sent for repair (this error cannot be resolved remotely).