Enroll a new guest and perform a check-in for loyalty points via the Punchh POS API
domain: developers.partech.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate your POS integration using the credentials provided through the PAR Technology developer portal after completing the POS API certification process.
At transaction time, look up the guest using an identifier such as email address or phone number via the user look-up API call to determine if they already have a Punchh account.
If no account exists and the guest consents, create a new user record via the Create User API with the required profile fields.
Create a check-in for the identified user tied to the current order to earn loyalty points; include the order total and relevant transaction identifiers.
Confirm the check-in response from Punchh indicates success before completing the POS transaction; surface any errors to the cashier for manual resolution.
After check-in, optionally query the user's current point balance to display it on the receipt or POS screen.
Known gotchas
Punchh's POS API requires formal certification before production use; the developer portal includes a multi-module certification tutorial that must be completed — do not skip certification steps even if the API calls work in sandbox.
Guest enrollment at POS requires the user to be registered with the specific business in Punchh's system, not just any Punchh account; cross-brand enrollment is not automatic.
The check-in and redemption flows are separate API calls; a check-in earns points but does not apply discounts — handle redemption as a distinct step if the guest wants to use rewards on the current order.
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?