If your Terminal deployment uses many readers across multiple physical locations, keeping track of them all can get overwhelming. Locations help you manage readers and their activity by associating them with a physical operating site. They also ensure your readers download the proper regional configurations.
Use the Terminal Locations object to group readers, view their connectivity status, and customize their settings by physical location. This can be especially helpful for marketplaces with many connected accounts.
Creating a location Server-side Dashboard
To create a new location, use the create location request.
You can also create locations from the Stripe Dashboard, under Locations.
Whenever you register the Verifone P400 , the specified location groups the reader and defines its country settings. If you do not provide a location, the reader will be ungrouped on your account and default to the regional configuration associated with the country of your Stripe account.
When you connect to a BBPOS Chipper 2X BT for the first time, it will be automatically registered and will be ungrouped on your account. The BBPOS Chipper 2X BT can only be used in the United States.
Creating Connection Tokens Server-side
When creating a ConnectionToken for the Terminal SDK, you may provide a
location parameter to control access to readers. If you provide a location, the ConnectionToken is only usable with readers assigned to that location. If you do not provide a location, the ConnectionToken is usable with all readers.
Registering a reader to a location
Verifone P400 Server-sideServer-side
Register Verifone P400 readers to a location for better onsite discoverability. When discovering readers, your app can provide a
location parameter to only show readers in that location.
You can also register readers in the Dashboard, under Locations.
BBPOS Chipper 2X BT Dashboard
Filtering discovered readers
Verifone P400 Client-side
Your application uses the SDK’s
discoverReaders method to look for readers it can connect to. When discovering a Verifone P400, 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.
Setting a custom splash screen Dashboard
A splash screen is the default screen displayed when your Verifone P400 is ready to accept payments.
Set a custom splash screen for all of your Verifone P400 readers:
- From the Readers section of your Dashboard, click on your default location.
- In the location details, click Reader settings.
- Upload an image (less than 2MB in size) to display on your readers. The Verifone P400 has a 320 x 480 display resolution and you will be prompted to crop your image to fit those dimensions.
You can also customize the splash screen for each location, so that all readers registered to a site share the same branding. For Connect users, custom splash screens enable you to create different checkout experiences to reflect the various merchants connected to your platform.