Punchh Platform Release Notes - 04 March 2026 Deployment
The updates described in these release notes and the affected/linked documentation will not be available in the Punchh platform until the target deployment date.
Segments
Update to No Checkin No Redemption Segment Type
We have resolved an issue where guests were not correctly included in the No Checkin No Redemption segments. Guests are now targeted as expected. (EPS-11146)
Developers Corner
Password Reset Security Enhancement
With this enhancement, password reset calls will automatically invalidate all active sessions and tokens in Punchh. Old tokens and old passwords stop working across API2, AUTH, v1-secure, and Iframe flows. (EPS-7558)
See the following article(s) for more details:
- Online Ordering Change Password (Developer Portal)
Redemptions 1.0 APIs Now Return Per-Item-Level Discounts
We have enhanced the POS Possible Redemptions 1.0 API (POST/api/pos/redemptions/possible) and Create Redemption 1.0 API (POST/api/pos/redemptions), and Create Online Redemption 1.0 API (POST/api/auth/redemptions/online_order) to provide item-level discount details in the redemption response.
Previously, the API returned a single consolidated discount amount for the entire receipt after an offer was applied. With this enhancement, discounts are distributed across each qualifying menu item, making it easier for POS and online ordering systems to display and process discounts accurately. Each discounted item now includes its own applied discount amount (negative value). (OMM-1639, PDOC-3642)
This enables POS and ordering platforms to:
- Show accurate per-item discounts on receipts
- Improve tax calculations and reporting
- Better align the offer presentation with customer expectations
What’s not changing:
- No breaking changes to existing Redemption 1.0 APIs
- Redemption logic and offer eligibility remain unchanged
- Integrations that rely only on the consolidated redemption amount will continue to work as before
See the following article(s) for more details:
- Possible Redemption (POS Redemptions 1.0) (Developer Portal)
- Create Redemption (POS Redemptions 1.0) (Developer Portal)
- Create Online Redemption (Online Ordering Redemptions 1.0) (Developer Portal)
Advanced Authentication APIs – id_token Removed from Verify and Refresh Token Responses
The Advanced Authentication APIs — the Verify Token (POST/api2/password_less/verify) and Refresh Token (POST/api2/password_less/refresh_token) endpoints — no longer return the id_token field in their responses.
This change simplifies the authentication flow by requiring only the access_token as a Bearer token in the Authorization header, removing the need for both id_token and access_token when using Advanced Authentication and prevents unintentionally exposing identity‑related information.
As part of this update, the id-token response header has been removed from the Online Ordering and Mobile API documentation on the Developer Portal to align with the updated API behavior. (INT2-2776, INT2-2744, PDOC-3608)
See the following article(s) for more details:
- Verify Token (Advanced Authentication) (Developer Portal)
- Refresh Token (Advanced Authentication) (Developer Portal)