Phoenix - Your AI AssistantCoding Programming Development Software Projects
Looking for freelance Coding Programming Development Software jobs and project work? PeoplePerHour has you covered.
opportunity
Build "SmartAjo": A Secure Fintech Web App for Thrift Savings
I am a Legal Practitioner looking for an experienced Full-Stack Developer (or Team) to build SmartAjo—a digital platform that modernizes the traditional Nigerian "Ajo/Esusu" thrift system. We have the Full Technical Specifications, Database Schema, and Business Logic ready. We need a developer to execute this blueprint into a secure, responsive Web Application (PWA). Core Project Logic (The "Tri-Wallet" System): The application relies on a specific logic where every user has three distinct balances: Locked Savings Wallet: For daily contributions. Funds are frozen until cycle maturity (e.g., 31 days). Matured Wallet: Funds move here automatically upon maturity (minus a 1-day Admin Commission). These funds are liquid for withdrawal. Utility/Credit Wallet: Used for instant Bill Payments and Loan disbursements. Key Features to Build: 1. Customer Portal: Registration/KYC: Phone OTP verification + Bank Account linking. Savings Plans: Users subscribe to daily plans (e.g., ₦1k/day). Bill Payments: Integration with VTPass API to pay Electricity/Airtime using "Matured" funds. Education Shield Module: A specific logic where saving 70% of a target triggers an automatic 30% loan top-up. 2. Field Agent Portal (Mobile Optimized): Cash Logging: A simplified interface for Agents to search for a user and log cash received. SMS Triggers: System must send instant SMS alerts to customers upon cash entry. Daily Reconciliation: A report showing "Total Cash Logged" vs "Cash Remitted." 3. Super Admin Dashboard: Global Liquidity View: Total Locked vs. Total Matured funds. Approvals: Manual approval button for Withdrawal Requests. User Management: Ability to ban users or agents. Loan Engine: Algorithm to calculate loan eligibility based on savings consistency. Required Integrations: Payment Gateway: Paystack or Flutterwave (for card funding). Bill Payment API: VTPass or Reloadly (for Airtime/Power). SMS Gateway: Termii or SmartSMSSolutions. Tech Stack Preference: Backend: PHP (Laravel) OR Node.js. Frontend: React, Vue.js, or Clean Blade Templates (Must be Mobile Responsive). Database: MySQL. Security: SSL, CSRF Protection, and Bcrypt for passwords are non-negotiable. Deliverables: Full Source Code (uploaded to GitHub/Bitbucket). Database SQL File. Deployed & Tested Application on my Server. 30 Days of Post-Launch Bug Support. Budget & Timeline: Budget: $500 - $650]. Timeline: 4 - 6 Weeks.
Unethical or Fraudulent Behavior
Choose the company name Tesla Amazon Netflix Starbucks JetBlue Walt Disney Proctor & Gamble In your initial post, introduce yourself and address the following: Select the company you'd like to focus on for your project. Summarize an article about unethical and/or fraudulent activity on your selected company. Include the following details in your response: Include the citation. If you can't find unethical or fraudulent activity, review the legal proceedings section of the company's 10-K and summarize one of the lawsuits described there. Explain how the unethical and/or fraudulent activity or lawsuit was resolved and whether it could have been prevented. Part 2 In your responses to two peers, be sure to address the following: If your peer posted an article on unethical and/or fraudulent activity, explain how the accounting department could have prevented the unethical and/or fraudulent activity that happened in the article your peer shared. If your peer posted a lawsuit, explain the potential impact of the lawsuit on its customers and organization as a whole. First respond. Hi everyone, my name is Gagandeep Singh, and I am an accounting student. For this course project, I chose to focus on Amazon because it is a very large company that has faced ethical and legal issues in its business operations. The article I reviewed talks about how Amazon admitted there was a risk of fraud on its platform from counterfeit products being sold by sellers. These fake and counterfeit goods broke the trust of customers, brand owners, and Amazon shareholders since it ruins the trust of the company supplying these items and the shareholders who invest into this company. The article explains that Amazon did not do enough to stop these counterfeit products, which caused concerns about ethics and consumer protection (Brachmann, 2019). Amazon increased efforts to remove counterfeit sellers and fake products from its platform by investing more money into fraud detection systems and brand protection programs. The issue could have been prevented earlier if Amazon had stronger controls and processes of verification in place before allowing sellers to list products. The way to make sure this doesn't happen in the future is to have better monitoring and stricter seller approval processes. Reference Brachmann, S. (2019). Amazon admits to fraud risk: Counterfeiting woes affect shareholders, brand owners and consumers. Inventors’ Digest. Second respond My name is Matt, and I am a junior at Southern New Hampshire University. I am 21 years old and currently pursuing a degree in business-related studies with an interest in accounting and financial analysis. I am looking forward to developing a deeper understanding of earnings quality and ethical financial reporting throughout this course. For my ACC 345 project, I have selected Tesla, Inc. as the company I will be focusing on. Tesla has experienced rapid growth and strong market performance in recent years, but it has also been involved in several ethical and legal controversies that raise questions about earnings quality and corporate governance. A recent article published by Reuters discusses allegations related to Tesla’s marketing and disclosures surrounding its Autopilot and Full Self-Driving (FSD) technologies. According to the article, U.S. regulators, including the Department of Justice and the Securities and Exchange Commission, have investigated whether Tesla made misleading statements to consumers and investors by overstating the capabilities of its driver-assistance systems. These claims raised ethical concerns because exaggerated or misleading disclosures could influence investor decisions and artificially support stock prices, thereby impacting earnings quality (Shepardson, 2023). The issue has not yet been fully resolved, as investigations were ongoing at the time of publication. However, Tesla has updated some of its disclosures and marketing language to clarify that its vehicles do not offer fully autonomous driving. This situation may have been prevented through stronger internal controls, more conservative public disclosures, and clearer communication with regulators and consumers. Transparent reporting and ethical marketing practices are essential to maintaining investor trust and ensuring that reported earnings reflect the company’s true financial performance. Reference Shepardson, D. (2023). U.S. probes Tesla over claims about self-driving cars. Reuters.
opportunity
Build Integration to send IONOS Web Orders to Kipos POS
We run a food takeaway and need a developer to build an integration so that orders placed on our IONOS webstore are automatically sent into our Kipos account (https://app.kipos.uk/) and print straight to our kitchen/printer setup with no manual re-entry. This must be production-ready: fast, reliable, and built to handle busy service periods. What the integration must do 1) Capture new online orders from IONOS Detect new orders as soon as they’re paid/confirmed (or the correct “ready for kitchen” status) Pull all relevant order data: Order ID, timestamp Customer name + phone/email Delivery vs collection Address (delivery) / pickup details (collection) Requested time: ASAP vs scheduled (time slot if applicable) Customer notes (allergies, “no onions”, etc.) Items, quantities, variants Modifiers / add-ons / extras (e.g., “extra cheese”, “no sauce”, spice level) Discounts / delivery fee / tips (if present) Payment method/status 2) Create the order in Kipos exactly as the kitchen needs it Push the order into Kipos so it lands in the correct screen/queue as an online order Map all the required fields Ensure delivery/collection is correctly set and visible on print tickets Include requested time clearly (especially for scheduled orders) 3) Auto-printing to kitchen printers Orders arriving in Kipos should auto-print to our configured printer(s), or be inserted into the correct Kipos workflow/status that triggers printing. Key requirements (takeaway-specific) Modifier & note handling (critical) Must support multiple modifiers per item, and multiple items each with their own notes Preserve formatting so the ticket is easy to read during service Handle edge cases like: “No X” and allergy notes Duplicate prevention + reliability No duplicate tickets/orders if a webhook retries or the sync is re-run Retry + failure handling: Automatic retries Clear error logs Optional alert (email) if an order fails to sync Operational timing Webhook/event-driven preferred (near-instant) Polling acceptable only if webhooks aren’t available, but it must still be reliable and efficient Security Secure credential storage (environment variables/secret store) HTTPS, least-privilege access Preferred technical approach We’re open to the best implementation, but we expect this to be either: Middleware service (recommended): listens for IONOS orders and posts to Kipos or Direct plugin/integration if IONOS supports it. Deliverables Working live integration: IONOS → Kipos order creation + printing workflow Configuration options: Which order status triggers sending Item/modifier mapping method Logging dashboard or structured logs (success/failures, retries, duplicates) Documentation: Setup steps How to update menu/mappings Troubleshooting guide Test evidence: At least 10 varied test orders (modifiers, delivery/collection, scheduled/ASAP) Source code + handover (Git repo or zip) Short post-launch support period (bug fixes) Acceptance criteria A new IONOS order appears correctly in Kipos within an agreed time (e.g., under 60 seconds if webhook-based) Ticket prints automatically (or via correct Kipos status trigger) without staff interaction Items, modifiers, notes, times, and delivery/collection details are accurate and readable No duplicates under retries/network issues Clear logs for each order’s sync status To include in your proposal Your recommended approach (webhooks vs polling, architecture, hosting) Relevant experience (POS integrations, online ordering, printers/kitchen workflows) Estimated cost + timeline (phased: build → test → deploy) What you need from us (API access, sample menu, Kipos printer workflow details) Info we can provide to speed things up Sample orders (with modifiers/notes) Our current IONOS product list/menu structure Screenshot/video of our Kipos order screen + print output requirements Printer setup details inside Kipos (single printer or multiple stations)
Unreal Engine + Pixel Streaming + Full Platform Integration
We are a technical team and we handle all technical solutions and decisions ourselves. We are not looking for an architect, a planner, or someone else to define the system for us. What we need is an execution-focused engineer who can help implement the website strictly according to our requirements. This project has very strict verification requirements. There are eight platform development contracts based on the same principle; this is just the first one. We need to deliver a multi-role platform based on (state-machine driven + Stripe payments/escrow + ad bidding + 3D digital humans via pixel streaming).Using low-code + modular composition, we are building an international platform. It must be explicitly stated that this is not an MVP. A.Deployment & Infrastructure(Must be assembled and built on the Fly.io platform) 1) The platform must run on (frontend/backend, jobs/queues, WebSocket/WebRTC services as needed). 2) Proper logging/monitoring/alerting is required, including alerts for third-party integration failures and cost/usage anomalies. B.Core Requirements (Important) 1) Multi-role / four portals: end users, service providers, maintenance staff, and admin portal (different permissions and flows). 2) Critical business flows must be implemented using a state machine / state-driven architecture (no “skipping steps”): order → payment → escrow/split → fulfillment → acceptance → settlement → refund/dispute, with full traceability, rollback rules, and audit logs. 3) Payments: Stripe (payments, payouts, webhooks). Must handle idempotency, webhook replay protection, and concurrency-safe state transitions. 4) Automation / orchestration: n8n (or similar) as the workflow hub, connecting Supabase, payments, notifications, ads, and digital humans. 5) Conversational guidance: use Botpress (or similar tools) for conversations + next-step actions. 6) Advertising: creative management + delivery configuration + analytics; ad slot bidding/auction (e.g., Prebid.js / RTB model). Bidding logs must be retained and auditable. 7) Multilingual: UI/content must support multiple languages and integrate language detection and translation APIs. 8) External widgets / external entry systems：iframe / JS SDK / external components with controlled internal core logic. 9) Risk control mechanisms: rate limiting, switches, circuit breakers, fast shutdown without impacting payments) 10) 3D digital human system (Unreal Engine Pixel Streaming): 10.1.) MetaHuman + Unreal Engine for creating 3D digital humans. 10.2.) Pixel Streaming (WebRTC) to stream UE video to web/mobile clients. 10.3.) A unified control interface to switch avatars/actions and drive lip-sync via TTS audio, integrated with state-machine-driven guidance flows. C.Execution responsibility (mandatory) 1) This project must be completed independently by you personally. We do NOT accept teams, outsourcing, temporary staffing, or task splitting. 2) This requirement exists purely for commercial confidentiality reasons. 3) If the project cannot be completed by one individual, please do not proceed. D. Price and maintenance terms (fixed) Project delivery price: USD 3,000 (fixed) Post-launch maintenance: - USD 100 per month (fixed) - Includes system stability, critical bug fixes, security updates, and environment handling - No unilateral price increase is allowed - Any adjustment requires written mutual agreement If your pricing expectation is significantly higher, or if you cannot accept these terms, please do not contact us. E.Delivery time: 1) For an experienced and skilled engineer, under normal circumstances, the full project should be achievable within two months. 2) In addition, we have a clear requirement that within an earlier phase of the timeline, a runnable pilot version must be delivered. This pilot version is not the final completion, but it must already be in a stable, operable state and able to enter trial operation. 3) During the trial operation, we will identify issues, validate stability, and make necessary adjustments, so that the final delivery can meet the required quality standards. F. Please reply with: 1) Similar projects you have delivered (if possible, provide links/demos). 2) Recommended architecture and service decomposition. 3) What materials you need from me to proceed (execution step flows, required module list, etc.). 4)phased timeline, rough price range.
