Certification - Online Ordering

Punchh has a process for integrating partners with the Punchh loyalty platform. For necessary API keys, as well as additional setup or integration information, reach out to your Punchh representative.

Punchh has a comprehensive set of APIs that allow our ordering partners to build integrated solutions for their users. Users can sign up and log in using their Punchh credentials, earn points on their orders, and redeem their rewards and offers while ordering online on via a website or a mobile app.

Online Ordering Implementation Phases

• Phase 1: A partner uses Punchh APIs to integrate with Punchh. After this phase is done, users can order online on a website or on webview in an app (without having to log in twice -- one for the app and then for ordering) and interact with their loyalty account to see loyalty status, earning points and redemptions of rewards and offers.
• Phase 2: Punchh uses the partner’s mobile APIs to build a native ordering experience on the mobile app.

Certification Process

Punchh has a certification process during which Punchh certifies the integration done by the partner. It generally takes 3-6 weeks for Punchh to certify the integration. Issues found will be fixed by the partner, and once all issues are fixed, the solution will be certified. A list of standard features for ordering integration levels will be available for certification testing.

Requesting Business

Punchh needs the integration details for a requesting business and its timelines for implementation. If a specific timeline is not available, we at least need an estimate of when the integration will need to be implemented.

High-level Features

• User management: Ability of a user to create a new account and log in with the existing account. Punchh will be the master for user management (sign-up/login, etc.).

• Check-in: Earning points for a user

• Redemptions: Redeeming offers and rewards that a user has earned as a result of participation in a loyalty program or via campaigns. The partner should implement support for all types of program structures, as some redemption types are specific to certain program structures.

• Fetch balance: At any point, fetching a user’s loyalty balance and available offers/rewards

• Void check-in and redemptions: Voiding check-ins and redemptions of orders that are cancelled

• User access token: Ability of partners to accept a Punchh user’s access token to make further API calls to Punchh (specific to native ordering flow)