Payments
Troubleshooting card readers
Fix discovery, Bluetooth, firmware and declined WisePad payments.
Last updated 13 September 2026
If Cobbtree cannot find the WisePad, turn the reader on, keep it next to the phone, turn Bluetooth on, and scan again from Payments & Devices. Forget the reader in iPhone or Android Bluetooth settings if it was paired there, then connect only through Cobbtree.
If the reader disconnects, keep it in range and wait for Cobbtree to reconnect, or tap Connect card reader again. Switching business or location disconnects the reader on purpose so it is not used on the wrong till.
A low battery can block firmware updates. Charge the reader, keep it connected, and do not take a payment during a required update.
If a payment is declined or cancelled, the sale stays unpaid. Retry on the same sale. A refund of a completed card-present sale does not need the physical reader unless Stripe specifically asks for it.
Related articles
Connect a card reader
Connect a BBPOS WisePad 3 through Cobbtree. Do not pair it in device Bluetooth settings.
Using the BBPOS WisePad 3
Take tap or chip-and-PIN payments on the WisePad through the same POS sale as Tap to Pay.
Why Tap to Pay is unavailable
Plan, permission, device, Stripe account or Apple / Google setup.
Was this helpful?