Loyalty rewards app built on SumUp transactions
How a loyalty rewards app connects to SumUp for points on card sales, with checks for refunds, duplicates and reconciliation.
Updated 2026-11-07
Loyalty rewards app with SumUp
A loyalty rewards app for a business that takes its payments through SumUp starts with a practical question: which transactions should earn a reward? A card reader at a café or salon counter records every sale, but it does not know whether the buyer is a regular. The app has to bridge that gap. Usually that means linking a customer's digital card to a sale through a phone number, an email address or a loyalty card the customer scans at checkout, then letting the rules you set convert completed sales into points. Refunds, voided sales and staff test transactions should never earn anything, so those cases need explicit handling from the start. Because SumUp keeps its own record of takings, the loyalty app should treat that record as the reference and avoid building a second ledger of money. Starting from transactions that are already settled keeps reconciliation simple when the owner checks the books at month end.
How it works
Decide which SumUp records earn points. Completed card sales can count, while refunds, voided sales and staff test transactions should be excluded by rule.
Pull transaction records through a dashboard export or SumUp's developer API, and check the columns against a sample before the feed is trusted.
Link each sale to a customer through a phone number, email or scanned card, since a card payment alone does not identify the person who paid.
Apply the reward rules once per transaction ID, so a repeated import never adds points twice.
Leave refunds and disputes to SumUp's own tools, and have the owner approve any point reversal before it posts to a customer's balance.
Keep card numbers and personal details out of logs and out of any model that reads the records, then test redemptions at the counter with staff.
Frequently asked questions
- What should I back up in SumUp first?
- Export a full set of SumUp transaction records for a period you can check by hand, and store it with the date it was pulled. Save the current reward rules and customer balances too, so a change can be reversed. Keep card numbers and personal details out of every backup. If you use the API, note the scopes and account settings as well, so a rebuild can reproduce the results.
- How does a loyalty rewards app connect to SumUp?
- The usual route is a feed. The app pulls completed transaction records from SumUp, either from scheduled dashboard exports or through SumUp's developer API where your account has access. Each record carries an identifier, which stops a sale earning points twice. The app matches records to customers through a phone number, email or scanned card. It never takes payments itself.
- Do I need a developer to connect a loyalty rewards app to SumUp?
- A file-based setup needs someone comfortable with spreadsheets and exports, though the rules and customer records still need careful building. A live connection through SumUp's API usually needs a developer who can handle authentication and keep the link working when interfaces change. Either way, agree the scope first, and check that it covers refunds, duplicate records and where the data is stored.
- How does a loyalty rewards app stay in step with SumUp?
- It stays in step by reading SumUp's records on a regular schedule rather than trusting a one-off copy. Each run compares new transactions with those already processed, so sales are added once and corrections are picked up. When SumUp's export columns or API fields change, the import should fail loudly rather than quietly skipping data. Someone should look at the import log after each run and check a sample against the dashboard totals.
- How do I know a loyalty rewards app works with SumUp?
- Test with a small set of real transactions before any customer sees the app. Make one purchase, one refund and one voided sale, then confirm that only the purchase adds points. Compare the app's totals with SumUp's dashboard for the same window. Check that a repeat sale is recorded as a new event. Any mismatch should be explained before launch.
Related
read these nextUp a level
More with SumUp
- Ordering app with SumUp: how the build works
- Payments reconciliation integration for SumUp
- Review request automation with SumUp for beauty and hair salons
- AI adoption for SumUp businesses: training around the tools you already pay for
- AI strategy for SumUp businesses
- Custom development for SumUp: bespoke tools built around your takings records
- Product idea for SumUp businesses: test a new service before the build
- Workflow automation for SumUp businesses
Loyalty rewards app with other software in the same category
- Loyalty rewards app for Epos Now, built around your till data
- Loyalty Rewards App for Kounta Point-of-Sale Businesses
- Loyalty rewards app built on Lightspeed sales data
- Loyalty rewards app for Lightspeed Retail (X-Series) businesses
- Loyalty Rewards App for Mr Yum Point of Sale Venues
- Loyalty rewards app built on Square for repeat customers
- Loyalty rewards app for Zettle point-of-sale businesses
