We are developing an internal application that will take payments natively from the Square chip reader via the Read SDK, however I am a little confused around the SDK authorization (you have to download the SDK using a Square application ID and generated repository password) requirements and working with multiple Square accounts.
Background: we currently have eight physical locations (depending on how the coronavirus plays out :S) to service. After we grew to three locations, we moved away from having a single Square account with multiple Square “locations”, to individual Square accounts each with a single Square location. This was due to limitations around inventory management.
My concern at the moment is that, given what I can see of the SDK authorization / installation process, an app that uses the Reader SDK can only service/take payments for Square locations associated with the Square account that was used to authorize the SDk download - presumably the App ID or similar is being embedded in the SDK and used as a check reference.
If this is truly the case, then we will have to publish eight different versions of our app, one for each physical location / Square account, with individualized copies of the Reader SDK.
Somewhat annoying, but not the end of the world - I’m just keen to understand the implications before I get too far down any particular path…