Split the money once a deal is done
Take the payment right away and split the money once the deal goes through.
Your product makes the call on the deal. SettleOps carries out the money actions it needs and sees them through to the end.
Operation ₽12
on a marketplace, ₽18,400
payment, decision, split
6 h timeout
Work out what splitting the money on deals will cost in the first year.
Enter your own figures.
Deals: a week, each one a single SettleOps operation.
That is ≈ 433 SettleOps operations a month.
Manual work
Tracking the decision by hand and starting the money actions takes min per deal.
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 deals 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.
Accepting the payment and holding the money until the deal is decided.
Waiting for the decision with a timeout and a default action when none arrives.
The split: payouts to several parties in a set order.
Refunding the buyer on cancellation and reversing payouts already made.
Each payout exactly once: none skipped when a server fails and no double payout.
Tracking each deal 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.
For operations with an external decision, the first decision is included in the price; each additional one costs ₽12.
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,493,750, manual splitting ₽812,500, SettleOps ₽558,565. Manual splitting is cheaper below 62.8 deals a week.
When does SettleOps pay off?
First year at 100 deals a week
SettleOps is cheaper by ₽1,935,185
SettleOps₽558,565Calculation details
Your own code — ₽2,493,750
development: 3 mo × ₽300,000 = ₽900,000
code maintenance: 0.5 engineers × ₽300,000 × 9 mo = ₽1,350,000
manual work: deals by hand while development lasts, then reviewing exceptional cases = ₽243,750
With SettleOps — ₽558,565
integration: 1 wk = ₽75,000
code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500
manual work: deals by hand while integration lasts ₽16,927 + reviewing exceptional cases ₽53,038 = ₽69,965
fee: ₽12 per operation (first decision included) × ≈ 5,092 deals over 11¾ mo after integration = ₽61,100
saving ₽253,935
SettleOps₽558,565manual workdevelopment and integrationcode maintenanceSettleOps feeSettleOps levelmore than with SettleOps
Calculation details
Manual splitting — ₽812,500
manual work: 0.25 h × ₽625 × 52 deals = ₽8,125 for each weekly deal, × 100 = ₽812,500
With SettleOps — ₽558,565
integration: 1 wk = ₽75,000
code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500
manual work: deals by hand while integration lasts ₽16,927 + reviewing exceptional cases ₽53,038 = ₽69,965
fee: ₽12 per operation (first decision included) × ≈ 5,092 deals over 11¾ mo after integration = ₽61,100
Threshold — 62.8 deals a week
at 100 deals a week — above the threshold: SettleOps is cheaper than manual splitting by 812,500 − 558,565 = ₽253,935
SettleOps is cheaper than manual splitting from about 63 deals a week.Exact threshold for the current figures: 62.8 deals a week.
Every deal handled by hand adds to the yearly spend. Spend on SettleOps grows much more slowly — most of it goes on integration and maintenance.
Deals a week100 deals a week
SettleOps saves ₽1,935,185 over in-house development in the first year.At 100 deals a week, SettleOps saves ₽253,935 over manual splitting.
Calculation assumptions
One deal is one SettleOps operation with one decision: the fee is ₽12 per operation with the first decision included, however many payouts the operation holds; the estimate has no additional decisions. A month has 52 ÷ 12 weeks.
Your system makes the call on the deal on every path, and the time spent on the business decision itself is not counted. Your own code and SettleOps take over starting payouts or refunds by hand and checking the result: the outcome arrives as a status and a webhook; only manual review of exceptional cases remains.
Your own code: development while deals 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.