Budget: 27000 UAH Deadline: 30 days
Good afternoon. Regarding the timeline and budget, I would estimate around 180,000 UAH and about 30 working days for the first working version - receiving, checking incoming payments, outgoing payouts, internal API, statuses, operation logs, and a test screen for connecting to the web page.
Look, there’s a nuance here - without centralized services, this is no longer just a payment button, but a payment infrastructure. We need to carefully address key storage, hot wallets, limits, re-checks, network confirmations, fees, payout queues, and protection against duplicates. It’s better not to heroically tackle this on the fly, because when it comes to money, there’s an old wisdom - check seven times, send once =)
I would simplify it - first a short design phase, then core development. In the first stage, we describe the scenarios for receiving and withdrawing, choose networks USDT, USDC, TON, Ethereum, Tron, BNB Chain, set confirmation rules, and only then write the service. This reduces the risk of getting a working demo that breaks on real transactions.
> What you will need to provide
> access to the test environment of the site or a description of the future page
> a list of networks and tokens for the first version
> rules for payouts - automatic, manual, or through admin confirmation
> requirements for storing private keys and limits
> Questions
> do you need a custodial service with user balances within the system or just address generation and payment verification
> should outgoing payouts be automatic after the request or through manual confirmation in the admin panel
Relevant examples from Ingello
> https://business.ingello.com/platforma - a complex platform with roles, business logic, and internal processes
> https://business.ingello.com/prime-eva - an example of system automation for commercial processes and integrations
> https://systems-fl.ingello.com - a general profile of the team for complex systems, APIs, and automation
Overall, it’s a normal task for us, but I wouldn’t promise to do it cheaply and quickly - it’s better to do it sustainably than to later catch transactions manually in the logs. But that’s that.