Integrate a loyalty program with PAR Brink using Discount and Tender configuration since no dedicated loyalty API exists
domain: developers.partech.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm there is no native GetLoyalty/RedeemLoyalty endpoint in Brink — loyalty is not a first-class Brink API resource
Configure a Discount object in the Brink Settings Editor (e.g. a Comp-type, order-granularity discount) to represent loyalty redemption, using flags like 'Must Enter Name'/'Must Enter Amount' to capture redemption details at the POS
Alternatively or additionally configure a Tender type to represent loyalty-funded payment where the integration calls for it
Push these Discount/Tender definitions via the Settings2 service alongside your other menu/settings sync, since they are ordinary settings objects rather than a separate loyalty schema
Coordinate with the loyalty vendor on stacking rules, since some integrations allow only one loyalty-type reward per order while other non-loyalty discounts/coupons can still stack
Known gotchas
There is no Brink-native loyalty endpoint; treat loyalty strictly as a Discount/Tender configuration problem, not an API integration problem
Loyalty-type rewards may have stacking restrictions (e.g. only one loyalty reward per order) that Brink will not necessarily enforce for you
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?