Rewards Search Platform
The complete web layer for a paid-to-search earnings product, built for trust-first conversion

This is a consumer product with an unusual pitch: members install a desktop program that automatically performs web searches for partner websites, accrue per-search earnings, and cash out via PayPal or crypto. We delivered its entire web presence, a conversion-focused marketing site and an authenticated member dashboard, as one Next.js application consuming the product's REST API.
The application is a clean client of the operator's API. All business logic, earnings calculation, payout approval, API-key issuance, stays server-side; our web layer handles presentation, validation, session handling, and error states, and supports the operator's controlled beta rollout, where access was application-gated and the program download staged behind API-key issuance.
Development ran from November 2024 to February 2025 with a two-developer, pull-request-based workflow.
When trust is the conversion barrier
The product asks something unusual of its users: install software on your personal computer and let it run searches on your behalf. That makes trust the central design problem. The website had to explain a novel earning mechanism clearly, answer safety objections head-on, is it a virus, what data does it collect, will it slow my machine down, and convert visitors into applicants while the operator kept beta access controlled.
On the member side, the product needed a dashboard where users could watch their balance grow, track referrals, and request payouts to PayPal or a crypto wallet, with every screen backed by the operator's API and gated behind verified accounts.

Layered gates, one data layer, objection-first marketing
We built access control in two tiers: Next.js middleware blocks all dashboard routes for visitors without a session token, and a second gate inside the dashboard layout checks the profile's email-verification flag and redirects unverified users into the OTP flow. Every earning and payout screen inherits both protections with no per-page code.
Dashboard state, balance, earnings, referrals, payout history, API key, verification status, lives in a single Redux Toolkit slice with async thunks per API resource, so multiple screens share one consistent source of truth and one error-handling path.
The home page is sequenced as an objection-handling funnel: how it works, registration call-to-action, testimonials, a general FAQ, and a second, dedicated safety FAQ covering data privacy, malware concerns, bandwidth usage, and ad-personalization effects, followed by a contact form and an always-available live chat widget.

From skeptical visitor to verified, earning member
Registration collects name, email, and password with inline validation and required terms acceptance, then immediately pushes the new user into email OTP verification before any dashboard access. Login, logout, forgot-password, and reset-password flows all run against the API, with the session held in a cookie and cleared automatically when the API reports a server-side session problem.
Inside the sidebar-navigated dashboard, members get a Get Started guide, a balance overview with referral and payout tables, profile management, and a dedicated earnings view separating total earnings from referral commission. Payout requests accept either a PayPal email or a BTC wallet address, the form enforces exactly one method, validates wallet format, and surfaces field-level API errors onto the right inputs. Requests are created as operator-reviewed tickets with Pending, Approved, and Rejected statuses visible in a full payout history.
Every member gets a shareable referral link. When a visitor arrives with a referral parameter, the app stores the attribution locally, cleans the URL, and attaches the referrer to the eventual registration payload, so attribution survives browsing across pages before sign-up. For the gated beta, the dashboard includes an API-key validation screen with a path to the external application form, and a Downloads page that surfaces the member's key once issued.
OTP-verified onboarding
Registration with inline validation and required terms acceptance flows straight into six-digit email OTP verification, so no account reaches the dashboard unverified.
Member earnings dashboard
Balance overview, referral and payout tables, profile management, and an earnings view separating total earnings from referral commission, with dates, currency, and statuses formatted consistently across screens.
PayPal and crypto payout requests
Members submit a PayPal email or BTC wallet address, exactly one, format-validated, creating operator-reviewed tickets tracked through Pending, Approved, and Rejected statuses.
Durable referral attribution
Referral parameters are captured on any page, persisted locally, and attached at registration, so a referred visitor can browse freely and still credit their referrer when they sign up.
API-key gated beta access
An API-key validation screen and Downloads page support the operator's controlled rollout, routing users without a key to the beta application form.
Trust-first marketing funnel
Product explainer, testimonials, and dual FAQs, including a dedicated safety FAQ on data privacy, malware scanning, and bandwidth, backed by a contact pipeline and site-wide live chat.


- 01
Middleware plus layout double gate
Edge route protection on token presence combined with a data-driven email-verification check in the dashboard layout, so every protected screen inherits both gates without per-page code.
- 02
Single typed data layer
One Redux Toolkit slice with async thunks per API resource and typed dispatch and selector hooks, letting Dashboard, Payouts, and Referrals screens compose the same data without duplicating fetch or error logic.
- 03
Hardened API client and sessions
A single axios wrapper attaches the bearer token from a 7-day session cookie, normalizes error shapes, and forces logout on invalid sessions, while server-side Next API routes proxy login and registration and set the cookie on the response.
- 04
Field-level API error mapping
Payout, registration, and account forms parse the API's error arrays and attach messages to the specific offending field, keeping server-side validation authoritative while preserving clean form UX.
- 05
Design-system frontend
Tailwind CSS with a shared style helper module, Flowbite and Headless UI primitives, self-hosted Clash Display and Geist typefaces, and SVG icons compiled to components via SVGR.
- Delivered the product's complete web presence, from visitor education and beta application through verified onboarding, earnings tracking, and payout requests.
- Every account passes email OTP verification before reaching any earning or payout screen.
- Referral attribution reliably survives the gap between first visit and eventual registration.
- The frontend supported the operator's gated beta rollout through API-key validation, without exposing the download prematurely.