PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
01 / Development cost

Revolut Clone Development Cost: Licensing Costs More Than Code

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.

No fixed prices are published. The factors below drive cost; a written quote follows a scope discussion by message.

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
02 / 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.

03 / What Moves the Number

What Moves the Number

BaaS integration depth

  • Five-plus providers are supported behind the routing layer. Integrating a provider outside that set, or supporting several simultaneously with failover between them, is scoped work - and worth it if your licensing route depends on a specific partner.

Infrastructure and scale

  • A single-region deployment on your cloud is proposed. Multi-region, high-availability topologies and advanced analytics are Enterprise scope - and in a regulated product, data residency requirements often force this conversation early.

Deeper governance

  • Four-eyes approval on defined operations, maker-checker workflows beyond the base and bespoke compliance reporting are quoted separately. If your authorisation route names specific controls, scope them at the start.
  • Every one of these is listed on the hub as a factor before you buy. The tier boundary is published rather than discovered, which is the opposite of a price that grows once you have committed.
04 / A proposed launch process

A proposed launch process, without time promises

Define the first service area

  • Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.

Apply your branding

  • Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.

Set the commercial rules

  • Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.

Connect your own accounts

  • Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.
05 / 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.

06 / 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
07 / Beyond the quote

Hidden Costs to Plan For

Costs that can sit outside a development quote. Ask which of these each quote includes or excludes; what is proposed inside our scope is worked out in writing before work starts.

Authorisation or sponsorship

An EMI, payments or banking licence, or a sponsor bank arrangement. Application costs, legal support and a timeline measured in months rather than weeks - and it gates everything else.

Regulatory capital and safeguarding

Most authorisations require capital held and customer funds safeguarded in segregated accounts. That is money on your balance sheet you cannot deploy - a working capital commitment, not an expense.

Compliance headcount

A compliance officer, an MLRO or equivalent, and the people doing ongoing monitoring. Regulators expect to see named, qualified individuals rather than a process document.

BaaS per-account and per-transaction fees

Your provider charges for accounts, cards, transactions and FX. Model these against your own pricing carefully - the margin between what they charge and what you charge is your actual unit economics.

KYC and screening per check

Identity verification, sanctions and PEP screening, and ongoing transaction monitoring are priced per check or per customer. They scale with growth, including with customers who never transact.

Card scheme and issuance costs

Physical card production, delivery, and scheme fees, plus the programme management your provider requires. Physical cards in particular carry a real per-unit cost.

Fraud losses

A cost of doing business in payments rather than an exception. Budget a loss rate from day one; the card controls and limits in the platform reduce it but do not remove it.

Audit and assurance

External audit, penetration testing and, where your customers demand it, ISO 27001 or SOC 2 certification - each a programme with its own auditor and its own annual cost.

Where the money comes back from

FX margin, transfer fees, card economics, subscription tiers, business finance modules and BaaS provisioning - and which to switch on first.