How we built the oneBanking app: everyday banking in one mobile app

What is oneBanking?

oneBanking is a fintech from Malta. Its idea is one mobile experience for everyday banking instead of several apps, with tiered plans that give each customer the access the plan covers and an AI assistant inside the app. On its website the client states that the assistant "never moves your money without asking first". We quote this as the client's statement.

The client's website also lists some functions, such as a European IBAN account and cards, as planned and not yet available. This page does not claim them.

What did S-PRO build?

S-PRO built the entire application. In the client's own words on its website, oneBanking chose "this Swiss-based engineering company for their proven track record in fintech and regulated industries". S-PRO's engineers work from Zurich and Łódź, our R&D centres.

We do not publish the split of components, delivery time, team size or technology stack for this project.

Who else stands behind the product?

According to the client's website, oneBanking works with two outside specialists next to engineering:

• DATAMI, a cybersecurity firm that the client brought in to audit the app.
• Lemur Legal, which the client describes as "The legal minds behind our startup."

Both statements come from the client's website. S-PRO makes no claim about the audit result and no statement about the client's legal or regulatory status.

How do you keep an AI assistant under control near money?

This is S-PRO's own view of good design for any assistant that sits next to payments. The assistant can prepare and suggest, and a person confirms every action that moves money. Three consequences for the build:

• confirmation is a step in the flow, with its own screen and log entry, not a message the assistant writes;
• what the assistant may read and what it may only propose are separate permissions;
• the same entitlement rules that decide what a plan includes also decide what the assistant may offer.

Where does the product stand today?

Pre-launch. The client's website calls the beta "coming soon" and describes the app as running with simulated funds. As of 5 November 2026 we know of no public launch date. We claim no users, transactions or revenue, because there are none to report.

What can other fintechs take from this?

Our view, from building banking software for regulated firms:

1. Design the confirmation first. If an assistant, a rule or a plan limit can touch money, specify the confirmation step before the feature.
2. Treat plan tiers as access control. Several tiers mean several sets of entitlements. Build them as one rule set that the app, the back end and any assistant all read.
3. Plan the external review. An independent security audit and a legal adviser are easier to work with when the platform is built for them: logged actions, clear boundaries, no hidden paths.
4. Say what is live. A pre-launch product should describe itself as pre-launch.

What's next?

The next milestones are the client's. We will update this page when oneBanking publishes them. If you plan a similar platform, see banking software development, our digital banking offer and our work for fintechs. For a published example of a digital front end layered over a core system, read the New Horizon Bank case.