You need to make a ZENOPOSTER.

An experienced Laravel developer is required for the integration of a payment system into an existing project. About the project Backend: Laravel Frontend: React Project: cloud file storage platform (similar to Dropbox) What needs to be implemented Integration of credit card payments via the payment system API. Creation of a payment. Redirecting the user to the payment page. Handling successful and unsuccessful payments. Processing callback/webhook. Checking the payment status. Correctly changing the order status after successful payment. Logging API requests and responses. Functioning in both test and production environments. Requirements Excellent knowledge of Laravel. Experience in integrating payment systems (bank APIs, etc.). Experience working with REST APIs. Will be an advantage Experience in integrating bank payment gateways. Ability to show similar projects. What we will provide Complete technical documentation of the payment system. Access to the test environment. When responding, please indicate: 1. Which payment systems you have already integrated. 2. Cost of work. 3. Completion time. 4. Examples of similar projects (if available).

TECHNICAL TASK Development of a Digital Signage system for a network of advertising screens 1. General description of the systemThe system is designed for remote management of media content (video, images) on a network of televisions running Android TV. Architecture:Backend / Control Panel (Admin Panel): PHP (Laravel / Yii2 or pure PHP) + MySQL.Frontend (Player on TV): HTML5 / JavaScript (Single Page Application), which runs on TV in full-screen mode via the Fully Kiosk Browser app.2. Functional requirements: Control Panel (Admin Panel on PHP)2.1. Screen (Television) ManagementAbility to add/remove screens in the system.Each screen is assigned: Name (geo-point), unique ID (device_token), and status (Online/Offline).Monitoring (Ping): Displaying the TV status in real-time. If the TV has not sent requests for more than 5 minutes, color its status red (Offline). 2.2. Content Management (Media Library)Uploading files (video, images) to the server.Deleting files (with automatic deletion of the physical file from the server).Ability to view (and modify) on which screens each individual media file is broadcasted.Setting the playback order of files. 2.3. Server API (for communication with TV)Implement REST API (JSON):POST /api/ping — receives its ID from the TV, records the last activity time (for Online status), and returns the current playlist version.GET /api/file/device_token — returns the current JSON array with links to media files, their order, and display time settings.3. Functional requirements: Client Player (HTML5/JS on TV)The player is a web page that is opened on the TV. The main task of the client is autonomy.3.1. Caching and Synchronization (Offline Operation)Upon startup, the player requests the playlist via the API.Local Storage: All files from the playlist (video/images) must be loaded into the internal memory of the browser (using Cache API or IndexedDB). Streaming (playing directly from the internet) is prohibited.Synchronization: If new content is added on the server, the player loads it in the background without interrupting the current display. After loading is complete, it adds it to the broadcast. If content is deleted on the server, the player must remove it from the local TV cache to avoid filling the device's memory.Offline Mode: In the complete absence of the internet, the player endlessly loops the last successfully loaded playlist. 3.2. Playback and RotationCyclic playback of content and according to the order set in the admin panel.For images, the display duration in seconds must be set (default 10 sec).Transitions between videos must be smooth, without black screens and noticeable page reloads. 3.3. Logging and Error Control (Failure Protection)Handling Corrupted Files: If a video file is corrupted and cannot be played, the player must skip it and turn on the next one in order, rather than hanging on a black screen.Show Logs (Analytics): The player must record in local memory the fact of each successful playback of a video. When the internet is available, this data is sent in batches to the server (POST /api/logs), so that statistics can be viewed in the admin panel: "Video A on TV #3 was shown 450 times in a day and 2365 times in total".4. Optimization Requirements for Android TVThe player interface must not contain any control elements (cursors, scroll bars, buttons). Only clean content on the full screen.JS code must be optimized for memory (timely clearing unused DOM elements and object URLs), as budget televisions have strict limitations on RAM and may crash the tab due to memory leaks after 12-24 hours of continuous operation.

It is necessary to migrate the Opencart online store from PHP 7.4 to PHP 8.x. Currently, the core version is 3.0.3.8. We read that most likely the core will also need to be migrated to version 4.0 and there shouldn't be many difficulties... The functionality is mostly custom, and there are also Simple, OCFilter, Nova Poshta. We are waiting for recommendations and an approximate price. Ideally, someone who has already done similar work.

It is necessary to perform the update, transfer, and configuration of Laravel projects to a new server, ensuring stable operation, security, protection against exploits, and correct functioning of all services after migration. 1. Main tasks Prepare the new server for operation. Transfer project files, databases, configurations, and cron jobs. Update server software. Configure a secure environment for Laravel. Check compatibility of PHP, Laravel, Composer packages, and dependencies. Ensure protection against known exploits, malicious requests, and unauthorized access. Set up SSL certificates. Check the functionality of the websites after the transfer. 2. Transfer of Laravel projects For each project, it is necessary to: Transfer project files. Transfer the database. Transfer the .env configuration. Set directory access permissions: storage bootstrap/cache Check functionality: homepage; admin panel; authorization; forms; API; file uploads; email sending; cron jobs; queue workers.3. Security and protection It is necessary to implement basic and application-level protection: close root access via SSH; configure SSH access only via keys; change the default SSH port if necessary; configure the firewall; allow only necessary ports; install Fail2Ban; hide service versions of Nginx/Apache/PHP; restrict access to .env, .git, backup files, log files; set correct file permissions; check projects for malicious files; check Composer packages for known vulnerabilities; update dependencies if it does not break functionality; configure protection against SQL injection, XSS, CSRF, and path traversal; check the correctness of Laravel APP_ENV and APP_DEBUG; set APP_DEBUG=false in production; configure rate limiting for critical endpoints; check access to storage/uploads; configure protection against PHP execution in upload directories; check access rights to admin panels. 4. SSL and domains It is necessary to: Install SSL certificates. Configure automatic SSL renewal. Enable redirect from HTTP to HTTPS. Check the correct operation of websites via HTTPS. 5. Backup It is necessary to configure backup: project files; databases; .env files; uploaded media; cron configurations; Nginx/Apache configurations. Backup should be performed automatically on a schedule. It is preferable to store copies separately from the main server. 6. Post-transfer verification After migration, it is necessary to check: absence of 500/403/404 errors; absence of critical errors in Laravel logs. 9. Result of execution After the work is completed, there should be: Laravel projects successfully transferred to the new server; websites are functioning stably; SSL is configured; the server is protected with basic security settings; access to critical files is restricted; backup is configured; cron and queues are operational; the old server can be turned off after final verification.

I am looking for a developer for a project consisting of 4 related tasks for the website best-matchmaking.com to be completed sequentially:Integration of a ready-made premium Blade template for blog articles + auto-generation of Schema/SEO markup (Article, FAQPage, Open Graph, canonical) for all current and future articlesRefinement of the blog structure: changing URLs with 301 redirects, renaming in the footer/menu/breadcrumbs, cleaning hidden code, removing categoriesNew block (photo + quote from a review) in the existing constructor for the main and landing pages = the ability to independently add text blocks between sectionsUnification of fonts, sizes, and colors across the entire site (except for the blog) — a single standard for headings and regular text, including header and footerDetailed technical specifications for each item — I am attaching them below via Google link.https://docs.google.com/document/d/1E5oQO2E-xmKJ3C0jW0ZsSPDBjaiELq0ETxfdivW6yIs/edit?tab=0 HTML samples and code will be sent in private messages after the response IMPORTANT! Please review all 4 tasks in detail before making an offer, especially the last one about fonts. There is quite a lot of work involved.Experience RequiredLaravel + Blade — confident, not beginner levelFrontend (CSS/JS) at the same level as backendExperience working with existing, not your own codeWork FormatBackup and test server before starting, transfer to production is MANDATORY — after agreement and testingMandatory self-check on all devices before submission — sending "ready, check" without your own testing is not acceptable. Bugs found after submission will be fixed within the same task. Bugs that arise during the transfer must also be fixed in production.Report with "before/after" screenshots for each itemDeadline and budget — after assessing the volume based on the detailed technical specifications. I look forward to your offers. Thank you