Skip to main content
Register each checkout as a payment location before it checks customers in or takes payments. Your backend does this once per POS or self-checkout, with one server-to-server call, and again whenever the checkout’s QR code or store changes. A payment location is Lobyco’s name for one checkout. That is a cashier POS, or a self-checkout the customer moves to after offloading the basket. The customer scans the QR code sticker at that checkout with the app. The registration tells Lobyco which sticker belongs to which checkout in which store.

​
Before you start

​
The procedure

1

​
Choose the identifier

The payment location identifier is the key the POS sends in every check-in and payment call. It must be unique across your whole estate and stable over time. Lobyco recommends {storeId}_{posId}, which names both the store and the till and stays readable in logs.
2

​
Register the location

POST /v1/payment-locations/{paymentLocation}/setupSend three things:
  • storeId, the store the checkout is in.
  • qrCode, the value printed on the sticker at that checkout.
  • type, Cashier or SelfCheckout.
The same call updates a location that already exists, so run it again when a sticker is replaced or a till moves to another store.

​
Failure and edge cases

A 200 OK means the location is registered. To check it later, read it back with GET /v1/payment-locations/{paymentLocationId}, which returns the store, the type, the QR codes and the current check-in state.
  • A QR code belongs to one location only. If the code is already assigned to another payment location, the call fails. Send force: true to move the code to this location, for example when a sticker has been moved to a different till.
  • The location must exist before check-in and payments. A check-in or a payment call for a payment location Lobyco does not know fails. Register locations when a checkout is commissioned, not on its first sale.

​
API reference

Endpoint documentation: Payment Coordinator.
  • Registering at POS — the check-in flows this location takes part in.
  • Payments — creating and capturing a payment at this location.
Last modified on October 8, 2026