Skip to main content

Brink POS - Loyalty Integration Setup (LB 2.0)

Written by Marija Golubovic

Overview

This article covers Brink POS loyalty integration setup and provides the requested values needed for the integration.

Important: If a previous loyalty provider is setup it will need to be removed in the settings editor under Options/Loyatly, set it to none and publish it.

Stores migrating from 1.0 to 2.0 cannot have this integration enabled. If they do then 1.0 orders will not close.

Configuring the Generic Loyalty Integration

To get to the Loyalty integration page, we must be logged into the partners' PAR Portal.

Example: https://admin3.parpos.com/, this URL changes per client and can be found in 1Password by searching Brink.

Step 1: From the left sidebar, select Configurations> Integrations Portal

Step 2: Click All

Step 3: Find Solutions> Click Loyalty

Step 4: Select Type > Generic

Step 4: Add in the following details

  • Allow PAR Customer Usage: Toggle On

  • Endpoint URL: Generic Brink incoming endpoint, which will be set for all chains that use Brink in-store. The endpoint URL should be... https://api.novadine.com/api/v2/sync_incoming/80e1ea5b-6991-4ccb-83ae-c18fe6f335ed

  • Store ID: This is a URL encoded version of the token set in the Site ID field on the location in Lunchbox. If the storeID contains any special characters (for example: /, =, etc.), they must be replaced with their URL-encoded versions. We can use the following reference for encoding 

    icon
    • Step 4A: Scroll down to Try It Yourself and paste the Store ID in this Field and click Submit

    • Step 4B: Next copy the value in the field not including the text=

    • Step 4C: Paste this value into the Store ID Field.

  • Default Discount: Choose the Lunchbox Loyalty Discount.

Note: For a discount to appear in this drop-down, the Loyalty Checkbox must be enabled on that discount in Brink. Any updates to discounts require a restart of the POS Register application to take effect. In Cabin Coffee's case, the discount appeared the following day after the system's scheduled overnight restart.

  • Enable Payment: Leave unchecked

  • Authentication Type: API Key

  • API Key: This is the unmodified version of the token set in the Site ID field on the location in Lunchbox.

Integration Validation

  • Lookup/Scan, Redeem, Void, Validate pass end-to-end.

  • Idempotent/non-destructive behavior verified (retries, reopened checks, provider/API outage).

  • Capture evidence: order examples (IDs + timestamps), provider logs, screenshots/video if needed.

  • Owner: Lunchbox + Brand POS Support; Support: PAR API Support as needed

Go-live readiness + monitoring

  • Pilot sign-off; rollout plan and contacts confirmed; escalation path agreed.

  • First 48-72h: monitor failures; for escalations, provide location token/name, time window, order examples, provider Brink Event logs, and video.

  • Owner: Lunchbox + Brand POS Support; Support: PAR API Support

Did this answer your question?