Punchh Platform Release Notes - 30 June 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.

Experiential Loyalty

Digital Collectibles

Digital Collectibles are a new, non-monetary (non-discounted) reward type in the Punchh Platform, such as digital badges and stickers that guests earn through engagement rather than traditional points or discounts. You create and manage collectibles using the new All Collectibles management page in the Punchh Platform, where you can configure each collectible's name, type, image, description, category, and expiry rules. Collectibles are available as reward types across Challenge, Post Redemption, Post Check-in, and Signup. They can be awarded as a standalone item or paired with a redeemable in a collect-and-win configuration. Guests can view their earned collectibles in a dedicated Collectibles tab in the app, and you can target guests based on collectible ownership using new segmentation attributes. (LPE-1707, PDOC-4158, CAM-7292, PDOC-4117)

See the following article(s) for more details:

• Digital Collectibles

Swag Redemption Using Loyalty Points

Swag Management is a new feature in the Punchh Platform that lets you create, manage, and deliver branded physical swag as loyalty rewards, all from a centralized dashboard with global inventory tracking. Using the Swag Management module, you can configure each item's SKU, image, product type, size variants, and fulfillment options, including in-store pick-up or direct shipping, and admins can export a date-range-filtered CSV of shipping details directly from the Redeemed Swag page. Members redeem points for swag they love and receive instant notifications at every step, from unlock to redemption confirmation, with your brand managing fulfillment directly. (LPE-2146, LPE-1987, LPE-1988, PDOC-4109)

See the following article(s) for more details:

• Swag Management

Fraud

Fraud Detection Enhancements

We have expanded the fraud detection module with new rules and automation capabilities. You can now attach automated actions, such as banning or deactivating a guest, directly to fraud rules, so the system responds to suspicious behavior without manual intervention. Five new detection rules are also available, covering patterns like high-frequency check-ins, abnormal points earning, and blocked email domains. Additional enhancements include the ability to force-redeem a guest's points on ban or deactivation, block linked device IDs when banning an account, and automatically invalidate referral codes for banned or deactivated members. (LPE-2115, LPE-1961, LPE-1971, PDOC-4116)

See the following article(s) for more details:

• Fraud Detection Rules

Bulk Actions Now Available for Guest Account Management

Admins can now ban, deactivate, reactivate, or unban guest profiles in bulk; no more doing it one by one! Just upload a CSV, choose what you want to do, and the platform handles the rest while you get on with your day. When it's done, a results CSV lands straight in your inbox so you always know exactly what was processed. You can now choose to force expire all available points as part of the same action. Whether you're tackling fraud or doing a large-scale clean-up, this makes the whole process a whole lot faster. (LPE-2116, LPE-1960, LPE-2033, PDOC-4116)

See the following article(s) for more details:

• Security and Sign In

Campaigns

Message-only Split Testing Now Available

You can now run split tests on mass notification campaigns to compare messaging variants; no gift type is necessary. This allows you to test and optimize things like push and rich notification copy, email subject lines, body content, and calls‑to‑action, all within a single campaign. This added flexibility makes it easier to understand what messaging resonates most with your audience, especially for informational or announcement‑based campaigns where a gift is not needed. Note: Split testing is not supported for mass notification campaigns that include a coupon gift type. (CAM-7265, PDOC-3821)

See the following article(s) for more details:

• Campaign Split Testing

Customize Push Notifications for Google Loyalty Passes

You can now customize the push notification message guests receive when a reward is added to their Google Loyalty Pass. Previously, all Google Wallet reward notifications used a standard, hardcoded message regardless of your brand settings. Now, the platform will use the Reward Field Message you configure in your Google Loyalty Pass Settings — giving you more control over how your brand communicates reward updates to guests. If no custom message has been configured, the platform will continue using the existing default notification text automatically. Apple Wallet behavior is not affected by this update.

See the following article(s) for more details:

• Google Passes

Consumer Experience

Themes Editor Supports Collectibles in Mobile Navigation

The Themes Editor now supports Digital Collectibles for brands that have collectibles enabled. Brands can add a Collectibles section to the bottom navigation of their mobile app directly from the Themes Editor. (CX-3012)

Themes Editor Supports a Second Online Ordering Provider

Brands that route orders by type — for example, Catering — can now configure a second online ordering provider in the Themes Editor. A separate ordering button for that provider can be displayed within the mobile app. (CX-3024, CX-3032)

Loyalty

Bulk Member Upload (BMU) Enhancements

We have shipped several updates to the Bulk Member Upload feature found on the Awaiting Migration page to make managing guest records faster and more reliable. (LPE-1923, LPE-1925, PDOC-4118)

• Failure reports are smarter and more actionable. Reports now only appear when there are actual errors, keeping the UI clean on successful uploads. When errors do occur, each failed row includes the original data and a clear description of the issue — so you know exactly what went wrong and where.
• You can now delete BMU records in bulk. A new Bulk BMU Delete tab is available under All Guest Profiles > Awaiting Migration. Upload a CSV of BMU Guest IDs (or provide a CSV URL for larger files), and the system processes deletions in the background. Once complete, a results CSV is sent to your inbox with a full summary of what was deleted and what was not.

See the following article(s) for more details:

• Awaiting Migration

Duplicate QR Code Check-ins No Longer Credited with Points

We have resolved an issue where the same QR code could be scanned multiple times by the same user, incorrectly crediting loyalty points on each submission. Going forward, any attempt to reuse a QR code that has already been checked in will be rejected; only the first valid scan will be credited. (EPS-11571)

Offers

Referral Reward Redemption Limits Now Configurable

This feature will be fully available to brands by July 25th.

You can now configure referral reward redemption limits in the Punchh Platform to reduce referral program abuse and manage loyalty liability. Two controls are available: a frequency limit that restricts how many referral rewards a guest can redeem within a rolling window of up to 30 days, and an annual limit that caps the total number of referral rewards a guest can redeem per calendar year. Note: Redemption counts begin tracking from the date this feature is enabled for your brand; any historical redemptions will not count toward the configured limits.(OMM-2075, PDOC-4078)

See the following article(s) for more details:

• Referrals

New: Net Amount Excluding Function Strategy

A new Net Amount Excluding Function Strategy field is now available in Qualification Criteria when using Net Amount Excluding qualification rules, giving you precise control over how Line Item Selectors are applied to the qualifying purchase calculation. You can choose to exclude all configured items together as a combined exclusion or evaluate each item independently against its own minimum qualifying amount. This update resolves scenarios where offers requiring both custom item exclusions and dynamic lowest-priced item exclusions could not be accurately calculated within the same qualification rule. (OMM-1943, PDOC-4104)

See the following article(s) for more details:

• Qualification Criteria
• How do I use the Net Amount Excluding Function Strategy field when building a Qualification Criteria (QC)?

Platform Integrations

Toast POS SPECIAL_REQUEST Field Bug Resolved

Resolved an issue in the Toast POS integration where enabling MLIDs caused errors on line items containing a SPECIAL_REQUEST field. The integration now correctly handles SPECIAL_REQUEST modifiers without requiring an MLID lookup. (PD-5944)

View and Export Terminally Failed Webhook Events

You can now view, download, and schedule reports of terminally failed events processed via webhooks. This gives your team greater clarity and visibility into integration reliability and failed event history. (INT1-2208, INT1-2250, INT1-2251)

Reporting and Analytics

We have refreshed the former Campaign Type Metrics report in the Punchh Platform to make your data easier to find, understand, and act on. The previous two-tab view (Campaign Type Metrics and Email Analytics) has been redesigned and split out into multiple reports under Marketing Automation:

• The Campaign Type Metrics report has been renamed to the Campaign Summary Report and stands on its own page without the extra tabs.
• The Email Analytics Report now appears as a separate option in the left-side navigation, so you can jump directly into the insights you need.

We have also refreshed the Redemption Report in the Punchh Platform. The previous view has been redesigned and split out into two reports under Offers:

• The Redemption Report has been modified to only show two tabs: Overview and Deal Summary
• A new stand-alone report, the Redeemable Performance Report, has been separated from the Redemption Report to show both a high-level overview and a detailed close-up of how certain redeemables are performing in your program. 

We have also enhanced the UI for all reports to improve readability and make it easier to navigate, filter, and interpret your data. These updates make it faster and simpler to get to the metrics that matter, so your teams can spend less time clicking through reports and more time turning insights into actions. (INT1-2049, PDOC-3871, INT1-2084, PDOC-3873 , INT1-2198, PDOC-3826)

See the following article(s) for more details:

• Campaign Summary Report (formerly Campaign Type Metrics)
• Email Analytics
• Redemption Report
• Redeemable Performance Report

Developers Corner

New API: Update User's Save Points for Swag Settings

A new mobile API endpoint, Update User's Save Points for Swag Settings (PUT /api2/mobile/user_banking_preferences), is now available. In Points Convert to Currency or Points Convert to Rewards loyalty programs, loyalty users earn points on every purchase. By default, these points are automatically converted ("banked") to rewards or currency. However, some loyalty users may prefer to accumulate their points and redeem them for swag instead. This API lets loyalty users manage their "Save Points for Swag" preference from the mobile app. When the "Save Points for Swag" feature is enabled for the brand, loyalty users can opt in or out of the feature and set a points threshold. Points accumulated up to this threshold are reserved for swag, while points earned above it are automatically converted to rewards or currency according to the program rules. (LPE-1993, PDOC-4113)

Added Flag to Program Meta API Response

The Program Meta API (GET /api2/mobile/meta.json) now returns a new boolean flag, enable_save_points_for_swag, indicating whether the brand allows members to save loyalty points for swag redemption. The flag returns 'true' when the 'Allow members to save points for swag redemption' setting is enabled for the brand, and 'false' when the setting is disabled or not configured. Integrators can use this flag to conditionally display swag redemption options in their mobile experiences. 

See the following article(s) for more details:

• Update User's Save Points for Swag Settings (Developer Portal)
• Program Meta API (Developer Portal)

New API: Redeem Swag

A new endpoint, Redeem Swag (POST /api2/mobile/swag_redemptions), allows a user to redeem branded swag items using loyalty points from the mobile app. The endpoint handles the complete redemption flow, including eligibility checks, point deduction, inventory updates, reward creation, and optional shipping detail capture. The request must include swag_id, location_id, and fulfillment_method. When fulfillment_method is HOME_DELIVERY, the shipping_info object is also required and must include the recipient and shipping address details. On success, the endpoint returns a 200 OK response with the confirmation message: "Swag redeemed successfully".  (LPE-1995, PDOC-4112)

See the following article(s) for more details:

• Redeem Swag (Developer Portal)
• Update User's Save Points for Swag Settings (Developer Portal)

New API: Fetch Available User Swag

We have added a new API endpoint, GET /api2/mobile/user_merch, that returns all available swag items for the authenticated user. The request requires an access_token in the request header and a client request parameter. The response returns a paginated list of available swag items, including details such as the item name, image, points cost, availability window, redemption eligibility, and fulfillment method. (LPE-1994, PDOC-4111)

See the following article(s) for more details:

• Redeem Swag (Developer Portal)
• Update User's Save Points for Swag Settings (Developer Portal)
• Fetch Available User's Swag (Developer Portal)

Collectible APIs Now Return a Unique Collectible ID

The Collectible Listing API (GET /api2/mobile/collectibles) and Collectible Details API (GET /api2/mobile/collectibles/{collectible_id}) now return a unique ID for each collectible in the response. This makes it easier to identify and reference individual collectibles in integration workflows and related API calls. (LPE-2129, PDOC-4077)

See the following article(s) for more details:

• List Collectibles (Developer Portal)
• Fetch Collectible Details (Developer Portal)

Registration Date Now Accepts Date-Only Format in Create and Update Business Migration User APIs

The registration_date request parameter in the Create Business Migration User (POST /api2/dashboard/migration_users) and Update Migration User (PATCH /api2/dashboard/migration_users/{ID}) APIs now supports two input formats:

• YYYY-MM-DD (date only)
• YYYY-MM-DDTHH:mm (full ISO 8601 datetime)

Previously, only the full datetime format was accepted. With this update, if only a date is provided without a time component, the system automatically sets the time to 00:00:00 (the start of the day). (LPE-1932, PDOC-3684)

See the following article(s) for more details:

• Create Business Migration User (Developer Portal)
• Update Business Migration User (Developer Portal)

Program Meta API Now Returns PAR Games Integration Status

A new boolean response parameter, enable_pargames_integration, has been added to the Program Meta API (GET /api2/mobile/meta.json). This parameter indicates whether PAR Games integration is enabled for the brand. When set to 'true', the mobile app displays the PAR Games section (for example, in the bottom navigation or More menu). When set to 'false', the Games section is hidden. (CAM-7409, CAM-7300, PDOC-4122)

See the following article(s) for more details:

• Program Meta API (Developer Portal)

Added Support for Device-Level Bans in Ban User API

The Ban User API (POST /api2/dashboard/users/ban) now supports a new optional boolean parameter ('false' by default), ban_all_associated_devices. When set to 'true', banning a user also bans all devices associated with that user. This parameter gives dashboard administrators more granular control over user bans by allowing them to optionally extend a user ban to all associated devices in a single API call. (LPE-1963, PDOC-4066)

See the following article(s) for more details:

• Ban a User (Developer Portal)

Added Benefit and Discount Details to Fetch User Subscription API Response

The responses of the Online Ordering Fetch User Subscription API (GET /api/auth/user_subscriptions) and the Mobile Fetch User Subscription API (GET /api2/mobile/user_subscriptions) now include additional benefit and discount details, providing richer subscription data for integration partners. (CAM-7165, PDOC-4164)

Benefits

• Partners can now retrieve complete benefit and discount details directly from the User Subscription API without needing separate calls, reducing integration complexity.
• The benefit_priority parameter enables partners to understand the order in which benefits are applied, ensuring accurate discount calculations on their end.
• Detailed discount parameters that allow partners to display precise discount availability and usage limits to the web and mobile users.

New Response Parameters

• Benefits: benefit_name, benefit_description, benefit_priority
• Discounts (nested within each benefit): occurrence, gap_units, gap_unit_type, start_time, end_time, threshold_discount, discount_type

Note: These response parameters were introduced in the April 21, 2026, Punchh Platform release and are now documented in this release.

See the following article(s) for more details:

• Online Ordering Fetch Subscription Plans for a User (Developer Portal)
• Mobile Fetch Subscription Plans for a User (Developer Portal)

Multi-Benefit Response Parameters Added to Fetch Active Subscription Plans APIs

The Online Ordering (GET /api/auth/subscriptions) and Mobile (GET /api2/mobile/subscriptions) Fetch Active Subscription Plans API endpoints now return four additional response parameters: purchasable_location_ids, purchasable_tag_ids, multiple_effective_locations_name, and enable_multibenefit. They provide location-specific purchasability details and indicate whether the multi-benefit subscription feature is enabled for the subscription plan. (CAM-7165, PDOC-4168)

Note: These response parameters were introduced in the April 21, 2026, Punchh Platform release and are now documented in this release.

See the following article(s) for more details:

• Online Ordering Fetch Active Purchasable Subscription Plans (Developer Portal)
• Mobile Fetch Active Purchasable Subscription Plans (Developer Portal)

Reminder: Data Type Changes Effective June 30, 2026

As announced in the April 21, 2026 release notes, the following data type changes take effect on June 30, 2026, to support a larger range of numeric values: INT to BIGINT (int64) and Float to Double.

Redemption APIs and Webhooks
The reward_id, redemption_id, and redemption_code_id parameters changed from INT to BIGINT (int64) across POS, Online Ordering Redemptions 1.0 and 2.0 APIs, Mobile Redemptions 1.0 APIs, and applicable Webhooks Manager event payloads.

User Balance and Check-in APIs
The total_credits, loyalty_points, gift_points, and total_lifetime_points parameters changed from Float to Double.

No platform-side or API changes are required. However, if your integration uses smaller numeric data types (for example, Float or Integer) for these parameters, update it to support the larger data types (Double and BIGINT (int64)).

For more information, see the updated API documentation in the Developer Portal (see the links in the April 21, 2026 release notes).