Skip to content

Internet banking software for retail, SME and corporate customers

We build internet banking that gives individuals, SMEs and corporates each the experience they need, from a quick transfer to bulk payroll approved under the company mandate, connected to your core banking system.

What changes

  • Corporate customers pay suppliers and staff in bulk, approved by the right signatories, without visiting a branch.
  • Requests that used to arrive as letters arrive as tracked workflows your teams can act on.
  • Finance teams see their balances and positions across accounts in one view.
  • Individuals and SMEs get a simpler experience that works on any screen.
An officer at a back-office desk marks a printed list with a pen, with a spreadsheet open on the screen

What’s included

  • Separate experiences for retail, SME and corporate customers
  • Bulk payments uploaded from a file, and scheduled payments
  • Maker-checker and multi-level approvals that follow each company's mandate
  • Standing orders that customers set up and manage themselves
  • Service requests, including trade-finance requests such as letters of credit, as tracked workflows
  • Liquidity views across accounts, with sweep instructions
  • Bill payments, transfers to mobile money and other banks, and statements
  • Responsive design for phone, tablet and desktop
  • An admin portal for onboarding, mandates, limits and support
  • Integration with your core banking system through its own interfaces

How it runs

  1. Step 1

    Discovery

    We map your customer segments, products, mandates and core banking interfaces, then agree scope and price in writing.

  2. Step 2

    Design

    Journeys for each segment, approval rules, limits and request workflows are agreed with your business, operations and IT teams.

  3. Step 3

    Build and test

    We build against a test copy of your core and test with your teams, including rejected approvals, partly failed bulk files and expired sessions.

  4. Step 4

    Launch and hand over

    A pilot group of customers first, then the wider roll-out, with runbooks and training for the teams who will support it.

Different customers, different banking

An individual logs in to check a balance and pay a bill. An SME owner pays a few suppliers and checks who has paid them. A corporate finance team uploads the monthly payroll, waits for two directors to approve it and needs to know what is in every account before noon.

One design cannot serve all three well. We build internet banking with a shared engine and a separate experience for each segment.

For corporate customers

  • Bulk and scheduled payments. Upload a payroll or supplier file, check it before it goes, or schedule a payment for a later date.
  • Approvals by mandate. Maker-checker and multi-level approvals that follow each company’s signing rules, by amount and by type of payment.
  • Standing orders. Set up, change and stop recurring payments without a branch visit.
  • Service requests. Trade-finance requests such as letters of credit, and other requests that used to arrive by letter, run as tracked workflows. Your team works them and the customer can see where each one stands.
  • Liquidity. A view of balances across accounts, with sweep instructions to move funds between them.

For individuals and SMEs

Transfers, bill payments, statements and payments to mobile money with M-Pesa, Airtel Money, MTN MoMo, Orange Money and other mobile money operators. Payments to other banks go through banks with open APIs or your switch. The design is simple, and it works on a phone, a tablet or a desktop.

For your bank

An admin portal for your teams: onboarding customers and companies, setting up mandates and limits, resetting access and seeing what customers see when they call for help. Every action in the portal is logged.

Connected to your core

Internet banking reads and posts through the interfaces your core banking system already exposes, agreed with your vendor and your IT team. If you are building several channels at once, a shared API layer keeps the rules in one place. See our mobile banking service and WSO2 integration.

Start with discovery

Tell us which customers you want to serve first and which core banking system you run. We reply with the questions that decide scope and cost, then agree a discovery phase with your team.

Common questions

Why separate retail, SME and corporate experiences?

Because they need different things. An individual wants to pay a bill quickly. A corporate finance team wants bulk files, approvals by mandate and a view of every account. Putting both in one design makes it worse for each, so we share the engine and separate the experience.

How do approvals work for corporate customers?

Each company's mandate is set up in the admin portal: who may create a payment, who may approve it, in what order and up to what amount. A payment is released only once the mandate is satisfied, and every step is recorded.

Can customers request a letter of credit online?

They can start the request online. Trade-finance and other service requests run as workflows: the customer submits the details and documents, your team works the request and the customer sees its status. The decision stays with your trade-finance team.

Does it connect to mobile money?

Yes. Customers can pay to M-Pesa, Airtel Money, MTN MoMo, Orange Money and other mobile money operators through each operator's API under your agreements, and to other banks through banks with open APIs or your payment switch. Settlement is reconciled against bank statements.

How much does internet banking cost?

It depends on the segments you serve, the features you need first and your core banking interfaces, so we price after a discovery phase. You get a written scope and price before work starts.

Planning a core banking or payments project?

Tell us what you are planning. We scope core banking, payments and identity work with your own IT team, starting with a discovery phase.