PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Feature scope - proposed scope

Revolut Clone Features: The Control Plane Is the Product

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
01 / Scope areas

Scope areas for this kind of build

The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.

02 / Feature Set by Role

Feature Set by Role

Three distinct products in one platform - a consumer banking app, a business finance suite, and the Banking Core that governs both. Most fintech scripts build the first and stop.

Retail Customer

  • Multi-currency accounts across the currencies agreed in scope
  • Balances held and viewed per currency
  • FX conversion between held currencies
  • Physical and virtual card issuance

Business Customer

  • Business accounts alongside the retail product
  • Invoicing and receivables tracking
  • Payroll and bulk transfer workflows
  • Expense management and spend controls

Banking Core Operator

  • Reason-based admin actions - nothing changes anonymously
  • Full audit log across accounts, transactions and decisions
  • Role-based access control per module
  • BaaS provider configuration and routing
03 / How It Works

How It Works, End to End

A customer from onboarding to a cross-currency card payment, traced through every provider hop and every record the platform writes.

Onboarding, with the provider behind it

  • A customer signs up and an account is provisioned through whichever BaaS provider you have routed that product to. Because the provider sits behind a configurable layer rather than in the application logic, the customer experience does not change if you later route somewhere else.

Currency balances, held separately

  • The customer holds balances in each of the currencies they use rather than one balance with a display conversion. That is the structural difference between a multi-currency product and a single-currency one wearing a currency selector.

Conversion happens at your spread

  • FX conversion between held currencies runs at rates and spreads you configure in the Banking Core. This is a primary revenue line rather than a convenience feature, so it is an operator setting rather than a hardcoded value.

A card is issued and provisioned

  • Physical or virtual, issued through the provider, with controls, limits and freeze available to the customer. Card programme management sits in the Banking Core, so limits and product rules are operator-set rather than per-customer support work.

The provider fires a webhook, and it is handled properly

  • Authorisation, settlement and status events arrive asynchronously - and sometimes late, out of order or twice. The platform handles them with replay operations and provider-event synchronisation, so the ledger converges on truth rather than on whichever event arrived last.

A business customer runs the same money differently

  • The same accounts and ledger underneath, but wrapped in invoicing, payroll, expense and vendor workflows with multi-step approvals. Business finance is not a separate product here, which is what lets one customer graduate from personal to business without leaving.

An operator intervenes, and says why

  • Every admin action - a limit changed, an account frozen, a transaction reversed - carries a reason and lands in the audit log against the staff member who took it, scoped by their role. That record is what a regulator, an auditor or a disputing customer is eventually shown.
  • Steps five and seven are where fintech products are actually judged. Anyone can move money once; the question is whether you can explain every movement afterwards, including the ones a human intervened in.
04 / Why these

Every Feature Earns Its Place

Feature lists are cheap. These exist because a specific thing goes wrong in a banking product without them.

Seven of these ten are governance rather than features. That ratio is correct for a banking product, and a vendor whose list is all interface and no control plane has built the easy half.

05 / Technology

The Technology Behind the Features

Choices made for auditability and extensibility rather than novelty.

Why TypeScript and PostgreSQL rather than something faster to write

  • Financial software is read far more often than it is written, and it is read under pressure - during a reconciliation break, an incident or an audit. A typed API layer makes the money-moving paths explicit rather than implicit, and PostgreSQL's transactional semantics are what would let a ledger entry and a balance update succeed or fail together in the proposed design. Neither choice is exciting. Both are the reason the platform can still be reasoned about in year three, which in this category matters more than development velocity in month one.
  • Complete source transfers to you at handover, with rebranding and white-labelling included.
06 / Boundaries we state

Boundaries we state in writing for your build

Enterprise scope, or yours to own

  • A banking licence, or a sponsor who has one The platform is software. Whether you hold an EMI, banking or payments licence in your jurisdictions, or operate under a sponsor bank or licensed BaaS partner, is entirely yours - and it decides what you are legally permitted to offer. Settle it before you build.
  • The BaaS provider relationship itself Five-plus providers are supported behind a configurable layer. Being accepted by one, and the commercial terms you get, is a negotiation you own.
  • Regulatory compliance programme The platform provides audit logs, reason-based actions, RBAC and governance workflows - the evidence layer. Your compliance policies, reporting obligations, and the people running them are yours.
  • Card scheme certification Card issuance runs through your provider. Scheme-level certification and the associated programme management sit with them and with you.
07 / More pages

More pages on this build

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Revolut.
Revolut Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Revolut, and how clients search for it.
Revolut and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.

08 / Next step

Discuss your scope by message

Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead