Pairing the Browser App
If you run Fuze Store in a web browser (Chrome, Edge, or Safari at store.fuze-store.com) on the same computer as Fuze Store Hub, you'll need to pair the browser with the Hub once. The pairing replaces the long-lived LAN token used by the mobile apps with a short-lived session token scoped to that browser.
You only need this on web. iPhone and Android tablets continue to use the QR-code/LAN-token flow described in Connecting to Your Store.
Why a separate flow?
Modern browsers block insecure (http://) requests from a secure (https://) page — that's called the mixed-content policy. The browser app is served over HTTPS, so Fuze Store Hub also serves a parallel HTTPS endpoint at https://localhost:18443 that the browser can reach. The catch: the certificate is self-signed, so Chrome warns you the first time. You accept the warning once, then exchange an 8-digit code for a session token, and you're done.
What you'll need
Open the Fuze Store Hub desktop app. The pairing endpoint is only reachable while the Hub is running.
Other Chromium-based browsers work too. Firefox needs an extra cert-trust step that we do not currently document — Chrome is easier.
After the first pairing, the session token lasts 30 days. The browser silently re-uses it — you only walk this flow once.
The four steps
1. Open the wizard
In the browser, sign in to Fuze Store at store.fuze-store.com, then go to Configurations → Preferences → Local Server. You'll see a Pair this browser with Fuze Store Hub card. Click Get started.

2. Trust the local certificate
Click Open trust page. A new tab opens at https://localhost:18443/health. Chrome shows a warning that the connection is private to your computer — that's expected.
Click Advanced in the warning, then Proceed to localhost (unsafe). You'll see a small JSON response confirming the Hub is up. Close that tab and click Verify connection back in the wizard.

"Unsafe" sounds scary, but the connection only ever leaves your computer's loopback network — it doesn't go to the internet. Chrome warns the same way for any self-signed cert. You only do this once per browser.
If you need to change the Hub's HTTPS port (the default is 18443), expand the Advanced section in this step and edit it before clicking Verify.
3. Generate and enter the code
On the Hub computer, open Fuze Store Hub → Settings → Network. Find the Pair the browser card and click Generate code. An 8-digit code appears with a 5-minute countdown.

Back in the browser, you have two ways to bring the code over:
- Type it — read the 8 digits off the Hub and type them into the wizard.
- Scan the QR — click Scan QR code in the wizard, allow camera access, and point the camera at the QR shown beside the code in the Hub. The wizard reads the code automatically.
Either way, the wizard submits the code and exchanges it for a 30-day session token. The token is saved to your store preferences so it survives a tab refresh.
4. You're paired
The wizard lands on a This browser is paired screen. Printing, kitchen display, and customer display now work from the browser tab. Click Save at the bottom of Preferences to persist the change.
If you ever want to pair a different browser or revoke this one, click Disconnect in the wizard. To rotate without losing settings, click Re-pair — it walks you through the same flow with a new code.
What's actually stored?
| Where | What | How long |
|---|---|---|
| Browser preferences (cloud) | 32-byte hex session token | 30 days, then you re-pair |
| Fuze Store Hub on this computer | Hash of the same token + paired-at timestamp | Until you click Disconnect or Revoke all in Hub Settings |
The 8-digit pairing code itself is single-use and expires after 5 minutes — even if you typed it into the wizard, it can't be replayed.
Common errors
Click Open trust page and accept the Chrome warning, then click Verify again. If the trust tab shows a totally different error (DNS, refused), check that Fuze Store Hub is running.
Open the Fuze Store Hub app from your dock or system tray. Wait a few seconds for the bridge to start, then click Verify again.
Codes expire after 5 minutes and are single-use. Generate a fresh one in Hub → Settings → Network and try again.
Wait one minute and try again. The Hub limits failed pairing attempts to slow brute-force guesses.
Check the camera permission in the browser address bar (the small lock icon). You can always type the code in by hand instead.
Revoking a paired browser
In Hub → Settings → Network → Pair the browser, the card shows the count of active sessions. Click Revoke (N) to invalidate every paired browser at once. They'll fall back to the wizard the next time they try a Hub call.