Square

Use completed Square payments to reward customers who have already joined a Perkstar programme. With optional Wallet-card identification enabled, staff open Review sale → Add customer → scan icon and scan the customer’s Perkstar Wallet QR code. Square attaches the safely matched or consent-created customer before payment, and Perkstar applies the routed programme’s earning rule and updates their Wallet pass.

​

System boundaries

Perkstar is the loyalty system of record. Square supplies merchant, location, completed-payment, refund and attached-customer signals. If the business enables customer identification, current customer consent gates every Square search, link and reference publication. For a consenting customer, Perkstar may exact-match an existing Square Customer, create one from their name and contact details only if no match exists, and put that member’s stable Wallet scan value in an otherwise empty Square Customer reference_id. Rewards are still redeemed with the Perkstar pass and scanner, then staff apply the corresponding item or discount in Square. Square Loyalty is not required. Perkstar never creates or updates Square payments, loyalty balances or rewards, and it does not request Square Loyalty permissions. Customer write access is used only for the optional identification flow described above.

​

What you need

• A Perkstar Scale plan or another plan that includes POS Connect.
• Owner access or a team role with Edit operations in Perkstar.
• Permission to approve apps for the intended Square production account.
• At least one active, earn-ready Stamp, Points or Cashback programme.
• Customers enrolled in Perkstar before the payment you want to reward.
• For one-scan identification: an individual default programme with a QR code and required First name and Email fields.

​

Data use

For payment earning, Perkstar reads the Square merchant and location profile, completed payments and refunds, and only the customer attached to a payment. Email or phone is used transiently to find an existing Perkstar member. If no member matches, the contact is not retained, enrolled or used for marketing. Optional Wallet-card identification does nothing in Square without current customer consent. For a consenting customer, it performs complete exact searches by the stable scan reference, email and, when available, phone. If the searches resolve to one Square Customer, Perkstar links that profile. If none resolves, Perkstar may create a Square Customer from first name, optional surname, email and optional phone. Perkstar writes the stable Wallet scan value only when reference_id is empty, never overwrites a value owned by the merchant or another system, and releases only a value for which it has durable ownership evidence. After a successful match, Perkstar stores an opaque Square customer link scoped to that merchant and connection. It also stores encrypted OAuth credentials, card and location routing, and the operational and loyalty records required to deduplicate earning and reconcile refunds. See Set up Square for the permissions and test procedure.