Google Pay is one of the safe & simple digital wallet platforms and an online payment system that has been developed by Google to make contactless payments, money transfers, paying bills, and more using the mobile app. Recently, Google has released Android 12 officially for its eligible Pixel devices and other brands are also getting into it. Meanwhile, it seems that plenty of users are facing the Google Pay Not Working issue on Android 12.

Mostly the particular issue is appearing to the Samsung Galaxy One UI 4.0 users based on Android 12. Although the closed beta testing program of One UI 4.0 for the Samsung Galaxy S21 series has been over, it looks like plenty of users are experiencing issues with the Google Pay app. Somehow the Google Pay app either does not open or it gets failed during the payment process. Samsung didn’t acknowledge this issue yet regarding the software bug.

Currently, Samsung has started rolling out the official One UI 4 stable update to the Galaxy S21 series. Meanwhile, interested Galaxy S20 series, Note 20 series, Galaxy Z Flip 3, and Z Fold 3 users can apply for the One UI 4 Beta program to taste out the Android 12 experience earlier. So, it’s quite unexpected that even after pushing beta updates for a while, users are still having app crashes or not working issues with the GPay app.

Also Read

Android 13 Google Pay Not Working, How to Fix?

Fix: Google Pay Not Working on Android 12

Well, if you’re facing the same issue on your Samsung Galaxy device running Android 12 (One UI 4) or any other Android 12 running handset then don’t worry. Here we’ve mentioned a possible workaround that should help you out.

  • Head over to the Settings menu on your device > Go to Apps (Manage Apps or Apps & Notifications).
  • Now, locate Google Pay (GPay) and tap on it to open App Info.
  • Tap on Storage > Tap on Clear Data > Select OK if the confirmation dialog box appears.
  • Finally, reboot the device > Open the Google Pay app > Set up the necessary info.
  • You’re done. The Google Pay not working issue should have been fixed now.

However, some users are claiming on the XDA forum that affected users have to root their devices with Magisk and enable the SafetyNet Fix module. But that’s not tested out yet by a majority of users most probably at the time of writing this article. So, we’ll have to wait for that workaround.

That’s it, guys. We hope this guide was helpful to you. For additional queries, you can comment below.