Retail Omni-Channel Digital Banking

Every channel your customers use. One platform, inside your bank.

A complete, ready-built digital banking front end: web, mobile, branch kiosk, wearables and an operations console. It plugs into your existing core, runs entirely inside your own datacentre, and works from day one, even before the core is connected.

Product screens use a fictional demo bank and fictional data. Phone screens show the responsive customer portal.

Customer web portal dashboard: total balance across Egyptian pounds and US dollars, accounts, savings goals, spending by category and recent activity.
Home screen at phone width: total balance and accounts. Cards screen at phone width: debit, credit and frozen cards. Payments screen at phone width: send money and saved beneficiaries.
5customer and staff channels on one platform
EN · AREnglish and Arabic on every channel, right-to-left native
On premiseruns inside your own datacentre, air-gap capable, with no cloud dependency
01 Why Benten

Your core systems work. The customer-facing layer is a decade behind.

Benten turns multi-day, branch-bound onboarding and servicing into minutes on any digital channel, without replacing your core and without moving your data to anyone's cloud.

01

A complete product

A proven, ready-to-deploy platform that your teams configure to your bank. Every installation runs the same product; what differs is configuration.

02

Your core stays the truth

Benten is never the system of record. We are the channels around your core, and every money movement commits on your bank's reply.

03

Runs inside your bank

One isolated install per bank on your own Kubernetes or Red Hat OpenShift. Air-gap capable, with no cloud dependency and no phone-home.

04

Works before the core is connected

Working stand-ins for every bank system let your teams test real journeys from the first week, then switch each one to your systems.

05

Configured by the bank

Products, fees, limits, texts and switches are changed in the back office under four-eyes approval, with no release needed.

06

Accurate by design

Customers see only the rates, fees and figures your bank publishes. Nothing is estimated or derived on the bank's behalf.

02 Product family

One architecture, many products.

A modular product family for banks and financial institutions. Start with one product and add the rest as you grow; each module can be bought on its own or as part of one platform.

Available

Available

Planned

Planned · H1 2027

Scheduled for release in the first half of 2027; final scope may vary.

03 Retail Omni-Channel Available

The same account, identity and security on every channel.

Real product screens, shown with a fictional demo bank. Each bank's own branding is applied by configuration.

Customer web portal

Self-service banking in the browser.

  • Full self-service banking in the browser
  • Responsive, accessible, English and Arabic
  • Bank branding applied by configuration
Customer web portal dashboard: total balance, accounts, savings goals, spending by category and recent activity.
04 What customers can do

Everyday banking, end to end.

Onboarding

  • Digital account opening with OTP and ID capture
  • National digital-identity (eKYC) verification
  • Self-enrolment for existing customers
  • Biometric login, devices and sessions

Accounts

  • Balances, history, net worth
  • E-statements by period
  • Spending insights and budgets
  • Savings goals with round-ups

Payments

  • Own-account, in-bank and domestic transfers
  • Instant payments by mobile number or alias
  • International transfers with charge choice
  • Standing orders, scheduled payments, status tracker

Bills and remittance

  • Bill payments and donations
  • International remittance through money-transfer partners
  • Saved beneficiaries with payee confirmation

Cards

  • Apply and activate
  • Freeze and unfreeze, channel controls
  • Set and change PIN
  • Pay the card, card transactions

Deposits and FX

  • Term deposits and certificates, with projection
  • Early-break preview
  • Live FX board, quote and exchange
  • Fees disclosed before the customer confirms

Loans

  • Public loan catalogue and calculator
  • Affordability, apply, offer and accept
  • Disbursement handled with the core

Investments

  • Mutual-fund shelf and orders
  • Suitability questionnaire
  • Switched on per bank, per licence

Service

  • Requests and disputes
  • Branch and ATM locator
  • Notifications centre and push alerts
  • Rewards balance and redemption

Planned · H1 2027 Mobile-wallet card tokenisation (tap to pay), card instalment plans and loan servicing (early settlement, restructure).

Back office review dialog for a pending change raised by another operator: domain, action, summary, submitter, reason, the value before and after, and Approve or Reject buttons.

Four-eyes approval: a fee change raised by one operator, reviewed by another.

05 The back office

Your teams run the bank's digital business from one console.

"Nothing consequential happens on one person's word."

Every sensitive change is made by one person and approved by another, and recorded in an append-only audit trail.

  • Unified work queueKYC review, account opening, card applications, loan decisions, requests and disputes. Claimed, owned and closed, with no item lost.
  • Four-eyes on every itemMaker-checker per item: no one approves their own change. Approvals inbox with full history.
  • Governed configurationProducts, fees, FX fees, pricing rules, limits, security policy, push templates, maintenance windows and the bank calendar.
  • Customer 360One view of the customer and their channels, channel access control, identity and KYC updates.
  • Money operationsSettlement reconciliation and replay, in-doubt transaction desks, corrections and refunds under approval.
  • Control and insightPer-channel product switches and maintenance, analytics and workforce KPIs, an access-control matrix mapped to your directory groups.
06 How it fits your bank

Integrate your back ends and configure. No custom build, no code changes.

All bank integration passes through one integration gateway to your enterprise service bus. Your core and card systems remain the source of truth.

Benten reference architecture Customer channels reach Benten through a customer edge, and bank staff through a separate operations edge on the intranet. Both sit inside the bank's own datacentre in front of the Benten platform. The platform reaches the bank's systems only through one integration gateway, which is never exposed to the internet, and then through the bank's enterprise service bus to core banking, the card system and other bank systems. CUSTOMERS Customer web iOS and Android Branch kiosk Wearables BANK STAFF · INTRANET Back officeconsole INSIDE YOUR DATACENTRE · ON PREMISE · AIR-GAP CAPABLE CUSTOMER PLANE Customer edge Internet-facing gateway OPERATIONS PLANE Operations edge Intranet only Benten platform One product, configured per bank Customer journeys Four-eyes approvals Microservices Kafka events Database per service Secrets vault Append-only audit ELK observability Local AI assistant Signed licence Kubernetes or Red Hat OpenShift One isolated install per bank INTEGRATION PLANE Integration gateway Never exposed to the internet Your ESB / middleware SOAP or REST YOUR SYSTEMS Core banking Card system Other banksystems Benten reference architecture Customer channels reach Benten through a customer edge and bank staff through an operations edge, both inside the bank's datacentre. The Benten platform reaches the bank's systems only through one integration gateway that is never exposed to the internet, then through the bank's service bus to core banking, the card system and other systems. CUSTOMERS STAFF Web Mobile Kiosk Wearables Back officeintranet INSIDE YOUR DATACENTRE Customer edgeinternet-facing Operationsedge Benten platform One product, configured per bank Customer journeys Four-eyes approvals Microservices Kafka events Database per service Secrets vault Append-only audit Local AI assistant Kubernetes or Red Hat OpenShift Integration gateway never exposed to the internet Your ESB / middleware · SOAP or REST Core banking Card system Other systems
Benten Your bank's systems Your datacentre
Shared foundations

What every Benten product has in common.

Inside your bank

On-premise on Kubernetes or OpenShift, air-gap capable, with your data never leaving your infrastructure.

Around your core

Your core and card systems remain the source of truth. We integrate through your middleware.

Configured, not customised

Every institution runs the same product. Products, fees, texts and rules are configured under four-eyes approval.

Secure and auditable

Separated network planes, vaulted secrets, encryption and an append-only audit trail in every product.

Licensed by module

One signed licence. Switch modules on as you grow, without reinstalling.

Built for Egypt and the region

Arabic and English, local payment rails and Central Bank requirements at the centre of the design.

07 Security by design

Built for a bank's threat model, designed against Central Bank requirements.

Strong customer authentication

  • In-app approval bound to the customer's registered phone
  • Unlocked by a secure PIN or biometrics; keys kept in the phone's secure hardware
  • Re-enrolling a new phone needs two independent proofs, with a cooling-off hold

Separated planes

  • Three network edges: customer, operations and bank integration
  • The integration edge is never exposed to the internet
  • Separate identity realms for customers and staff

Data protection

  • Secrets held in a vault, never in configuration
  • Field-level encryption of sensitive data
  • Card numbers, CVV and PIN are never stored by the platform

Privacy-safe notifications

  • Push alerts carry no names, amounts or account data
  • Marketing only with recorded, per-category consent
  • Customers can withdraw at any time

Accountability

  • Tamper-evident audit trail
  • Operator actions checked against capabilities
  • Signed, offline licence: no phone-home

Compliance programme

  • SOC 2 policy set approved
  • Controls mapped to Central Bank of Egypt cybersecurity requirements
  • Bank-specific artefacts for your own audits
08 How we engage

From a first conversation to customers on your channels.

Intro call

A short call to understand your channels, your core and card systems, and what you want to change first.

Demo against your scenarios

A walkthrough of the platform running against your own scenarios, on every channel and in the back office.

Start with one module

One signed licence key covers edition, term, seats and modules. Phase your rollout and switch modules on as you grow.

A typical path to go-live

  1. Install

    Install on your cluster and run every journey against Benten's stand-ins.

  2. Connect

    Connect your middleware, system by system.

  3. Configure

    Load your products, fees and branding through the back office.

  4. Pilot

    Pilot with staff, then open to customers by channel.

09 Talk to us

See the platform running against your scenarios.

Download the catalogue or the brochure, ask for a demo, or propose a time for an intro call. Every request goes to sales@bentenfs.com, and we reply within one business day.

Request material or a demo

Tell us who you are and what you need. We will send the catalogue or brochure, or arrange a demo.

I would like
Choose at least one, or write a message below.
Up to 1,000 characters. For example: your channels today, your core system, or what you want to see in a demo.

The button opens your email app with this request addressed to sales@bentenfs.com. Nothing is sent until you press Send in your email app.

Propose an intro call

Pick a time for a 30-minute call. We create a calendar invitation for you to send to sales@bentenfs.com from your own calendar.

You are the organiser of the invitation.

Open the downloaded file with your calendar, check the details and send the invitation. We will accept it or reply with another time.

No email app on this device? Write to sales@bentenfs.com

Benten

Let's build the future of banking together.

Book a walkthrough of the platform running against your scenarios.