# Large Retail Chains

A large retail chain, for the purposes of this documentation, is a company that operates many stores under the same organization, where managing individual client credentials for each store would be cumbersome.
For these retailers, we offer solutions to simplify credential management.

## Becoming a Registered Large Retail Chain

To use these features, you need to be a registered large retail chain.
Please contact our customer support at [Stø.no](https://stoe.no/tjenester/stoe-id-kort) for more details.

When you are registered, you will then be given access to the scope `vis-leg/shop_info`.
Use this scope when requesting access tokens through OIDC, together with the data scopes. See [authentication](https://docs.stoe.no/id-card/getting-started/authentication.md) for more information.

## Additional Properties

For large retail chains, there are two optional properties in the [_/merchant/session_](https://docs.stoe.no/id-card/API/ID-Card%20API.md#merchant-integration-api) endpoint.
The purpose of the properties is to give the users a more accurate account of where they have used the ID-Card.

### Shop Name

The `shopName` will be displayed to the user at the time of the scan, and in the history log in the app.
This should be a clear user-friendly name of the shop, for instance Stø Kiosk Tøyen.

### Global Location Number (GLN)

The `globalLocationNumber` is not displayed to the users, but used in internal systems.

> **Request Example**
>
> ```json
> {
>     "sessionId": "VisLeg-50f9cc4a-1354-4d57-88d8-e9a428e1016b",
>     "shopName": "Stø Kiosk Tøyen",
>     "globalLocationNumber": "9505567127630"
> }
> ```

> **Warning**
>
> If the scope `vis-leg/shop_info` is not present, the `shopName` and `globalLocationNumber` properties will be ignored and the organization name will be used by default.