Budget: 10000 UAH Deadline: 1 day
Good day. I have already developed this module for Fondy. I have a ready working solution. I am ready to show a demo on the latest version of Magento with access to the admin panel.
It is necessary to update and make the Fondy payment module for Magento 2 fully operational, which is currently available as an official Fondy plugin and open-source repository on GitHub: fondy.io/gb/plugins/magento-2 and github.com/cloudipsp/magento2. The current module is officially targeted at Magento 2.0–2.3, while in production, branches 2.4.x are predominantly used, which have changes in dependencies (PHP versions, payment API, etc.).
Adapt and update the Fondy module for correct operation on the current versions of Magento 2.4.x (Open Source / Commerce, we will specify the specific minor version after the start).
Ensure stable operation of at least two integration methods:
Prepare a clear installation, activation, and configuration guide for the module for Magento 2.4.x (via Composer and, if possible, via Magento Marketplace/archive).
Currently, the official Fondy documentation for Magento 2 describes support for Magento 2.0–2.2 and 2.3, including manual installation and via Composer (cloudipsp/magento2:1.2.1 and dev-master). The latest releases of Magento 2.4.x have changed the supported PHP versions and have new requirements for modules, which may break old payment extensions. Exact errors (logs, stack trace, Magento/PHP version) will be provided after the first installation/activation attempt on the dev stand.
Review the cloudipsp/magento2 repository: module structure, composer.json, dependencies, use of Magento payment API, checkout rendering methods (redirect / on-page).
Match the current implementation with the requirements of Magento 2.4.x (minimum PHP versions, changes in payment modules, event/observer, DI, layout/JS components).
Compile a list of incompatibilities and potential points of failure (deprecated classes/interfaces, changed XML configs, Composer dependency issues).
Update the module's composer.json (PHP versions, dependencies, package type, autoload, constraint for magento/framework and payment modules).
Align module.xml, registration.php, etc/di.xml, etc/payment.xml, etc/config.xml with the requirements of Magento 2.4.x.
Check and update the JS part / Knockout UI components of checkout if necessary (especially for on-page integration via Fondy Checkout / ipsp-js-sdk).
Ensure correct operation of the main flows:
creating a payment request to Fondy (merchant_id, payment_key, amount, currency, order_desc, etc.).
processing callback/notification (webhook) from Fondy, updating order statuses in Magento (pending, processing, canceled, refunded, etc.).
support for instant refunds and, if possible, hold/capture (freezing amount, partial capture/refund).
Ensure that the module correctly appears in Stores → Configuration → Sales → Payment Methods → Fondy / Fondy on Page.
Configuration fields:
Check that enabling/disabling the payment method works as expected and does not break checkout when Fondy is disabled.
Set up a Magento 2.4.x stand (the version will be agreed upon: for example, 2.4.6-pX).
Cover the following scenarios:
Provide a brief test report (list of scenarios, results, logs/screenshots in case of errors).
Prepare a README/instruction (in the form of a Markdown document) with the following sections:
Requirements: Magento 2.4.x, minimum PHP version, required modules.
Installation:
Activation: php bin/magento module:enable Fondy_Fondy, setup:upgrade, setup:static-content:deploy.
Configuration in the admin panel (Stores → Configuration → Sales → Payment Methods → Fondy), description of each field.
Description of main operation scenarios and tips for diagnosing typical errors (where to look for logs, what statuses to expect).
Updated Fondy module, installable via Composer, which:
Repository (fork or separate repo) with:
module source code,
installation/configuration instructions,
brief description of changes made (changelog).
Experience in developing/supporting payment modules for Magento 2 (preferably cases specifically with 2.4.x).
Experience working with Composer packages, Magento DI, payment gateways, and preferably with Fondy or similar systems.
Willingness to briefly document changes and provide basic support for integration (answers to installation/configuration questions).
Budget: 10000 UAH Deadline: 1 day
Good day. I have already developed this module for Fondy. I have a ready working solution. I am ready to show a demo on the latest version of Magento with access to the admin panel.
Budget: 30000 UAH Deadline: 30 days
Good day! I am a Magento developer with 9 years of experience. (Magento 1/2, Enterprise, Cloud). I have extensive experience in both developing from scratch and supporting existing stores.
Deep customization and integration of external services and systems.
I have experience in developing payment services for Magento both from scratch and supporting existing ones.
I quickly looked at the current implementation - it completely needs to be redone because it is incompatible with the Magento Payment Gateway. There are still many nuances, but it is worth discussing in a private conversation.
I am ready to discuss the details of cooperation, feel free to reach out.
Budget: 8000 UAH Deadline: 1 day
I am ready to complete this project and have extensive experience in developing various applications.
I need content from WhatApp pulled into Monday.com project management plans / task lists. The connection currently created is already transferring information to Monday.com but not to the right project boards and not including owner and timeline. I need help with this connection.
I am looking for an experienced developer or a small team to create the ENGoose website - an online platform with ready-made ESL materials for English language teachers. This should not be an ordinary informational site or landing page, but a convenient library of educational materials with a paid subscription, personal accounts, and the possibility of further development. Currently, I am prioritizing WordPress, but I am open to considering Bubble or another well-argued technical solution. Main functionality A modern responsive website for computers, tablets, and smartphones. A catalog of ESL materials with cards and separate lesson pages. Filters by levels, topics, types of materials, grammar, and other parameters. Search and sorting of materials. Free and paid materials. Monthly subscription. Integration of a payment system compatible with Ukrainian individual entrepreneurs. Registration, login, and personal account. Adding materials to favorites. Protected access to PDF files and Canva links. Administrative panel for self-adding and editing materials. Main informational pages: FAQ, pricing, contacts, terms of use, and privacy policy. Timer until the next material is released. Possibility of further expanding functionality. Additional features Please separately evaluate the possibility and cost of: private notes and personal tags for lessons; a simple planner: date, time, student name, and status "scheduled/conducted". In your proposal, please indicate: recommended platform and its advantages; examples of similar projects; estimated cost and timelines; what is included in the proposed amount; monthly and annual expenses after launch; terms of further support.
There is a sales funnel for the online store that we want to replicate for ourselves. It looks like this: The main landing page (the product that is primarily for sale, for example, a shirt). Then the checkout page (where the person enters their details and chooses how many shirts they want to buy, for example). Then they go further down the funnel and are offered upsell 1 (socks) + then upsell 2 (underwear) and finally the thank you page. You can see how this should work in terms of page transitions and logic here (you need to get to the end to the thank you page) https://3plus3.heroman.com.ua/standard/. We have examples of pages that we want to create for ourselves. So for us, essentially, we will copy the design - layout - fill it in with our product. The upsell pages will have the same design and structure as on the site I shared above (underwear). You will not need to fill the pages with information, just gather the skeleton - so that the application comes through correctly. Also, you do not need to come up with the structure of the pages. From you, essentially: Copy and layout. Set it up to work technically correctly. Show how to work with this so we can do it ourselves. There are 2 website builders in mind, we are currently working closely with 1 and need to understand if we can deploy this on it (but I read in GPT that it is possible).
It is necessary to deploy a website from a full backup on a new hosting The website is created on Drupal Please send your proposals
A web service needs to be developed for automating the operations of coffee shops and small food service establishments. The product should have functionality similar to Poster POS, but with its own design, architecture, and source code. Copying the code or interface of Poster is not anticipated. The plan is to create a full-fledged commercial SaaS product that various coffee shops can use in the future on a subscription basis.In the first stage, an MVP needs to be developed Main functionality: registration and authorization of the establishment owner; creation of one or several establishments; management of employees and roles; catalog of products, categories, and modifiers; adding sizes, flavors, and additional options; cash interface for processing sales; opening and closing cash shifts; various payment methods; returns and order cancellations; inventory accounting and write-offs; basic stock accounting; sales history; reports on revenue, products, shifts, and employees; loyalty program for customers; adaptive operation on tablets, laptops, and smartphones; administrative panel for the service owner; tariff plans and restrictions according to the tariff.Future plans include mobile application; integration with payment terminals; receipt printing; integration with fiscal services; delivery and online ordering; table reservations; advanced analytics; API for third-party integrations; integration with accounting and CRM systems.Important requirements the system must be designed to operate multiple independent establishments; data of each client must be isolated; scalability of the product must be anticipated; secure handling of financial and personal data is required; the code must be structured and suitable for further development; technical documentation is needed; rights to the source code are transferred to the client after payment. At this moment, the design is absent, so a separate assessment of UI/UX design is needed or a ready-made solution for the MVP should be proposed.Please include in your proposal experience in creating SaaS, POS, CRM, ERP, or accounting systems; examples of similar work; proposed technology stack; team composition; estimated cost of the MVP; development timeline; what exactly is included in the proposed cost; cost of further support; whether you are ready to work in stages with payment for each completed stage. Preference will be given to performers or teams that have already developed cash, inventory, restaurant, or multi-user SaaS systems.