Revolut Clone Development Company: How to Choose One
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.
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.
Typical scoping questions
Replay a failed webhook in front of me
- Provider events fail, duplicate and arrive out of order - reliably, in production. If there is no replay mechanism, recovery after a provider outage is manual reconciliation across every affected account.
Change a balance, then show me why
- An admin adjustment should be impossible without a recorded reason attached to the actor. If the console lets someone move money silently, you have no answer for an auditor or a disputing customer.
Log in as support and try to reach the ledger
- Role-based access has to actually block, not merely hide menu items. Ask them to demonstrate the denial, not the absence of a button.
How would I change BaaS provider?
- If the answer involves touching business logic rather than configuration, then your provider relationship - which will end at some point - is welded to your product.
Show me a reconciliation against the provider
- Your ledger and theirs must agree. Ask how divergence is detected and what happens when it is found; "it shouldn't happen" is not an operational answer.
Are balances held per currency?
- Or is there one balance with a conversion applied at display time? The second hides FX exposure and makes the spread you earn impossible to account for cleanly.
What is the transaction boundary on a transfer?
- A ledger entry and a balance update must succeed or fail together. If they can diverge, you will find out during a reconciliation rather than at the moment it breaks.
Is any of the source encrypted?
- Ask directly, and about licence callbacks. In a regulated product, a vendor kill switch is a concentration risk your compliance function will eventually raise.
What is not included?
- Ours is published as the Enterprise tier, and includes the plain statement that we cannot supply your licence, your BaaS relationship or your compliance programme.
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.
Red Flags That Mean Walk Away
If you hear any of these, stop
- "We'll help you get licensed" Software vendors do not obtain authorisations. A firm blurring that line is either overselling or does not understand the regulatory perimeter - and both are disqualifying in this category.
- "Webhooks just work" They do not. They fail, duplicate and arrive out of order, and a team that has not built for that has not run payments in production.
- "Admins can adjust balances" Not without a recorded reason, an actor and a role scope. Silent balance adjustment is the single clearest sign that governance was an afterthought.
- "One currency now, multi-currency later" Holding balances per currency is a ledger decision. Retrofitting it onto a live product with real money in it is not a feature addition, it is a migration with regulatory consequences.
What We Do Not Supply
Stated plainly, because in a regulated category the boundary between software and permission is the most important thing on this page.
We do not supply your licence
- Whether you hold an EMI, payments or banking authorisation, or operate under a sponsor bank or licensed BaaS partner, is entirely yours. The platform is software and confers no permission. This decides your product scope before any configuration does - settle it before you build.
We do not supply the BaaS relationship
- Five-plus providers are supported behind the routing layer. Being accepted by one, and the commercial terms you negotiate, are yours - and those per-account and per-transaction terms are your actual unit economics.
Treasury and capital are yours
- Regulatory capital, safeguarding customer funds in segregated accounts, and managing float across currencies are balance-sheet and treasury functions. No software supplies them, and they are usually the largest commitment in the plan.
- This preview supplies no ISO 27001 or SOC 2 evidence; no certification is claimed here. The architecture is specified so evidence gathering is possible - audit logs, reason-based actions, role scoping - but certification is a separate programme with its own auditor.
- A vendor who is precise about this boundary is more useful than one who implies they can shorten a regulatory timeline. Nobody can.
A partner who knows where software ends
Named fintech deployments, a control plane built for audit, provider abstraction that survives a relationship ending, and a plain statement of what we cannot supply.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Revolut.
More pages on this build
Overview
The full proposal on one page.
Features
Every proposed capability grouped by who touches it.
Business model
How a platform in this category earns, and which lever to switch on first.
Cost
What actually moves the budget, and how a scope-first written quote is put together.
Company
Agency versus freelancer versus Omnistu, plus the checks to run before hiring anyone.
You are hereOmnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Revolut.
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.
