TECHNOLOGY, OWNERSHIP & FINAL ACCEPTANCE
Architecture, Accounts, Source Code and Completion of the Handover
This final document records how Paylesa is built and run, confirms who owns each account and the source code, and completes the handover. It is signed by both parties in the presence of one witness each.
1. Architecture
| Component | What it does | Address |
|---|
| Paylesa API | Node.js and Express service that runs every business rule and the ledger | api.paylesa.com |
| Game Engine (Pay Less) | Server-authoritative engine inside the API: spins, distribution cycles and the five price-band prize rooms, with every spin stored with proof | Internal |
| The Algorithm | Funds and releases every discount: target profit from 12 levels, the 50/50 Paylesa–winner split and exact settlement | Internal |
| Paylesa Communications | Separate service that sends every email, push, in-app and WhatsApp message | Internal |
| Mobile app | Flutter app for customers and vendors (com.paylesa.marketplace) | Google Play |
| Web storefront | Next.js web app for customers | paylesa.com |
| Control Centre | Super-admin console | control-center.paylesa.com |
| Staff Portal | The same console, built for staff roles | portal.paylesa.com |
| Data | MongoDB Atlas (main database) and Redis 7 (cache, queues, real-time) | Internal |
Integrations: Paystack (payments, transfers and refunds), Speedaf (delivery, live) and GIG Logistics (built in), Firebase (push notifications), Cloudinary (images and media), Brevo (email) and WhatsApp.
2. Hosting & Operations
- Production. Each service runs as a Docker container behind a reverse proxy that handles domains and TLS. Only one production instance runs background automation.
- Releases. Each change is built into versioned images from the source repository and deployed to production. A separate development environment is used for testing.
- Secrets. Keys and passwords live in the Infisical configuration vault and are injected at runtime. None are stored in the code.
- Background jobs. Distribution cycles, win expiry, settlement release, return deadlines, unpaid-order cancellation, ledger retries, revenue snapshots, anomaly scans, message delivery and daily summaries.
- Handover documentation. The repository includes an operations runbook (health checks, logs, incident levels SEV-1 to SEV-3), a go-live checklist, a user acceptance checklist and an access transfer template.
3. Ownership & Access
All business accounts used by the platform are moved into Paylesa’s ownership, registered to the company email addresses below, so that Paylesa holds full control of its services.
Confirmedpaylesaofficial@gmail.com
All platform data and credentials:
- Paystack (payments and payouts)
- Speedaf and GIG Logistics
- Firebase, Cloudinary and Brevo
- Infisical configuration vault
- Source code repository
- Support and company email
Confirmedchairman@paylesa.com
Mobile app publishing:
- Google Play Console: com.paylesa.marketplace (transfer submitted 20th October 2026, pending Google review)
The domain name and DNS (paylesa.com) are held in Paylesa’s Namecheap account.
🔑
Where every password and API key is kept: Infisical
- Address
- https://app.infisical.com
- Sign in with
- paylesaofficial@gmail.com
- Project
- paylesa (production environment: prod)
- Holds
- Database and Redis access, Paystack, logistics, Firebase, Cloudinary, Brevo and email credentials, and server keys. The Android signing keystore is in the Deliverables Vault.
No secret is stored in the source code or in this document. To change a key, update it in Infisical and redeploy; the platform reads it at start-up.
The Technical Lead stays on each account as a developer or administrator to continue technical support. Hosting, servers and day-to-day platform operations continue under a separate hosting and maintenance arrangement, so the live service is not interrupted.
4. Source Code & Intellectual Property
On acceptance of this handover, the Paylesa source code, mobile application, designs, content and published policies are delivered to Paylesa Digital Market Place as a single clean release (version 1.0.0), together with the Android signing keystore and its credentials needed to publish future updates. From that point, Paylesa Digital Market Place owns them.
The source code is held in an encrypted Deliverables Vault on this page. The vault unlocks once this document is signed and opens with a private access key handed over by Profynix’s Technical Lead. It also holds the Android signing keystore and its credentials. Files are decrypted only in the recipient’s browser, each file’s checksum is verified, and every download is logged.
5. Final Acceptance
This document, together with PH-01 Overview & Handover Letter and PH-02 Platform Features, forms the complete Paylesa Handover Pack.
“By signing below, Paylesa Digital Market Place accepts the Paylesa platform as delivered and described in PH-01, PH-02 and this document, confirms ownership of the accounts, source code and intellectual property set out above, and agrees that the handover is complete. Any further work will be carried out under a separate arrangement.”
