SettleOps

Marketplaces

Launch new money scenarios faster. Whether or not you already have your own payment layer

Bring new capabilities to market fasterUse a ready operations layer instead of building one.

SettleOps is an SDK for the scenario in your code, a control panel for money movement, recovery after failures and ready connections to rails.

Enter your own numbers

An engineer costs ₽ gross per month.

With SettleOps: engineer for 1 week.

On your own payment layer: engineer for – months.

From scratch: engineer for – months.

Salary costs before launch: with SettleOps, 1 week, ₽75,000; on your own payment layer, 1–2 months, ₽300,000 – ₽600,000; from scratch, 6–12 months, ₽1,800,000 – ₽3,600,000.

The estimate covers salary costs only. Infrastructure, taxes and employer contributions, management, operations and support are not included.

One person-week to integrate with SettleOps allows for business logic changes on your product’s side; it is not a guaranteed launch date.

First-year cost

Volume: operations per month.

SettleOps tariff — ₽12 per operation of any type.

Payments, refunds and payouts are charged separately.
The fee depends on the payment method and the payment system.
More about pricing.

Engineer load per month for code maintenance:
with SettleOps , on your own payment layer , from scratch .

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.

On your own payment layer: maintaining the new scenario, fixing bugs, handling failures, updating integrations and tests.

From scratch: maintaining the whole operational layer, including scenarios, payment system integrations, fault tolerance and monitoring.

The estimate covers salary costs of engineering maintenance after launch within the first 12 months. It excludes infrastructure, taxes and employer contributions, and fees for money actions.

Suppose the revenue from your product is ₽ per month.

SettleOps launchSettleOps tariffbuilding your own solutionduration rangemaintenancethe product earns

The comparison covers development, maintenance and use of the operational layer.
Fees for payments, refunds and payouts are not included.

First-year cost: with SettleOps ₽1,837,500; on your own payment layer ₽1,950,000 – ₽2,100,000; from scratch ₽3,600,000. Revenue over 12 months: with SettleOps ₽3,525,000; on your own payment layer ₽3,000,000; from scratch ₽0.

What this means for your business

Example for 10,000 operations per month

Cost per operation with SettleOps

₽15.64

Cost on your own layer

₽19.5–21

Cost from scratch

no operations

within the first 12 months this path does not launch

With these parameters, SettleOpsreduces the estimated cost of the operational layerby ₽112,500 – ₽262,500 compared with your own layerand by ₽1,762,500 compared with building from scratch over 12 months.

Cut development and maintenance costsYour team focuses on product business logic, SettleOps handles the routine.

Your team can maintain only the product business logic code.
Delegate everything else to the operational layer.

Put in your own numbers

An engineer costs ₽ gross per month.

Engineers per month on code maintenance:
with SettleOps , on your own payment layer .

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.

On your own payment layer: maintaining the whole operational layer, including scenarios, payment system integrations, fault tolerance and monitoring.

The estimate excludes infrastructure, taxes and employer contributions.

Volume: operations per month.

SettleOps tariff — 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.

Maintenance costs: with SettleOps ₽150,000 per month, ₽1,800,000 over 12 months — maintenance ₽30,000 and tariff ₽120,000; on your own payment layer ₽300,000 per month, ₽3,600,000 over 12 months.

Maintenance costs

code maintenanceSettleOps tariffsaving

With these numbers, SettleOpscuts the cost of maintaining the payment layerby ₽150,000 per month — ₽1,800,000 over 12 months.

The comparison covers engineer costs for code maintenance and the SettleOps tariff.
Fees for payments, refunds and payouts are not included.

Reduce manual workSettleOps executes money operations automatically and handles failures by the rules you set,
and shows money movement in one place.

SettleOps takes repetitive money work off your staff.

Work out what share of manual work SettleOps has to take off to pay for itself.
Enter your volumes, handling time and hourly cost.

Volume: operations a month.

SettleOps fee — 12 ₽ per operation of any type.

All manual work — ₽340,104 a month, reduction potential — ₽286,875; spend on SettleOps — ₽120,000, 42% of the potential.

Failure handling

Tick the failures your staff handle by hand and enter how many there are a month and how many minutes each takes.

Handled by handFailure typeA monthHours a monthWhat SettleOps does
Temporary bank errors cases at min40 hAutomatic retries under the retry policy
Provider unavailable cases at min20 hSwitch to the backup route
Unknown payout result cases at min26.7 hPolls the bank to find out the result
Final refusalif the operation now has to be closed by hand cases at min20 hRecords the result and closes the operation by its rules
Wrong payment details cases at min12.5 hNot fixed automatically: a person has to step in
Total119.2 h

Failures are handled by engineers: ₽ gross a month per person, an hour — ₽1,875.

Stuck operation control

Tick the waits your staff track by hand and enter how many checks and decisions there are a month and how many minutes one check or decision takes.

Handled by handWaiting forA monthHours a monthWhat SettleOps does
Payment not received in time checks at min13.3 hPayment deadline: when it passes, the operation is closed under the timeout policy
Operation stuck at the bankunless counted under failure handling checks at min6.7 hPolls the bank and tracks the deadline: when it passes, closes or compensates under the timeout policy
Operation waiting for a business decisionremind, watch the deadline checks at min13.3 hReports by webhook that a decision is needed; at the deadline, acts under the timeout policy
The business decision itselfconfirm, cancel, refund decisions at min6.7 hMakes no business decisions: the decision stays with you
Total40 h

Stuck operations are handled by operations staff: ₽ gross a month per person, an hour — ₽625.

Finding out operation status

Tick what support looks up by hand to answer a customer and enter how many requests there are a month and how many minutes one takes.

Handled by handWhat they look upA monthHours a monthWhat SettleOps does
Status the customer can see themselvesif your product shows status via the SettleOps API; do not count these requests below requests at min15 hStatus via API and webhooks: your product shows it to the customer, no request arises
Did the payment go throughlooked up in the bank, payment gateway, logs requests at min15 hShortens the search: status of the operation and its payments in the console
Where is the payout or refund requests at min16.7 hShortens the search: status of each money action in the console; SettleOps finds out the result at the bank itself
What has already been doneretries, switches, cancellations requests at min12.5 hShortens the search: execution history — what, when and why — in the console
Reply to the customercounted separately from the search requests at min20 hDoes not talk to your customers: the reply stays with support
Total79.2 h

Operation status is looked up by support: ₽ gross a month per person, an hour — ₽500.

Related money actions

Tick the money actions your staff start by hand and enter how many there are a month and how many minutes one takes.

Handled by handWhat they startA monthHours a monthWhat SettleOps does
Payout after order confirmation actions at min16.7 hExecutes the payout on a decision from your system and makes sure it completes
Refund after cancellation actions at min16.7 hExecutes the refund on the cancellation decision; if the bank declines, follows the compensation policy
Extra charge or partial refundthe order amount changed actions at min12.5 hAdds actions to the operation on your decision and executes them
Recurring charges and payoutssubscriptions, scheduled payouts actions at min12.5 hStarts operations on a schedule
Recording in accountingentries in the accounting system entries at min25 hDoes no bookkeeping: accounting entries stay with finance
Total83.3 h

Related actions are started by finance: ₽ gross a month per person, an hour — ₽625.

When does SettleOps pay off?

Example for 10,000 operations a month

All manual work

321.7 h

a month · ₽340,104

Reduction potential

257.5 h

a month · ₽286,875

Break-even threshold

42%

fee ₽120,000 a month

failure handling: ₽223,438stuck operation control: ₽25,000finding out operation status: ₽39,583related money actions: ₽52,083needs a person: ₽53,229

SettleOps pays for its fee if it cuts at least 42% of the manual work potential.How much of the work can really be automated, we will find out in a pilot.

Calculation assumptions

Model: 160 working hours a month; an hour of staff time is their cost divided by 160.
The simplified formula assumes an automated case needs no more manual effort. Cases that require a person are not part of the reducible share.
Freed time does not necessarily mean a direct cut in costs.

Add a ready backup operations layer out of the boxIf your own money-handling code starts throwing errors,
switch operation processing to SettleOps.

SettleOps picks up new operations
when your code starts failing.

Work out how many failures SettleOps has to prevent to pay back the integration.
Enter your volumes, margin and failure figures.

Operations a month , average ticket ₽.

Contribution margin on operations — %.

One failure lasts h, failures a year — .

Share of operations lost — %.

An engineer costs ₽ gross a month.

Integrating SettleOps and describing business logic with the SettleOps SDK

engineer for week.

How to estimate the integration effort

Estimate the changes to your product’s code.
Specifically, how long it takes to build the code that switches operation processing to SettleOps with the SettleOps SDK.

SettleOps fits you if it supports the scenarios you need, recurring payments for example.

Switching new operations must be built and tested in advance.

Operations already started are not moved automatically.

Say your code switches traffic to SettleOps in minutes.

SettleOps fee — ₽12 per operation of any type.

One failure: ₽11,111 of profit lost without a backup, ≈ ₽9,792 prevented. The integration, ₽75,000, pays off at failure 8.

When does SettleOps pay off?

Example for 10,000 operations a month, a 4 h failure

Loss from one failure

₽11,111

without a backup, new operations stall

Losses prevented

≈ ₽9,792

per failure: net of losses before switching and the fee

Break-even threshold

8 failures

integration ₽75,000 ÷ ₽9,792

preventable losseslosses before switchingfailures beyond your year — up to the thresholdintegrationfee

SettleOps pays back the integration if it prevents at least 8 such failures.With 4 failures a year, in about 2 years.

Calculation assumptions

Losses are the contribution margin on lost operations: operations × average ticket ÷ 720 h × margin × share of operations lost.

Losses prevented per failure are losses without a backup minus losses before switching and the fee for operations during the failure. SettleOps integration is engineers × weeks × engineer cost ÷ 4.

Backup maintenance and fees for money actions are not included. With other figures the result may be considerably better or worse. If operations can be carried out later without losing profit, the economic benefit of a backup is smaller.

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.

Discuss a pilot