Linking of a kiosk to a Square Terminal

Hello,

We are currently working on developing a kiosk application that will use the Square Terminals to take payments.

Currently, we’re working on the configuration phase of the kiosk and we just wanted some clear guidance on the recommended process of attaching a square terminal to a kiosk.

They way we envision doing it is as follows:

1. Generate a kiosk ID (abc-123 for example)
2. Select a location
3. Call the v2/devices?location_id=xxx API to get a list of devices
4. Let the person setting up the kiosk choose a device from the list (e.g if they see abc-123-terminal) OR let them create a new one
5. If they create a new one, call the POST v2/devices/codes to create a new device code passing in the name field as abc-123-terminal (same as kiosk ID).
6. If they choose a pre-existing terminal (from step 4), store this terminal’s ID (unsure wether to store x.id or x.type == APPLICATION => x.device_code_id - please advise)
7. Use the stored device ID on checkout to send to that terminal.

While this does seem like a good plan, we’re not 100% certain that this is the Square recommended approach and would love to have a Square developer weigh in on the matter.

For example, in step 3 will we need to filter out some devices? If so, based on what criteria? I imagine we don’t want to display already paired devices?

Thanks,
C

3 posts - 2 participants

Read full topic