After creating Locations, you can use them to help you group readers, improve reader discovery flows, customize their settings by physical location, and more. This can be especially helpful for marketplaces with many connected accounts.
Scoping connection tokens Server-side Internet-connected readers
When creating a ConnectionToken for the Terminal SDK, you may provide a
location parameter to control access to internet-connected readers. If you provide a location, the ConnectionToken is only usable with internet-connected readers assigned to that location. If you don’t provide a location, the ConnectionToken is usable with all readers.
Registering a reader to a location
Your reader must be registered to a location in order to accept payments. The process for registering your reader to a location differs based on whether it’s an internet-connected reader or a Bluetooth reader.
Internet-connected readers Server-side
Register internet-connected readers like the Verifone P400 to a Location during reader registration.
You can also register readers in the Dashboard, under Locations.
BBPOS Chipper 2X BT Dashboard
Filtering discovered readers
Internet-connected readers Client-side
Your application uses the SDK’s
discoverReaders method to look for readers it can connect to. When discovering an internet-connected reader like the Verifone P400 or BBPOS WisePOS E, you can discover the intended reader more easily by filtering results by location.
With the code below, only readers in a given location are returned to your app’s callback. You can find the location’s ID in the Dashboard, under Locations.
BBPOS Chipper 2X BT
Because your app uses Bluetooth discovery to find a BBPOS Chipper 2X BT, it can only search for nearby readers. There’s no need to filter by location.