Budget: 2000 PLN Deadline: 5 days
Hello.
I develop bots in NodeJS. I have experience with exchanges. Write to me, and we will discuss.
Budget: 1500 PLN Deadline: 8 days
I read the technical specifications completely: a P2P merchant on Binance, Bybit, and OKX from scratch, step by step, starting with the trading core and integration with exchanges, then payment verification, automation, and analytics. According to the description, the most risky part here is not in connecting the API, but in reliability: to ensure that a payment is not counted twice, an order does not receive a double release, and after a failure or restart, the system restores the actual state of the transaction, rather than losing or duplicating events.
I have had exactly that experience. For more than three years, I managed a fleet of Telegram bots for a payment platform: payment and ticket events went through a RabbitMQ queue across dozens of merchant channels, with session recovery, reconnection without event loss, and delivery at least once. During 12 days of continuous operation, the sequential numbering of operations had no breaks with 994 events. This is the same class of task as yours: to prevent a payment or order from being lost or duplicated during failures and high load.
For exchanges, I built an asynchronous real-time system on top of Binance: receiving quotes via WebSocket, processing signals, managing through Telegram. I understand how to build a resilient cycle for round-the-clock operation and how to log every action for auditing. I have not worked with Bybit and OKX APIs before, but structurally they are similar to Binance, so connecting a new exchange is a clear task.
I agree with the phased approach from the specifications. It makes sense to start with the trading core and integration of one exchange, most likely Binance, since there is already experience with its API, plus basic order monitoring and logging. This way, we can test the architecture and quality of work with real code before expanding to Bybit, OKX, and full automation with payment verification and repricing. This reduces risk for both you and me: there will be no need to rewrite the core if requirements change along the way. I take the first phase into account with full testing, not just basic integration, so I am looking at a timeline of not a couple of days, but one and a half weeks.
I am ready to discuss the architecture in more detail and clarify the specifics of parsing SMS and bank notifications for payment verification, which will help to more accurately assess the volume.
Budget: 700 PLN Deadline: 5 days
Hello! I am Serhiy, I have 8 years of experience in IT across various technologies: web/mobile, backend, API, integrations, automation, and data handling.
I see the main task as follows: Automation of P2P on Binance, Bybit, and OKX. Development of a high-load system for full automation of P2P merchant operations on the exchanges Binance,...
Skills for the task:
- bots, parsing, and data handling
- reporting, analytics, and business automation
- solution architecture
- development, testing, and release preparation
- post-launch support
Portfolio: https://software.campstudio.net/#showcases
Budget: 2000 PLN Deadline: 3 days
Hello,
Your project requires a robust, fault-tolerant architecture rather than a simple trading bot, and it aligns well with my experience in building high-load backend systems, financial automation, API integrations, and scalable web platforms.
I would build the system from scratch with a modular architecture, integrating the Binance, Bybit, and OKX APIs, automated order processing, dynamic repricing, payment verification, comprehensive logging, role-based access control, and a real-time monitoring dashboard. The platform would be designed for 24/7 operation with scalability, auditability, and strong safeguards to minimize operational risk.
I recommend developing the project in phases, starting with the core trading engine and exchange integrations, followed by payment verification, automation rules, analytics, and advanced risk management. This approach allows early validation while keeping the system extensible for future exchanges and payment methods.
After reviewing the detailed technical requirements, I can provide a precise timeline, architecture proposal, and fixed-price estimate.
I would be happy to discuss the project and define the optimal implementation strategy.
Best regards,
Budget: 1000 PLN Deadline: 5 days
Hello, Denys! I have fully familiarized myself with your detailed technical assignment regarding the automation of P2P trading on Binance, Bybit, and OKX. The logic of asynchronous order tracking, parsing the order book (P2P Orderbook), and automatic repricing is completely clear to me. I am ready to start developing the system.
I respond crystal clear and factually:
1. My stack and skills: I am a Python developer. My specialization is asynchronous Python (asyncio, aiohttp), writing stable automation scripts, integrating complex REST APIs/Webhooks, and working with databases (SQL). I will write clean, modular code that can easily handle large streams of JSON data from cryptocurrency exchanges without lagging. I am familiar with Git and maintain my code neatly.
2. About the portfolio: My profile on this exchange is completely new, so there are currently no ready cases here. That’s why I indicated a cost of 1000 PLN for the First stage of development (for example, full integration of the P2P API of one exchange of your choice, setting up order book collection, and basic order monitoring), so you can check my skills in action without financial risks. I work purely for quality, the first feedback, and stars in my profile.
3. Implementation logic: I will build the monitoring and repricing system on asynchronous tasks so that the bot can instantly react to competitors' price changes and reposition your listings according to the mathematical rules (limits) you set.
I am ready to move to a personal chat right now, discuss the architecture of the first exchange, and immediately start coding through a secure Safe. I'm here!
Budget: 10000 PLN Deadline: 21 days
Shalom!
We have reviewed the technical specifications. It is clear that the key task here is not the integration with the exchange APIs, but the construction of a reliable high-load platform where each financial operation is controlled, logged, and protected from errors.
We would immediately build the system on a modular architecture: separate services for managing listings, repricing, processing orders, verifying payments, releasing cryptocurrency, risk management, and analytics. This will allow scaling the platform, connecting new exchanges and payment methods without reworking the core.
We have relevant experience in developing high-load backend systems, automation platforms, and complex API integrations. We design fault-tolerant architecture, work with REST/WebSocket APIs, message queues, Docker, PostgreSQL, Redis, monitoring, logging, and background processes. We develop CRM/ERP systems, dashboards, business process automation, and financial services.
Before starting, we are ready to conduct a technical session, propose architecture, a roadmap, and if necessary, prepare a small PoC of one of the key modules. This will allow us to test the chosen approach before full-scale development begins.
Our website: https://winbixai.com/ru. It presents only a part of our projects; we will send more relevant cases in private messages.
Budget: 700 PLN Deadline: 4 days
Hello, I am in the TOP 10 freelancers on the platform, I have completed similar projects, I will do it quickly, efficiently, and at a low cost.
Budget: 2000 PLN Deadline: 5 days
With a volume of 40,000+ transactions, connecting three APIs and assembling a dashboard is the easy part of the job. The real challenge is to ensure:
- a payment will not be used again;
- an order will not receive a double release;
- cryptocurrency will not leave the account solely based on an SMS, screenshot, or recognized receipt;
- after a failure, repeated webhook, or restart, the system will restore the actual state of the transaction;
- the operator can stop the automation before any financial damage occurs.
I have close practical experience:
- long-running trading systems on Python with Binance Futures API, risk control, position states, and reconciliation;
- asynchronous repricing and synchronization of stocks for 100,000+ products through external APIs;
- FastAPI, asyncio, PostgreSQL, SQLAlchemy, Docker, Linux;
- systems with retries, idempotency, logging, and manual operator intervention.
I would not directly link the business logic to the API of each exchange. The architecture should consist of its own P2P core and separate adapters for Binance, Bybit, and OKX. This way, order states, repricing rules, payment verification, and risk control remain unified, and a new exchange can be added without rewriting the entire platform.
I propose to build the release process as a separate controlled workflow:
1. Receiving and saving the order with a unique identifier.
2. Verifying the actual receipt of funds through an available banking channel.
3. Matching the amount, currency, sender, destination, and time window.
4. Checking that the payment has not been used before.
5. Transactional locking of the deal before release.
6. Rechecking the state with the exchange.
7. Release with idempotency and subsequent reconciliation.
8. Switching to manual mode in case of any discrepancies.
SMS, push notifications, and OCR can serve as additional signals. They should not be the sole basis for automatic release.
It makes sense to conduct development in vertical stages:
- auditing available P2P APIs, merchant rights, and payment channels;
- working outline for one exchange, one account, and one payment method;
- announcements, orders, and repricing;
- secure payment verification and controlled release;
- multi-accounting, other exchanges, roles, analytics, and scaling.
After clarifying the merchant statuses of accounts, banks, currencies, countries, and rules for automatic release, I will prepare a decomposition, stages, and a realistic estimate for development.
Budget: 45000 PLN Deadline: 20 days
Hello. I am ready to execute the project in stages.
In the first stage, I will conduct an audit of the available APIs of Binance, Bybit, and OKX, check the capabilities of merchant accounts, design the system architecture, database, order processing logic, payment processing, and automatic release. I will also prepare a detailed technical specification and a working prototype of the main integration.
The deadline for the first stage: up to 20 working days.
Next, I can implement:
integration with the official P2P APIs of Binance, Bybit, and OKX; automatic creation, modification, and disabling of ads;
an automatic repricing system;
real-time order retrieval and processing;
automatic and semi-automatic operation modes;
integration with banking APIs, SMS, and notifications for payment verification;
protection against duplicate payment accounting and double release;
automatic release of cryptocurrency upon confirmed payment;
working with multiple accounts, currencies, and payment directions;
a web management panel;
roles and access rights;
notifications, logging, action auditing, and kill-switch;
monitoring, backup, and deployment of the system on the server.
Preliminary timelines:
MVP for one exchange 3-4 months.
Working version for three exchanges 8-12 months.
Full production version with high fault tolerance, banking integrations, advanced analytics, and risk management system up to 12-15 months.
Exact timelines and costs can be determined after checking access to the merchant API, the list of banks, currencies, countries, and payment methods.
I work only through official APIs and secure integrations. I do not use Selenium, browser emulation, or unofficial methods that may lead to account blocking or financial losses.
Budget: 11250 PLN Deadline: 30 days
Hello!
I am Nina from the Valflow team. Valentin specializes in high-load automation systems, crypto integrations, and trading bots - this is exactly the stack needed for your project.
We understand the task: a complete P2P cycle on Binance, Bybit, OKX with automatic release, protection against double payments, repricing, and a web panel for 40,000+ transactions per month. Architecture from scratch, without ready-made solutions - this is our approach.
Project examples: https://valflow.dev
Terms:
• Cost: starting from $3,000 - final after clarifying the technical specifications
• Implementation in stages through Escrow
We are ready to discuss the details!
Budget: 100 PLN Deadline: 15 days
Denis, I am familiar with P2P automation on three exchanges. The main issue usually isn't in placing orders, but in how to avoid getting blocked by banks and timely parsing receipts when there's a stream of transactions, especially on OKX and Bybit, where the API often returns statuses with a delay compared to websockets.
I have already set up similar software and know that when working with multiple Bybit accounts, it quickly cuts limits on requests if sent directly without rotating proxies for each API key. Another point: if parsing SMS on Android through a gateway, sometimes operators delay messages for a couple of minutes, so it’s necessary to duplicate the check through bank webhooks or pushes.
import easyocr
reader = easyocr.Reader(['ru'])
text_lines = [line[1] for line in reader.readtext(img_path)]
full_text = ' '.join(text_lines)
is_paid = 'Recipient' in full_text and 'Successful' in full_text
First, I will gather connectors to the exchange APIs and create a layer for proxies. Then I will integrate SMS parsing and OCR for recognizing payments. After that, I will set up a web panel with a general dashboard and an emergency stop button.
I can start tomorrow.
