Card-Linked POS Loyalty Platform
Budget: £250 – £750 GBP
I’m building a lightweight MVP that lets independent cafés run a fully automatic, card-linked loyalty programme without issuing separate cards or apps. The core of the job is a secure backend service that:
• Listens to Square and SumUp webhooks / APIs, fingerprints the payment card (never the full PAN) and recognises returning customers.
• Increments a visit counter and, when a customer hits the reward threshold, instantly triggers the reward logic.
• Fires an SMS through Plivo to let the guest know they’ve just earned, for example, a free coffee.
What I’ll look for in the finished work
1. Clean, well-documented code (language and framework are up to you as long as it’s reliable and easy to maintain).
2. Clear setup instructions a café owner can follow in under 30 minutes to connect their Square or SumUp account.
3. No card data stored anywhere; the solution must respect PCI rules and rely solely on tokenised or hashed identifiers provided by the POS.
4. A minimal but functional database schema that supports multiple cafés so the product can scale later.
5. Optional but appreciated: a simple web dashboard that shows total visits, rewards issued and active customers per café.
Please outline the tech stack you’d use, any similar integrations you’ve handled, and how you would keep the service resilient if one POS webhook goes down. I’m aiming for a straightforward, dependable system I can demo quickly, then expand.
• Listens to Square and SumUp webhooks / APIs, fingerprints the payment card (never the full PAN) and recognises returning customers.
• Increments a visit counter and, when a customer hits the reward threshold, instantly triggers the reward logic.
• Fires an SMS through Plivo to let the guest know they’ve just earned, for example, a free coffee.
What I’ll look for in the finished work
1. Clean, well-documented code (language and framework are up to you as long as it’s reliable and easy to maintain).
2. Clear setup instructions a café owner can follow in under 30 minutes to connect their Square or SumUp account.
3. No card data stored anywhere; the solution must respect PCI rules and rely solely on tokenised or hashed identifiers provided by the POS.
4. A minimal but functional database schema that supports multiple cafés so the product can scale later.
5. Optional but appreciated: a simple web dashboard that shows total visits, rewards issued and active customers per café.
Please outline the tech stack you’d use, any similar integrations you’ve handled, and how you would keep the service resilient if one POS webhook goes down. I’m aiming for a straightforward, dependable system I can demo quickly, then expand.