#Gabriel1234-terminal-location
untold bridge
For each card-present transaction we're required to have an address associated for regulatory reasons, so we implemented the location as a means of tracking that.
dark sorrel
for bluetooth devices couldn't that simply be the phone's current location?
if I'm understanding correctly, our server makes a call to the /locations on stripe API to create a location and then clientside we would input that created location id in the bluetooth configuration?
untold bridge
It can't be the phone's current location, as we mostly need it to be able to associate the reader with a business' address.
dark sorrel
how granular of an address is needed?
untold bridge
You'll need a full address: https://stripe.com/docs/api/terminal/locations/create#create_terminal_location-address
dark sorrel
ok so the location is the location of the business and not the current location of the bluetooth device? i.e. if the business location is in arizona but is collecting money in california then there should be no problem?
real totem
👋 stepping in here. The location should be the physical address that the reader operates at. However, if it moves around then you can just use one primary address. We detail this here: https://stripe.com/docs/terminal/fleet/locations
dark sorrel
ok let me take a step back and detail our use case a bit and maybe that'll clear up some things
our company provides software to many other companies, they enable a 'stripe integration' in our software which encapsulates a lot of things and allows them to use our mobile app which collects payments on their behalf
prior to version 2 this was no problem and fairly seamless for them (aside from creating a stripe account and linking it)
our customers host events at random locations as well in which they collect money (donations)
so this one primary address should be our customer's main address our ours or do you suggest something else?
real totem
When you say "random locations", is that scoped to a specific area? Like random locations within a city? Or truly you expect for anywhere across the country to collect these donations?
dark sorrel
for the sake of argument lets say anywhere across the country
but probably for most of our customers it's localized
real totem
Okay well if you supply a location that isn't in proximity to the actual location of the charge then you may see conversion rates drop as this can make issuers think that the charges are potentially fraudulent. It is basically recommended that the location registered be in proximity to the actual physical location of the device. So I would recommend in that case having a "primary location" in the relevant city that the reader will be used in.