Skip to main content
Controlled rollout. Reviewed 13 September 2026. The status shown in the intended business’s dashboard is authoritative for that account.
Use the Clover app for scan-first customer identification, loyalty earning, redemption and refund recovery. Access requires explicit release approval and the required provider configuration; an eligible subscription alone does not enable it.

​
What to do now

Open Perkstar → Integrations and inspect Clover. If it says Coming soon or Unavailable, do not use an old setup URL or grant provider credentials to work around it. Documentation and a provider’s developer portal do not themselves grant access to a Perkstar connector. If you already have an approved connection, use My integrations → Manage where available. Keep the original provider account and transaction references when asking support about a failure. Do not disconnect a working installation merely to test whether you can reconnect it.

​
Discuss compatibility with support

Provide the business account number, provider product/version, country, relevant store or location, and the loyalty workflow you need. Do not share passwords, API keys or customer lists. Ask support to confirm both access and an appropriate controlled test before relying on this connection for customer transactions. For a bespoke connection, start with the POS guide and API availability. A custom integration is a separate implementation, not a way to enable an unreleased native connector.