The BBPOS WisePad 3 is a Bluetooth LE device. It collects payment details, but relies on a paired mobile device for communication with Stripe. Connecting your app to a Bluetooth reader requires two steps:
Use this guide to connect your application to the reader using the
First, turn on the reader. Then, from your application, search for nearby Bluetooth readers using the
discoverReaders method and
bluetoothScan discovery method.
Bluetooth scan searches for all nearby readers and returns a list of discovered readers to your app. As the discovery process continues, the SDK continues to invoke the
DiscoveryDelegate.didUpdateDiscoveredReaders method with the latest list of nearby readers.
With the Bluetooth scan discovery method, you can set a timeout to scan for a set period of time. This is useful for managing battery life or triggering an error message if no devices are found.
In your mobile application, we recommend displaying an auto-updating list of discovered readers, with serial numbers or labels to help users identify their reader.
Connecting to a reader
To connect to a discovered reader, call the
connectBluetoothReader method from your application.
You must supply the
connectBluetoothReaderwith a valid
BluetoothReaderDelegate. The SDK uses this delegate for all reader events while connected, including reader software updates. These updates include regional configurations that keep you up to date with card network and issuer requirements, as well as potential security updates. To learn more, see Required updates.
The WisePad 3 uses BLE Secure. The first time you attempt to connect to a reader your POS device shows a “Bluetooth Pairing Request” dialog. Select “Pair”. After the POS connects to the reader, the reader beeps twice.
On iOS, for your app to run in the background and remain connected to the reader, configure your app to include the required background mode.
Don’t program your app to call
disconnectReader to conserve power. The reader efficiently handles power management by dimming its screen.
Your app must implement the
UnexpectedReaderDisconnect callback to handle when a reader disconnects.
In your implementation of this callback, display a UI to notify the user that the reader disconnected. You may also want to call
discoverReaders to begin scanning for readers and reconnect. Your app can attempt to automatically reconnect to the reader that disconnected, or display a UI for your user to reconnect to another reader.
The BBPOS WisePad 3 can disconnect from your app if it goes out of range or runs out of battery. To simulate an unexpected disconnect while testing, power off the reader.
The BBPOS and Chipper™ name and logo are trademarks or registered trademarks of BBPOS Limited in the United States and/or other countries. The Verifone® name and logo are either trademarks or registered trademarks of Verifone in the United States and/or other countries. Use of the trademarks does not imply any endorsement by BBPOS or Verifone.