# Mobile Payments SDK for Android ACCESS\_FINE\_LOCATION requirement vs. upcoming Google requirements **URL:** \ **Category:** Questions\ **Tags:** mobile-payments-sdk\ **Created:** [October 29, 2026, 7:32pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-for-android-access-fine-location-requirement-vs-upcoming-google-requirements/28392 "2026-10-29T19:32:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![JonathonMinard](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/jonathonminard/32/5154_2.png) [@JonathonMinard](https://developer.squareup.com/forums/u/JonathonMinard)\ **Post date:** [October 29, 2026, 7:32pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-for-android-access-fine-location-requirement-vs-upcoming-google-requirements/28392/1 "2026-10-29T19:32:27Z")
The documentation for Mobile Payments SDK for Android mentions that the ACCESS\_FINE\_LOCATION permission is required. Our app is currently specifying and requesting that permission. [Google is now cracking down on the ACCESS\_FINE\_LOCATION permission. They mention:](https://support.google.com/googleplay/android-developer/answer/16909972#location-permissions) > You may only request `ACCESS_FINE_LOCATION` if neither the Android location button (for apps targeting Android 17 or higher) nor the `ACCESS_COARSE_LOCATION` permission (applicable across all Android versions) can support your feature. Our app currently targets Android 16 and we are not in a hurry to target Android 17. However, the current pattern is that targeting Android 17 would be a requirement for Play Store app updates by September 2027. I’m curious as to what Square’s plans or recommendations are for dealing with this new requirement. I assume that the recommendation would be to submit a Play Console declaration to get permission to continue using ACCESS\_FINE\_LOCATION. In that case, we’d likely need some more information as to why that’s needed instead of ACCESS\_COARSE\_LOCATION. I understand that it’s gathered because payments are sensitive and logging as much relevant information as reasonable is preferable, but I’m unsure if I can explain that in a way that Google would accept. ---
**Author:** ![andrew423smith](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@andrew423smith](https://developer.squareup.com/forums/u/andrew423smith)\ **Post date:** [October 30, 2026, 6:18am UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-for-android-access-fine-location-requirement-vs-upcoming-google-requirements/28392/3 "2026-10-30T06:18:23Z")
Good question. Square should clarify whether ACCESS\_COARSE\_LOCATION suffices or provide official guidance and justification text for the Play Console declaration. Many developers will face this, so an official response before Android 17 enforcement would help. ---
**Author:** ![jseok](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@jseok](https://developer.squareup.com/forums/u/jseok)\ **Post date:** [October 30, 2026, 1:37pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-for-android-access-fine-location-requirement-vs-upcoming-google-requirements/28392/4 "2026-10-30T13:37:00Z")
Our documentation now includes a [precise-location explanation you can use for your Play Console declaration](https://developer.squareup.com/docs/mobile-payments-sdk/android#why-precise-location-is-required). The Android Mobile Payments SDK currently requires `ACCESS_FINE_LOCATION`; coarse location isn’t a supported replacement. Precise location supports geographic payment eligibility, particularly near country borders, as well as fraud detection and dispute investigation. ---
**Author:** ![JonathonMinard](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/jonathonminard/32/5154_2.png) [@JonathonMinard](https://developer.squareup.com/forums/u/JonathonMinard)\ **Post date:** [October 30, 2026, 3:01pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-for-android-access-fine-location-requirement-vs-upcoming-google-requirements/28392/5 "2026-10-30T15:01:16Z")
Thank you. That should hopefully be enough.