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: 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: 1 day
Good day. I am ready to implement. Write to me directly on tg pabomdi.
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.
