#zperkins
1 messages · Page 1 of 1 (latest)
It is primarily about organizing reader so that you can discover at a specific location and give a manageable list of readers for merchant staff to choose from
ah okay. So with regards to BT readers, where we've got only the nearby readers getting returned we shouldn't have problems with this? (e.g. we won't get into a situation where there's an unreasonably giant, hard to manage list)
That seems reasonable
We haven't fully decided either way on an implementation, but as long as the location information doesn't affect the payment itself in any way then we should be good
You might find it easier to review with locations for each site, but that's up to you
alright sounds good