Premium Early-Access Bidding System

Customer: AI | Published: 16.11.2025
Бюджет: 750 $

I need a pay-walled bidding module that releases every new job on my custom-built platform to paying members a full 24 hours before it appears for everyone else. The site’s stack is a mix of JavaScript front-end components and a Python back-end API, and log-ins already rely on standard email credentials reinforced with two-step verification, so whatever you build has to slide cleanly into that flow without weakening it. Core flow • When a client posts a job, your code should time-stamp it, flag it as “premium,” and expose it only to verified subscribers for the first 24 hours. • At the 24-hour mark the listing flips to public automatically. No manual intervention. • Subscribers need a clear badge or highlight that they are inside the early-access window. • Payment handling (Stripe is my current preference, but I’m open) must recognise recurring subscriptions and instantly elevate the user’s role on the very first successful transaction. Freelancer.com tie-in On every public job I post here, I want a small, eye-catching button that simply says “Secret Jobs Here.” Clicking it redirects users to the pay-wall sign-up screen on my own site. Keep the implementation lightweight: plain HTML/CSS snippet I can paste into a job description or an embeddable image/link that survives Freelancer’s formatting rules. Acceptance criteria – Jobs remain invisible to non-subscribers for exactly 24 hours and then switch automatically. – Existing email + 2-step authentication flow stays intact; no extra log-ins. – Payment confirmation instantly promotes the account and grants early access. – “Secret Jobs Here” button renders correctly on Freelancer.com and routes to the sign-up page. – Clean, well-commented JavaScript/Python code delivered via Git with a short README so I can deploy in one go. If you have direct experience building gated-content or subscription modules with JavaScript/Python, this should be a straightforward build; otherwise please outline any libraries or micro-services you’d lean on.