After identifying the guest via user look-up and completing check-in, call the Possible Redemptions API to retrieve the list of active offers and rewards available to the user for the current order.
Present available redemptions to the cashier or surface them in a self-service flow; the guest selects the reward they wish to apply.
Call the Create Redemption API with the selected offer ID and current order details; Punchh validates the redemption against the order and returns the discount amount to apply.
Apply the discount to the POS order and confirm the transaction; then call the Finalize or Settle redemption endpoint to commit the redemption so it cannot be reused.
If the transaction is voided, call the corresponding redemption void or cancel API to return the reward to the guest's account.
Log the redemption ID and order reference for reconciliation and dispute resolution.
Known gotchas
Redemptions must be finalized after the order is settled; abandoning an in-progress redemption without finalizing or voiding it can leave the reward in a locked state on the guest's account.
The Punchh Redemptions 2.0 flow (Access Code approach) differs from the legacy flow — consult the developer portal to confirm which flow your integration should implement based on your account configuration.
Punchh offer eligibility rules (minimum order size, excluded items, day-of-week restrictions) are evaluated server-side; always rely on the Possible Redemptions API response rather than caching eligibility logic client-side.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp