An Active US Infusionsoft Payments account is required to use the Infusionsoft Mobile Payments feature.
The Infusionsoft Payments Mobile Card Reader allows for payments to be taken, via orders, created in the Infusionsoft Mobile application, for Android and IOS. There are 2 versions of the Infusionsoft Payments Mobile Card Reader. The following steps will instruct on connecting the older audio jack model, and the new Bluetooth model, to a compatible device.
Table of Contents:
How to Use
- Launch the Infusionsoft Mobile application, on a compatible device
- Expand the Menu and tap Settings
- Tap on Card Reader to view connected readers, or add a reader
- Insert Infusionsoft Payments Mobile Card Reader (audio jack model) or have the Infusionsoft Payments Bluetooth Reader, nearby. Tap Connect your card reader
- Once the reader is connected to the device, a confirmation message will appear. AUDIOJACK is the audio jack reader model connected.
MOB-## is the bluetooth reader model connected
- The Infusionsoft Payments Mobile Card Reader battery level can also be viewed from the card reader settings
What devices are supported?
- IOS: requires version 8.0 or higher
- Android: requires version 4.0 or higher
How often does the Infusionsoft Payments Bluetooth reader need to be charged?
- The Infusionsoft Payments Bluetooth reader can be used 200 to 400 times before needing to be recharged.
What do the different LED indicators on the Infusionsoft Payments Bluetooth reader mean?
- Red solid: device is on and has sufficient charge
- Red flashing: device is on, but has low battery; also indicates charging battery
- Blue solid: device connected via Bluetooth
- Blue flashing: device ready to connect, but not yet connected
Is internet access required?
- Yes, internet access is always required to process a payment (Internet access is also required for mag stripe transactions).
How do I allow card present processing in the rare case of a bad chip?
- Swipe is allowed after 3 failed attempts to dip (using the chip). Those 3 attempts and subsequent dip must occur within the same transaction.