01
Customer
Submit the claim
Reason, description, up to 3 photos and 1 video.
Project Handover · 21 October 2026
Platform Handover
Begin the handoverChapter I · Overview & Status
Paylesa Digital Market Place is Nigeria's gamified marketplace — every purchase can become a Pay Less win. Delivered, live and handed over to its owner.
Platform status
Six production surfaces, all serving over secure HTTPS.
| Surface | Address | Check | Status |
|---|---|---|---|
| Web storefront | paylesa.com | Serving | Live |
| Super Admin Control Center | control-center.paylesa.com | Serving | Live |
| Staff Portal | portal.paylesa.com | Serving | Live |
| Core API | api.paylesa.com | Health OK | Live |
| Communications engine | Internal service | Health OK | Live |
| Android app com.paylesa.marketplace | Google Play · v1.0.6 | iOS build ready | Live |
Production is live behind an early-access gate (7-digit invite codes; vendors skip the gate) while launch preparations finish. Secure HTTPS on every address, valid and auto-renewing.
A note from Profynix
Dear Mr Nelson,
Paylesa is now a complete ecosystem: a customer and vendor mobile app, a web marketplace, an executive Control Center, a staff portal, a server-authoritative game engine and a double-entry financial backbone, with logistics, returns, governance and communications built in around them.
This site is your reference for what was built, how each part works, what you own, and how the platform is operated from here. Ownership of the code repository and every third-party account now sits with Paylesa. Profynix Technology continues to host, monitor and deploy the platform for you.
Thank you for the trust you placed in our team. It has been a privilege to build Paylesa with you.
The platform at a glance
Customers, vendors, KYC, staff, logistics, support and risk.
Executive Control Center
Nine pillars and their modules, exactly as built.
Executive Control Center
Screens shown are from the Paylesa development environment with sample data; production is live and pre-launch.
Chapter II · Commerce
Verified stores, a curated catalogue and a direct, cart-free purchase flow.
The storefront
Eight of the 93 web storefront pages. Click any screen to enlarge.
Two ways to buy
Example Buy Now order. The vendor's share is held until delivery plus the return window.
Catalogue management · Control Center
Orders & fulfilment
The vendor taps Process & Ship; a waybill is generated automatically with Speedaf or GIG Logistics. The vendor drops the parcel at a terminal; final weighing and billing happen at the Lagos hub, charged to the Paylesa logistics wallet.
Stays pending through delivery plus a 24-hour return window.
SLA jobs remind, escalate and auto-cancel overdue orders: a vendor not shipping within 4 days, or a failed delivery.
Returns, refunds & Resolution Center
Resolution Center flow
01
Customer
Reason, description, up to 3 photos and 1 video.
02
Vendor · 3 days
Within 3 days, or the case is marked SLA breached.
03
Paylesa
The return is approved or declined.
04
Customer · 24 hours
Within 24 hours, with the return waybill.
05
Vendor · 24 hours
Within 24 hours; auto-confirmed otherwise.
06
Refund
Approved amount minus the ₦10,000 return shipping fee.
07
Closed
The full timeline stays on record.
Chapter III · Gaming — Distribution System
Discounts are funded only by real money in the General Purchased Spin Bank, and the server decides every outcome.
How a spin flows
01
Buy
A verified payment credits the spin balance exactly once, through the payment webhook with a recovery path.
02
Choose
Then start a game session.
03
Each spin
04
Room
The product's Paylesa price places the player in a price-range room — a prize-slot window.
05
Spin start
One spin is consumed atomically, the pending spin is created with server proof, the room's recognised potential winner is recalculated, and the room is claimed atomically if the spinner is recognised.
06
Result
The selected large discount if the room is funded and claimed; otherwise a consolation discount of 10% or 15%.
07
Checkout window
Held for its checkout countdown (default 10 minutes, set in the Control Center). Checkout, discard or expiry resolves it.
Distribution cycles
The engine opens a cycle, draws a target profit (or uses an operator pin) and opens five prize-slot windows: one room per price band, one winner per room per cycle.
A single countdown runs, its duration drawn from a configured range (for example 30–6,000 seconds). When it ends, unclaimed slot reservations return to the Spin Bank and a new cycle starts.
If the bank cannot fund the target, the windows still open but no money moves, and wins downgrade to consolation.
Control Center controls
Chapter IV · The Algorithm
The rules the game engine follows on every spin, every cycle and every checkout.
1 · Spin records & winner recognition
Lifetime. Never resets.
Every spin the player has ever made.
The only basis for selection.
Losses and consolations since the player's last big win. Resets to zero after a win.
Room members are ranked by highest Win Spin Record, then earliest eligible session. The top-ranked member is the recognised potential winner.
A player with a higher record who enters before the recognised player spins takes over recognition.
The win happens only when the recognised player spins while still on top. One player alone in a room wins on their spin.
A winner holds the slot — nobody else can enter — and is excluded from all other rooms for the rest of the cycle.
2 · Target-profit split
| Target | Paylesa 50% | Slot 1 | Slot 2 | Slot 3 | Slot 4 | Slot 5 |
|---|---|---|---|---|---|---|
| ₦1,000,000 | ₦500,000 | ₦80,000 ₦65k–80k | ₦90,000 ₦65k–90k | ₦100,000 ₦65k–100k | ₦110,000 ₦90k–110k | ₦120,000 ₦100k–120k |
| ₦2,000,000 | ₦1,000,000 | ₦100,000 ₦65k–100k | ₦100,000 ₦65k–100k | ₦100,000 ₦65k–100k | ₦300,000 ₦100k–300k | ₦400,000 ₦300k–400k |
| ₦3,000,000 | ₦1,500,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦200,000 ₦100k–200k | ₦400,000 ₦200k–400k | ₦600,000 ₦400k–600k |
| ₦4,000,000 | ₦2,000,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦1,000,000 ₦500k–1M |
| ₦5,000,000 | ₦2,500,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦1,500,000 ₦1M–1.5M |
| ₦6,000,000 | ₦3,000,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦2,000,000 ₦1M–2M |
| ₦7,000,000 | ₦3,500,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦2,500,000 ₦1M–2.5M |
| ₦8,000,000 | ₦4,000,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦3,000,000 ₦1M–3M |
| ₦9,000,000 | ₦4,500,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦3,500,000 ₦1M–3.5M |
| ₦10,000,000 | ₦5,000,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦4,000,000 ₦1M–4M |
| ₦12,000,000 | ₦6,000,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦5,000,000 ₦1M–5M |
| ₦15,000,000 | ₦7,500,000 | ₦100,000 ₦65k–100k | ₦200,000 ₦100k–200k | ₦300,000 ₦200k–300k | ₦400,000 ₦300k–400k | ₦6,500,000 ₦1M–6.5M |
A product lands in the first slot band that contains its price, in slot order. At every level the five slots add up to the Winners 50%.
3 · Worked example — one won discount
All four movements post together at checkout as one balanced ledger batch.
4 · A win without checkout
On discard or countdown expiry, the discount is forfeited. No profit or vendor credit is created.
The full slot reopens with its complete prize.
The held amount returns to the Spin Bank.
A payment that arrives after expiry is auto-refunded to the original payment method.
5 · Safety guarantees
Chapter V · Financial Ecosystem
A canonical, double-entry ledger view of company, vendor and spin wallets, with governed withdrawals and reconciliation telemetry.
Where company money lands
Credited once per funded cycle. Never refunded.
Slot amount minus vendor price, at winner checkout.
All checkout shipping.
What winners actually paid.
The markup on Buy Now and consolation orders.
The derived sum of the five boxes — a view, not a separate pot.
Paystack Balance is shown alongside: the live provider balance, read-only.
Spin & vendor wallets
| Wallet | What it holds |
|---|---|
| General Purchased Spin Bank | 90% of every spin; funds the cycles. |
| Winners Slots Pool & Winners Slot Amount Two views of one reserve | Unclaimed reservations, and locked wins. |
| Vendor Total Engagement Spin | The vendors' 10% share of spins. |
| Vendor pending release | Order payments held until delivery plus the return window. |
| Customer Refund Balances Liability view | Outstanding refund obligations. |
| Logistics wallet | Pays final shipping charges at the Lagos hub. |
How money leaves — revenue snapshots
A snapshot captures selected boxes — by default all five — into the Snapshot Wallet.
Withdrawals draw only from the snapshot, and must pass governance approval and Paystack.
Voiding a snapshot returns the part that was not withdrawn.
Built-in protections
Chapter VI · People & Operations
Customers, vendors, KYC, staff, logistics, support and risk — each with its own tools.
Four user roles
Workforce
Logistics
Delivery and return shipments are tracked separately, so a return never muddies an order's delivery record.
Each provider can be switched on or off from the Control Center.
Customer support
Tickets, a unified inbox for live chat, WhatsApp and email, and guided chat with an AI first-line assistant that hands off to agents.
Risk management
A risk case opens automatically when a vendor or customer crosses the threshold — by default 5 events a week.
Each case carries a full trail: suspension, appeal and resolution.
Chapter VII · Governance & Communications
Who may do what, who must approve it, and how every customer, vendor and staff member hears about it.
Governance by design
Admins sign in with authenticator (TOTP) 2FA; an IP allow-list is optional.
Communications engine
Transactional messages for orders, payments, spins, returns, refunds, KYC, payouts and security.
Targeted campaigns with audiences.
A log of every message sent and its delivery.
Every email uses the Paylesa templates.
Control Center pages: Overview · Automated messages · Campaigns · Delivery activity · Settings.
Platform control
Versioned, so every change can be traced.
Security settings and connected services.
Invite codes for the pre-launch period.
Terms, privacy, refund, return and vendor terms.
Protected, for controlled resets only.
Chapter VIII · Technology & Handover
The technology map, the repository, hosting, every account, our recommendations and the sign-off.
Technology map
| Surface | Address | Technology |
|---|---|---|
| Storefront | paylesa.com | Next.js 16, React 19 |
| Control Center | control-center.paylesa.com | React + Vite |
| Staff Portal | portal.paylesa.com | React + Vite (staff build) |
| Core API | api.paylesa.com | Node.js 20, Express, MongoDB, Redis/BullMQ jobs, WebSockets |
| Communications | Internal service | Node.js worker + Redis queue |
| Mobile | Google Play iOS build ready | Flutter (20 feature modules) |
Repository guide
Branch main is production. Start with README.md. Configuration values are never stored in the repository.
| Folder | What it holds |
|---|---|
| backend-services/paylesa-api | Core API |
| backend-services/paylesa-communications | Communications engine |
| frontend/web | Web storefront |
| frontend/control-center-vite | Control Center and Staff Portal |
| frontend/mobile-app | Mobile app |
| frontend/landing-vite | Retired pre-launch site |
| shared-libraries | Code shared across services |
| docs | HOW_PAYLESA_WORKS.md (the canonical product guide) and DISTRIBUTION_WORKED_EXAMPLE.md |
| scripts | Business-rule and game-algorithm guard checks |
Hosting & deployments
Dedicated cloud infrastructure in London, with automatic HTTPS.
Every change merged to main runs this pipeline automatically. If any check fails, the deployment rolls back on its own.
The repository transfer does not affect the live platform. To keep automatic deployments, keep the existing deployment webhook and Profynix's read access.
Accounts & ownership
| Account | Used for | Owner | Status |
|---|---|---|---|
| GitHub repository | Source code | Paylesa | Transfer in progress |
| Domain paylesa.com Namecheap | Domain | Paylesa | Owned · renews May 2029 |
| Google Play Console | Android app | chairman@paylesa.com | Transferred |
| Firebase | Sign-in & push | paylesaofficial@gmail.com | Transferred |
| Paystack | Payments & payouts | paylesaofficial@gmail.com | Transferred |
| Cloudinary | Media | paylesaofficial@gmail.com | Transferred |
| Brevo | paylesaofficial@gmail.com | Transferred | |
| Infisical | Configuration vault | paylesaofficial@gmail.com | Transferred |
| Speedaf | Logistics | paylesaofficial@gmail.com | Transferred |
| GIG Logistics | Logistics | paylesaofficial@gmail.com | Transferred |
| Twilio | SMS & WhatsApp | paylesaofficial@gmail.com | Transferred |
Recommendations
| Priority | Owner | Action |
|---|---|---|
| High | Paylesa | Refresh service keys after transfer (Paystack, Firebase, Cloudinary, Brevo, logistics, Twilio). Profynix updates the hosting side. |
| High | Profynix | Add Firebase web settings so storefront Google and phone sign-in work on web (mobile unaffected). |
| Medium | Profynix | Daily off-site backups with alerts. Backups currently run before every deployment. |
| Medium | Profynix | Library security updates flagged by audit. |
| Medium | Paylesa | Confirm the Play Store listing and publish iOS under Paylesa's Apple Developer account. |
| Low | Profynix | Enable bot protection and the logistics status webhook. |
| Low | Profynix | Repository tidy-up (merged branches, older runbook). |
| Low | Profynix | Automated tests for the web storefront and Control Center. |
Acceptance & sign-off
Ticks are saved in this browser.
0 of 8 confirmed
For Paylesa Digital Market Place
Founder & Chairman
For Profynix Technology
Founder & Team Lead
Support & contact
18b Peace Estate, Badore Road, Ajah, Lagos