We connect systems to each other and build APIs others can use: site and CRM, accounting and stock, payment providers, telephony, messengers. From one week, with logging and error handling.
This is a starting price. The exact figure and timeline come from your technical brief, and the review is free.
Who it is for
If somebody in your company opens two systems every morning and types the same record into both, this page is about that hour. The other version of the same job is a partner API sitting on your side with nobody to implement it. Either way the work begins by reading the documentation of the other side, and that reading costs you nothing.
Problems we solve
· The same record is entered into two systems
· An integration fails and you learn about it from a customer
· A partner offers an API and nobody can connect it
· The old integration has no documentation at all
What is included
· Exchange scheme: what moves, from where, how often
· Error handling, retries and alerts on repeated failure
· Logging detailed enough to trace any single request
· Documentation and a test environment
What we can build
· Exchange between site, CRM and accounting
· Payment provider and bank gateway integrations
· Telephony, SMS and messenger integrations
· Your own public API for partners
· An integration layer over several sources
How we work
· We collect the requirements and write down the edge cases
· We agree the scheme: who initiates, what happens on failure
· We implement and test on sample data
· We release to production and switch on monitoring
· We hand over the documentation
Engagement models
· Fixed price when the partner API is documented
· Time and materials when it is not
· Support: updating integrations when a partner API changes
Stack
LaravelNestJSPHPTypeScriptPythonCeleryNext.jsReactVue 3Inertia.jsBladeTailwind CSSPostgreSQLMySQLRedisMeilisearchiOSAndroidDockernginxPM2ObsidianTelegram Bot APIJSON-RPCClaude API
Projects for this service
Online Payments for Websites and Apps
35+different payment systems behind one integration
A wallet people abroad use to pay for services back home: top-ups and withdrawals, payments through aggregators, identity checks, limits and referrals.
NestJSTypeScriptNext.jsPostgreSQL
IT for FinTech and Payment Companies
4subsystems: private API, public JSON-RPC, agent office, documentation
Dealers take payments for services through providers, earn commission or rewards, and work in strictly isolated tenants. Integrators get a public JSON-RPC interface.
We build and run products that move money: wallets, processing, billing and reconciliation. This is the direction where we have 14+ years of practice and 35+ different payment systems behind us.
We connect payment acceptance so that the money arrives, refunds work and the accounting matches. Local providers and international gateways, from one week.
We work with companies that already run a system: extending it to fit a changed process, connecting it to the website and accounting software, migrating away from a platform that stopped fitting.
We know what hurts in a subscription product: isolation of customer data, billing, and onboarding a new customer without a developer.
Frequently asked questions
How long does an integration take?
From one week when the other side has documentation and a sandbox. Without them the timeline grows, because most of the effort goes into establishing how the partner API actually behaves.
How do you price an integration?
One integration starts from $300. Past that, the price follows the number of integrations, the direction of the exchange and the number of edge cases. We read the API documentation before quoting, and we do not charge for that.
What happens when an integration fails?
Failures do not stay silent: every request is logged, failed attempts are retried and a persistent error raises an alert. This is exactly where cheap integrations break, because they swallow the error.
Can you open an API for our partners?
Yes: keys, permissions, rate limits and documentation, so a partner developer can connect without asking questions first.
Local providers, local protocols, and a server of yours that they call. A short map of the payment work for a team planning market entry from outside the country.
6 min read
Discuss your task
Leave a name and a phone number, and we will ask the rest in the conversation.
Have an idea for a new product, or need to grow an existing one?
Tell us about the task. We will study it and propose an option that makes sense technically and economically.
