A referral service with explicit reward rules

Deciding when a referral earns a reward

The referral-service brief described a programme with configurable tiers and reward types: cash bonuses, discounts or account credits. Its central business question was what qualifies as a successful referral and when a reward becomes payable. Both the inviting customer and the invited user needed visibility into progress.

Links, dashboards and payment connections

The outlined stack was Next.js, TypeScript and TailwindCSS, backed by Node.js, Express and MariaDB. The plan used unique tokens to identify invitation links and tracking endpoints to record visits, registrations and completed actions. A dashboard would present the referral funnel and reward status, while administrators managed rules, tiers and payout history.

CRM integration connected referral data with customer records. Stripe and PayPal were named as payment options; Twilio and Mailgun as notification options. Analytics integration was intended to make the route from visit to registration to qualifying action visible. The user dashboard covered earned rewards, pending payouts and completed transactions.

Rules that matter before a launch

The original outline included verification of email or phone, duplicate-account checks and review of suspicious activity. An IP address can support a review signal, but cannot alone establish that two accounts represent the same person. Reward accuracy depends on clear conditions, validation and an auditable history of changes.

Deployment and testing were part of the project outline, including tracking correctness and reward automation. The brief does not confirm a production launch or improved conversion.

Explore customer products, CRM connections and API integration contracts, or describe your referral programme.

Referral project outline

The original project outline describes the requirements and planned implementation. It does not establish final deployment, current operation or measured business results.