Skip to main content

​
Before connecting

  1. Confirm the business account and the provider account or store. Give the connection a recognisable name where supported.
  2. Read the integration’s availability and requirements. A provider account and a paid Perkstar plan do not automatically grant every connector.
  3. Decide who owns the connection and who will respond when it needs attention.
  4. Review the requested access and keep keys and verification tokens private.

​
Verify one result

Use an authorised fixture or controlled test appropriate to the integration. A connected badge proves authorisation or configuration, not that every business event succeeded. Read the reason, timestamp and relevant provider record behind a status. A missing signal is not a healthy signal.

​
Duplicates and recovery

For custom API writes, keep a stable source reference and follow idempotency. Repeat the same controlled request and verify that it does not duplicate loyalty. Follow the provider-specific guide for refunds, cancellations and recovery. Do not run a bulk retry because a summary looks stale; first establish which records were accepted or completed. For webhooks, use the receiver walkthrough. Check the signed payload and delivery status. A redirect is not a successful receiver response.

​
Hand over ownership

Record the responsible business user, provider account, programme/location mapping, last verified result and recovery instructions. Store secrets in the appropriate secure system rather than in this handover. Before revoking access or disconnecting, review pending work and how late delivery reports will be reconciled.