Run money operations on a schedule
Set the schedule once, and SettleOps runs the operations on time.
No scheduler of your own to build and no manual runs.
Work out what scheduled runs will cost in the first year.
Enter your own figures.
Scheduled runs: a week, payments and payouts.
That is ≈ 17 SettleOps operations a month.
Manual work
Today each run is prepared and started by hand: h per run.
Checking the result of one run takes min, successful and failed alike.
With your own code or with SettleOps, exceptional cases still need manual review: suppose % of runs hit one, and each takes min.
An employee costs ₽ a month.
Development and maintenance
An engineer costs ₽ gross a month.
Your own scheduler: mo of development, engineers maintaining the code.
What does your own scheduler include?
This is code your team writes and maintains itself.
Storing schedules and working out the next run: the calendar, time zones, the 31st in a short month.
Running exactly once: no skipped run when a server fails and no double payment.
Counting runs and stopping after the last one.
Changing and cancelling a schedule.
Tracking each run 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 scheduler ₽2,199,306, manual runs ₽585,000, SettleOps ₽444,253. SettleOps pays off above 3.1 runs a week.
When does SettleOps pay off?
Estimate for 4 runs a week over a year
SettleOps is cheaper by ₽1,755,053
SettleOps₽444,253Calculation details
Your own scheduler — ₽2,199,306
development: 2 mo × ₽300,000 = ₽600,000
code maintenance: 0.5 engineers × ₽300,000 × 10 mo = ₽1,500,000
manual work: runs by hand while development lasts, reviewing exceptional cases = ₽99,306
With SettleOps — ₽444,253
integration: 1 wk = ₽75,000
code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500
manual work: runs by hand while integration lasts, reviewing exceptional cases = ₽14,309
fee: ₽12 per run × ≈ 204 runs a year = ₽2,444
saving ₽140,747
SettleOps₽444,253manual workdevelopment and integrationcode maintenanceSettleOps levelmore than with SettleOps
Calculation details
Manual runs — ₽585,000
manual work: 4.5 h × ₽625 × 52 runs = ₽146,250 for each weekly run, × 4 = ₽585,000
With SettleOps — ₽444,253
integration: 1 wk = ₽75,000
code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500
manual work: runs by hand while integration lasts, reviewing exceptional cases = ₽14,309
fee: ₽12 per run × ≈ 204 runs a year = ₽2,444
Threshold — 3.1 runs a week
at 4 runs a week — above the threshold: SettleOps is cheaper than manual runs by 585,000 − 444,253 = ₽140,747
Every extra manual run adds to the yearly spend. Spend on SettleOps grows much more slowly — most of it goes on integration and maintenance.
Runs a week4 runs a week
SettleOps saves ₽1,755,053 over your own scheduler in the first year.At 4 runs a week, SettleOps saves ₽140,747 over manual runs.
Calculation assumptions
Your own scheduler: development while runs are done 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.