Mass payments or payouts triggered by an event
Hand SettleOps a batch of payments, refunds or payouts.
It executes the actions, retries failures by the rules and shows the result of the whole operation — no manual check of every step.
one SettleOps operation
Work out what batch payments and payouts will cost in the first year.
Enter your own figures.
Batches: a week, each one a single SettleOps operation.
That is ≈ 65 SettleOps operations a month.
Manual work
Technical preparation and manual submission of one batch takes h.
Checking the result of one operation takes min, successful and failed actions alike.
With your own code or with SettleOps, exceptional cases still need manual review: suppose % of batches hit one, and each takes min.
An employee costs ₽ a month.
Development and maintenance
An engineer costs ₽ gross a month.
Your own code: mo of development, engineers maintaining the code.
What does your own code include?
This is code your team writes and maintains itself.
Splitting a batch into money actions and building the register for the bank.
Each action exactly once: none skipped when a server fails and no double payout.
Retrying failed actions and sending those that still fail for review.
Partial execution: the batch result when some of its actions have failed.
Reconciling batch results with the bank.
Tracking each action through to its final status.
With SettleOps: wk of integration, engineers maintaining the code.
What does maintenance include?
This is the work of your engineers on your product’s side.
With SettleOps: supporting the integration, updating the SDK/API, diagnosing issues on the client side.
SettleOps fee — ₽12 per operation of any type.
Payments, refunds and payouts are charged separately.
The fee depends on the payment method and payment system.
More about pricing.
First year: your own code ₽2,228,646, manual batches ₽731,250, SettleOps ₽459,855. The manual process is cheaper below 9.2 batches a week.
When does SettleOps pay off?
First year at 15 batches a week
SettleOps is cheaper by ₽1,768,791
SettleOps₽459,855Calculation details
Your own code — ₽2,228,646
development: 2 mo × ₽300,000 = ₽600,000
code maintenance: 0.5 engineers × ₽300,000 × 10 mo = ₽1,500,000
manual work: batches by hand while development lasts, then reviewing exceptional cases = ₽128,646
With SettleOps — ₽459,855
integration: 1 wk = ₽75,000
code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500
manual work: batches by hand while integration lasts, then reviewing exceptional cases = ₽23,190
fee: ₽12 per operation × ≈ 764 operations a year = ₽9,165
saving ₽271,395
SettleOps₽459,855manual workdevelopment and integrationcode maintenanceSettleOps feeSettleOps levelmore than with SettleOps
Calculation details
Manual batches — ₽731,250
manual work: 1.5 h × ₽625 × 52 batches = ₽48,750 for each weekly batch, × 15 = ₽731,250
With SettleOps — ₽459,855
integration: 1 wk = ₽75,000
code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500
manual work: batches by hand while integration lasts, then reviewing exceptional cases = ₽23,190
fee: ₽12 per operation × ≈ 764 operations a year = ₽9,165
Threshold — 9.2 batches a week
at 15 batches a week — above the threshold: SettleOps is cheaper than manual batches by 731,250 − 459,855 = ₽271,395
SettleOps is cheaper than the manual process from about 9 batches a week.Exact threshold for the current figures: 9.2 batches a week.
Every batch handled by hand adds to the yearly spend. Spend on SettleOps grows much more slowly — most of it goes on integration and maintenance.
Batches a week15 batches a week
SettleOps saves ₽1,768,791 over in-house development in the first year.At 15 batches a week, SettleOps saves ₽271,395 over the manual process.
Calculation assumptions
One batch is one SettleOps operation, and the fee is ₽12 per operation however many money actions it holds. A month has 52 ÷ 12 weeks.
By hand, a batch is technically prepared, submitted, and its operation result checked as a whole. Your own code and SettleOps take over preparation, submission and checking; only manual review of exceptional cases remains.
Your own code: development while batches are handled by hand, then maintenance and reviewing exceptional cases.
Freed-up time does not necessarily mean a direct cut in spend. The estimate excludes infrastructure, taxes and employer contributions, and fees for payments and payouts.
Questions and answers
What is an operation? Is it a payment or a payout?
An operation is a container for financial actions: payments, refunds and payouts. It usually maps to a business transaction in your product. For example, an apartment rental deal consists of the tenant’s payment and the payout to the owner.
Is this some kind of payment gateway?
No. SettleOps is a payment operations layer that sits between your product and payment gateways. It runs the whole operation and routes payments, refunds and payouts through rails that are already connected, providing orchestration, oversight and resilience.
Why not write this ourselves — with AI in a week?
A happy-path scenario is quick to write. Everything else is expensive: retries and rail failover, timeouts, partial execution, disputed outcomes, audit. That is SettleOps.
We already have a payment layer. Why do we need SettleOps?
Launch new money scenarios without expanding your own infrastructure for running them. If SettleOps already supports the scenario you need, you only have to integrate it into your product. You won’t have to build and maintain new mechanisms for orchestration, retries, timeouts and execution control yourself.
Won’t we become dependent on you?
Your code works with operations through the API and webhooks, not with provider models.
What if we decide to stop using SettleOps?
Your business processes stay in your product. You can stop creating new operations in SettleOps and move their execution to your own system or another provider. Operation history is available through the provided export mechanisms; operations created earlier must be completed or settled before you disconnect.
What happens if SettleOps itself goes down?
An accepted operation is stored together with its plan and attempts and continues after recovery. Nothing is restored from memory.
How much does it cost?
Pricing is not fixed yet — we’ll discuss it on the pilot.