This error is often seen when OLO triggers an instance commonly linked to a security issue from a SSO (single sign on call).
If a guest is receiving this error, you'll want to follow common troubleshooting steps to address the application first. The following article is a great starting point:
If the error persists beyond completing common troubleshooting steps for the application, then the next step is to contact OLO so they can investigate specifics of the interaction.
In an effort to supply information as quickly as possible, this article has been published prior to a formal technical review, and is subject to factual, grammatical, and various structural errors. Data may be incomplete, misordered, or incorrect.
This additional disclaimer will be removed upon formal review of this article. The standard Punchh Inc. KB Disclaimer still applies, and can be found at: https://support.punchh.com/hc/en-us/articles/360040100273-Punchh-Inc-Knowledge-Base-Disclaimer
If further assistance is required, submit a ticket to Punchh Support. (For help submitting a ticket, click here)