Cut payment layer development costs
Cut development and maintenance costs.
Your 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.
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.