Key Features
The key features of Punchh x Lunchbox integration are: Single Sign-On (SSO), Earning Rewards, Rewards Redemption, Payments, and Delivery
Single Sign-On (SSO)
Lunchbox’s integration with Punchh SSO allows customers to use a single set of credentials to access both systems, eliminating the need to maintain multiple accounts. Here's how it works:
When a user signs up or logs in through Lunchbox ordering platforms, their record is simultaneously created in Punchh (and vice versa)
Upon login, Lunchbox sends the credentials to Punchh. If valid, Punchh returns a token.
This token:
Authenticates the user
Enables Lunchbox to access wallet and reward data
Remains valid for ~2 weeks and refreshes automatically two days before expiration or upon a new login session
IMPORTANT NOTE: There is no visible indication on the ordering platforms that the login is managed via Punchh. Also, the user experience remains fully native to Lunchbox.
Earning Rewards
Registered users can earn Punchh loyalty points when logged in and placing an order through any Lunchbox ordering platform (web or app) with the client who uses Punchh.
When a user completes a loyalty transaction (order status must be "Complete"), Lunchbox sends Punchh the following details about the transaction:
Customer Information - Fetch Account Balance of User
Product Mix - The assortment of different items the guest purchased.
Subtotal - The total cost of selected items.
Service Charges - Additional fees applied to cover services.
Tender - Form of payment accepted by the merchant.
Lunchbox will update Punchh if any changes are made to the transaction (i.e order modifications, cancellations, etc)
Rewards Redemption
When a signed-in user places an order, they can apply the following Punchh offers:
Coupon codes - One-time discounts for specific purchases
Promo codes - Campaign-specific offers (e.g., tied to a holiday or event)
Banked Points - Earned over time and stored until a perk is claimed
Rewards - Earned though moving to next level tiers or points conversion
IMPORTANT NOTE: Lunchbox allows stacking multiple offers per order or item. If an order is canceled, offers are returned to the guest’s Punchh account.
Payments and Delivery
As mentioned above, the user experience remains fully native to Lunchbox:
The Punchh integration allows users registered with Punchh or also users registered via chain's ordering platform to securely save and store their credit card information for future transactions.
When placing an order, user can choose between immediate (ASAP) or specify a desired time for order-ahead scenarios.
Additionally, our integration supports dispatch, delivery, and curbside pickup options.
Users can also choose to use the following payment options:
Apple Pay
Apple Wallet
E-gift cards
Physical gift cards
Onboarding Kick-off
To enable Punchh SSO and loyalty on Lunchbox ordering, we must reach out to the Punchh team.
Here's how the communication should flow:
CX team memeber confirms Punchh is the target loyalty provider for the chain and identifies all live and near-term locations that need SSO enabled
After confirmation, CX team memeber creates the spreadsheet containing Location Name, Store ID, Web Location URL for each participating stores. When ready, Lunchbox sends the CSV to Punchh for SSO URL mapping and requests client ID and secret key for the chain
Punchh then returns chain credentials: client ID and secret key
CX team member then need to submit an ENG change request to add the Punchh chain credentials to Lunchbox config. No per-location config in Lunchbox is required for SSO routing once Punchh has mapped the provided URLs on their side
Once configured, proceed with QA user creation, login, ordering, and loyalty earn/redeem validations
User Flow Summary
User signs up or logs in → Punchh returns token via SSO
Token triggers menu and loyalty wallet sync
User browses menu → Lunchbox checks Punchh for reward-eligible items
User adds items to cart → Reward suggestions are shown if available
If applicable, user redeems a reward or claim a perk on the cart page
User places an order
Order status is "Complete"
Loyalty data is sent to Punchh
After the transaction, the loyalty account is updated:
If a reward or perk was used, it's removed from the user's Punchh account
If not, the user earns points, which are then added to their loyalty balance
FAQ
Q: Do apps use the same deep links as web for SSO routing?
A: No. SSO redirect mapping uses web location URLs that Punchh configures. Apps do not use these web deep links. Validate any separate in-app deep linking as needed.
Q: Are Punchh credentials per location or per chain?
A: Per chain. Punchh provides a chain-level client ID and secret key that Lunchbox configures once. Location URLs are still required for Punchh’s SSO mapping.