#dlavoie-plannit
oblique oxide
plucky nimbus
I believe that is specific to Stripe Terminal, which requires a location in order to function: https://stripe.com/docs/terminal/fleet/locations
That gets passed down to us as a requirement from the card networks, as far as I know
lone hull
We do create Stripe Locations and associate terminals with a location upon connection, but is that something to do with realtime terminal position?
plucky nimbus
It depends on your situation/integration
If you're a user that runs a food cart, you may want to register different locations depending on where you're parked for example
lone hull
in our implementation, we always use same Stripe Location
by connected account
I took chance to ask you about this... in case you experienced yourself (or already heard about) that kind of rejection from Google Play Store
plucky nimbus
I see what you mean, though it doesn't appear to be a blocking factor:
Your app should not request access to location in the background unless it’s required. If your app requests access to location in the background but it’s not critical to the app’s core functionality, you must remove it from your app and/or implement location access in the foreground, such as when your app’s activity is visible to users
The above seems to imply that you can ask for location in the background if it is a critical part of the core functionality. Am I missing something?
lone hull
make sense but they may ask why Stripe's sdk needs to ask for location in the background... BLUETOOTH_CONNECT and BLUETOOTH_SCAN are more usual permissions to ask for terminal payment
if access location is a core functionnality to our app, we need to fullfill a check list of justifications including a video etc
plucky nimbus
Do you have documentation from Google that shows the request for that level of explanation? I've never heard of them requiring video proof of a need for location permissions in apps that use Google Pay
lone hull
in the link I posted above, search for Declaration requirements
plucky nimbus
Ah, interesting. Have they come back and flagged anything about how Stripe accesses location? I would expect this would be as simple as "Stripe requires location in order for Terminal readers to function. This is how they use it. So that's all this permission is used for"