Skip to main content
All CollectionsTaking a paymentTap to Pay
Tap to Pay on Android - Troubleshooting
Tap to Pay on Android - Troubleshooting

Steps to check if your Tap to Pay is not working

Ben avatar
Written by Ben
Updated over a month ago

If Tap to Pay on Android is not showing on the Charge screen in your app please ensure its setup by going to your app home screen, selecting the 'My devices' tile, then 'Setup Tap to Pay on Android' and accept the T&Cs.

1) Check your Android device is compatible

Your Android phone must have NFC capabilities and have Android 11 or higher.

For your Android phone to support Tap to Pay, you will need to enable NFC on your phone's settings.

2) Clear “Bad data” to reset the connection for Tap to Pay

If Tap to Pay is no longer working on your Android phone and your phone's operating system is Android 11 or higher, please follow the instructions below to clear the cache (temporary data) as it may resolve the issue.

  1. Press and hold on to the Lopay app icon from your home screen (not within the app) and then select the small “i” in the top right-hand corner of the pop-up menu.

  2. Go into the "Storage" screen

  3. Over here you will need to clear data and cache.

If your phone is compatible with Tap to Pay, you should see a pop-up about getting started on your home page. You can also go to “Your Devices” on the Homepage and select “Tap to Pay”.

3) Check your phone NFC is turned on

NFC is essential for contactless transactions, including tap-to-pay payments. You can check NFC is enabled in your phone settings.

4) Check your phone case is not interfering

An RFID-blocking phone case might interfere with the NFC (Near Field Communication) functionality on your phone. NFC is essential for contactless transactions, including tap-to-pay payments. Therefore, it’s advisable to avoid cases that may disrupt these signals to ensure seamless and secure transactions.

If after the above steps, Tap to Pay is not working, please contact us via the in-app chat or email us at [email protected].

Did this answer your question?