A platform to run a fintech business: from the first payment to the regulator's report

14 payment methods: cards and saved cards; bank transfers, direct debit, open banking; e-wallets, Apple Pay, Google Pay; mobile money and USSD; QR codes and faster payment systems; BNPL instalments; crypto. Acceptance covers 170+ countries through 700+ connected providers, with settlement in 40+ currencies. The banking core ships with charts of accounts for 40+ countries, each matching local accounting requirements. There are three transaction types: acceptance, payouts and merchant operations — refund, capture, void.

The payment moves to the next channel in the cascade. You set the routing rules yourself: by currency, amount, country and card type, by weights across terminals, by priority with a fallback channel, by schedule, and by the provider's current availability. The platform tracks route health — success rate, response time, errors — and a channel that degrades stops receiving traffic. Reconciliation with the provider runs on a schedule and discrepancies show up in the register. Machine ranking of channels and aggregate provider scoring are catalogue modules.

It depends on whose money passes through your setup. You collect payment for your own goods and services — an online shop, a retail chain, a service: no authorisation is required. You need agreements with the providers you connect, and the platform gives you a single technical integration to all of them. You serve third-party merchants: you need your own agreements with acquirers, providers and banks. The requirements for your status are set by the jurisdiction you work in. You operate under your own brand on an upstream operator's channels: no channel agreements of your own are needed. The rate here is 0.5% and the monthly minimum 50,000 RUB. You hold client accounts and issue means of payment — neobank, bank, issuer: a licence is mandatory. We do not provide licences and are not a payment services operator.

You pay a percentage per transaction set by your pricing plan. The platform calculates the fee itself: a fixed part plus the amount multiplied by the rate, then a floor and a cap are applied. Starter — 0.20% plus 1 RUB per transaction; fee from 2 to 1,000 RUB; turnover up to 100 million RUB a month. Business — 0.15%, no fixed part; fee from 1 to 200 RUB; turnover up to 1 billion RUB. Scale — 0.10%, no fixed part; fee from 0.6 to 100 RUB; turnover up to 5 billion RUB. Enterprise — 0.07%, no fixed part; cap 60 RUB; no turnover limit. The percentage applies to payment acceptance and payouts. Refunds, captures and voids carry no percentage: on Business, Scale and Enterprise they are free, on Starter they cost 1 RUB. The rate is charged on top of the fees of your acquirers, providers and banks, not instead of them: it pays for the platform, not for moving the money. Onboarding is free, the sandbox is free, and there is no subscription fee. Turnover above the plan limit blocks nothing — the limit marks the segment rather than capping your work.

It replaces a subscription fee. One rule sets it: a quarter of what building the same thing yourself would cost you. The month is billed at the greater of the two figures — the minimum or the percentage of turnover. Community or mutual-aid fund: 9,000 RUB up to 300 members, 25,000 RUB up to 3,000, 50,000 RUB above that. Your own brand on an upstream operator's channels: 50,000 RUB at a 0.5% rate. Large business running its own revenue: 500,000 RUB. Payment operator with third-party merchants: 600,000 RUB. Neobank: 700,000 RUB. Licensed bank: 1,000,000 RUB. Each minimum corresponds to an included turnover — the minimum divided by the plan rate. At a 600,000 RUB minimum and a 0.15% rate the percentage overtakes it from 400 million RUB of monthly turnover, and beyond that you pay the percentage alone. The bonus from implementation work is charged against the monthly minimum on the same footing as fees.

With your first successful transaction in the live environment. There is no amount threshold. Registration, the wizards, the test environment and acceptance runs are free and start no clock. The launch month is prorated by days: start on 20 September and you pay 11/30 of the minimum for September. Unused included turnover does not carry over: the payment covers a month of the platform running, not a bundle of transactions. We earn on your transactions, not on a subscription.

The rate covers the platform: the integration library, routing, the accounting core, reconciliation, anti-fraud, the operator back office, the sandbox, the API, event notifications and support at the level of your plan. Catalogue modules are charged separately — 14 of them at 7,000–45,000 RUB per month, with a trial period of 7, 14 or 30 days, switched on and off by you. They cover advanced routing and provider scoring, corporate single sign-on, document and statement recognition, programmable payments, a P2P FX order book, participatory finance, asset tokenisation, blockchain operations, BPMN processes, an operator assistant, a regulatory pack for Saudi Arabia, the UAE and Malaysia, Islamic finance, and infrastructure bonds. All fourteen together cost 244,000 RUB a month. Implementation work is charged by the hour: 10,000 RUB per engineer-hour, 15,000 RUB per consultant-hour, minimum order 8 hours. Half of what you pay comes back as a bonus on your deposit and goes towards day-to-day operation. Outside our scope are your channels' fees, your authorisations and regulatory reporting, an adapter to a provider outside the integration library, migrating history from a previous system, training beyond the included volume, physical card production, your own blockchain nodes, and interface work deeper than the logo and brand colours.

Nearly everything. The default path is self-service. You register and create your organisation through a step-by-step wizard: organisation and branding, pricing plan, settlement currency, team members, referral programme. Then you go through the wizards your scenario calls for: processing setup, routing cascade, publishing the payment form, importing statements for reconciliation, working under your own brand, the risk engine and limits, card issuing, launching a bank, corporate single sign-on, dCLS participant, participatory finance partner. Catalogue modules you switch on and off yourself; the platform checks dependencies on activation. The wizards were written from the record of onboarding the first operators: what our engineer used to do by hand, the operator now does alone. We step in where the setup is complex: banking, card issuing, non-standard integrations, data migration, installation on your own infrastructure.

The timeline is set by the complexity of your setup and the readiness of your side. There is no queue on ours. Once you have completed the organisation wizard and the processing setup wizard, the environment already works: the organisation exists, the plan is assigned, the terminal is configured, the payment form is published. What remains is to connect a provider under your own credentials and run a transaction in the sandbox. Going live is a matter of switching over. You choose how to integrate: the API with event notifications, the ready-made payment form, or a payment link. For banking and card programmes the timeline is set by your bank and your card producer.

Contractual availability is 99.95%. The API rate limit depends on the plan: 100 requests per second on Starter, 500 on Business, 2,000 on Scale, individually agreed on Enterprise. Support: email on Starter, priority on Business, a dedicated line on Scale and Enterprise. Enterprise adds service levels written into the contract, a personal manager and custom billing. Analytics come with Business, reports in your own formats with Scale. Event notifications and the dashboard are on every plan.

Yes. The payment form, the partner cabinet and the payment pages run on your domain, with your logo and brand colours. Neither your merchants nor your payers see our brand. Branding is set up through its own wizard and does not depend on us. Changes deeper than the logo and colours are interface work and are charged by the hour.

Ours is the platform. The card environment is certified to PCI DSS Level 1 — there is a report and an attestation from an external auditor, and it narrows your own assessment scope. Card data is tokenised and never stored in the clear. Organisations are isolated from one another, permissions are split across 7 roles and 30+ granular rights, user actions are written to an audit log, and data residency is chosen to match your jurisdiction. Information security controls follow ISO 27001 and SOC 2, personal data handling follows GDPR across 30+ jurisdictions. Open banking follows PSD2, Islamic products follow AAOIFI standards, and crypto-asset operations account for MiCA. Yours are the regulator's authorisations, membership in payment schemes, channel agreements, reporting and the certification of your own legal entity. Preparation for certification and legal support come under a separate agreement. They are not part of the platform fee.

A payment environment of your own costs at least 2.5 million RUB a month: four engineers and an operations specialist — 1.8 million, information security — 225,000, infrastructure — 400,000, maintaining certification — 100,000. That figure does not shrink in a weak month along with your revenue. The monthly minimum is a quarter of it. At scale you pay market rates of 0.07–0.20%. Building your own starts to pay off at around 1.7 billion RUB of monthly turnover. Below that threshold it costs more than the platform. Beyond the money there is time: the integration library, reconciliation, anti-fraud and certification have to be maintained every month, not just written once.

On a prepaid basis. Your organisation holds a deposit that you top up in advance. Everything is charged against it: transaction fees, module subscriptions, the monthly minimum. The platform checks the balance before processing a transaction. If the money is not there and no overdraft has been agreed, the transaction does not go through. You set the warning threshold yourself and an email goes out as it approaches. An overdraft is a matter of agreement; its size is fixed in the contract. When you work in several currencies, a separate deposit is held for each: rouble fees are charged against the rouble deposit, dollar fees against the dollar one. Nothing is converted at the moment of charging, so no dispute about the exchange rate can arise.

Yes, through an annual licence for installation inside your perimeter. Basic — 18,000,000 RUB per year: payments, payouts, transaction register, subscriptions, payment links, wallets; up to 3 organisations, up to 1 million transactions per month, up to 5 connected channels. Extended — 21,600,000 RUB per year: routing and the event log on top of Basic; up to 10 organisations, up to 10 million transactions, up to 20 channels. Corporate — from 36,000,000 RUB per year, with scope and limits set by contract. The licence costs three times the annual cloud subscription for the same profile: in the cloud the payment grows with your turnover, while the licence is fixed for the year and does not depend on how much you process. Support and updates cost 20% of the licence per year, the first year included. Without active support the licence is not renewed. Installation and data migration are charged by the hour. The platform itself checks the module scope, limits, term and regions at start-up. This option is for cases where data cannot leave your perimeter.

A banking core: accounts, general ledger, deposit and lending products, treasury, card issuing, compliance and regulatory reporting — for a neobank and for a licensed bank. Charts of accounts are ready for 40+ countries. Profit-sharing and interest-free finance for cooperatives, mutual-aid funds and collective funding platforms. Open banking under PSD2 in the third-party provider role: client consents and access to their accounts held at banks. Foreign-exchange settlement on a payment-versus-payment basis with netting windows. Asset tokenisation, blockchain operations and a wallet under your brand. BPMN processes with decision tables, document and statement recognition, an operator assistant. All of it runs in the same environment and the same back office: moving from accepting payments to banking products does not mean changing supplier. Some directions are catalogue modules; the mix and the order of introduction follow your scenario.