Certification - Kiosk

This page provides all relevant information required during the certification process.

Certification Prerequisites

1. Vendor technical contact to assist with setup and troubleshooting of the POS system

2. Feature set supported including different types of redemptions as mentioned in the SOW

3. Working system with a printer and scanner, etc., sent to the Punchh office in Austin, Texas

Punchh, Inc.
Attention: Scott Morgan,
1645 E 6th Street STE 250,
Austin, TX 78702

Note: If the POS cannot be provided for certification, remote access to the POS must be provided. The remote access option will slow down the process. Someone still needs to be available at the POS to assist with access to check images or with any steps that cannot be performed remotely.

4. Kiosk setup instructions

5. Business contact at Punchh

6. Instructions on how to access logs and enable Punchh while testing

7. Documentation for the implementation featuring the key items mentioned below

- List of Punchh functionality integrated
- Detailed information about how to access Punchh functionality
- Log location
- How to enable Punchh (entering location key and API endpoints)
- Mentions about UI configuration to enable Punchh integration
- Data mapping with Punchh parameters
- Flow diagram with steps of the implementation, including UI if possible

8. User credentials

9. For remote access (if applicable)

- OS (In some cases, Windows Admin access may be required)
- POS dashboard credentials to access back-end configurations

10. Escalation points

- Business contact (project manager, etc.)
- Technical contact (developer or QA tester) to report bugs
- Punchh implementation manager assigned to the project

Important Information

1. A list of test cases will be available for testing your implementation after it is dev ready.

2. During certification, there would be a QA tester aligned, and only when the implementation is verified with no open issues, you can request production keys from account managers for the business.

Best Practice in Case of User Look-up via Kiosk

Punchh currently recommends look-up via QR code on the kiosk to avoid any fraudulent activities. If a client is interested in supporting phone number look-up on the kiosk as well, considering the risk that fraudulent users might use random phone numbers to redeem offers since no verification is currently done to validate the actual user at the kiosk, then the client can go ahead and allow phone number look-up. This would require additional development on their end, but in that case it would remain uncertified since, as a best practice, Punchh does not recommend phone number look-up on kiosks.