This site is Fineract help for people who run a core-banking tenant: officers, checkers, and administrators. The product you click is Bankayo. The engine underneath is Apache Fineract.

Bankayo customizes Fineract for the institution. That is not only a new screen layout. It is the operator workspace, the backend around the core, the integrations that connect Fineract to the rest of your stack, and compliance — both the controls you run internally and the rules the bodies that regulate your institution require — configured to fit.

Apache already publishes platform and API documentation. Use that when you are changing Fineract itself or calling the REST API from your own code. Use this site when you need the operator path: which permission, which template *Options, which Bankayo screen, and how Bankayo sits on the core.

Apache Fineract is a trademark of the Apache Software Foundation. Bankayo is not an Apache project.

Fineract help

Fineract help here means the resources Fineract actually persists — clients, loans, savings, products, journals, reports, jobs — and the rules the API enforces (permissions, validators, template option lists).

Each article is written in two layers:

What Fineract is doing — the resource, the permission codes, and the catalog or template the form is bound to. That layer is useful even if you never buy Bankayo.
Where it lives in Bankayo — sidebar group, docked sheet, wizard, or report screen, then a short next step.

Start from the topic list, sign in, or finding your way around. The Bankayo ? button opens the matching page for the screen you are on.

Fineract UI

A Fineract UI is any application that talks to Fineract’s API instead of embedding banking logic in the browser. Bankayo’s workspace is that surface: search, tables, wizards, and help, with the session held on the server so the browser never calls Fineract directly.

The UI is one part of the customization, not the whole offer. Same tenant and same Fineract permissions; a different operator path — plus the backend, integrations, and checks described below.

If you are comparing UIs:

This docs site — how Bankayo maps each live screen onto Fineract, and what else Bankayo delivers around the core.
Apache Fineract docs — the API and platform, independent of any product UI.
Other UIs (including community Mifos apps) — their own chrome and workflows; they are not documented here.

Fineract customization

Fineract customization with Bankayo is the product you run, not a reskin of Apache’s reference screens.

Operator UI

Day-to-day work in Bankayo: clients, loans, savings, accounting, reports, and administration. Permissions still come from Fineract; screens you cannot use stay hidden.

Backend

Services around the core: a server-side session, a typed boundary to Fineract (the browser is not a proxy), aggregates computed on the server, and the same permission codes Fineract issues. Infrastructure and operations for that stack are part of the engagement — not something you assemble only in the UI.

Integrations

Connections Fineract already exposes, wired for the institution: hooks, external services (SMS, email, file storage, notifications), external events, credit bureau, and SMS campaigns. Customizing Fineract here means those links work in your environment, not that you paste REST calls into a page.

Compliance

Compliance in a Bankayo engagement covers two layers.

Internal control is what your own policies require on every posting and approval: roles and permissions, maker-checker and the checker inbox, audit trails, entity data-table checks, two-factor sign-in, and the session rules on signing in. Those are Fineract capabilities; customizing Fineract includes turning them on and fitting them to how you operate — not leaving them as unconfigured API flags.

Supervisory and regulatory is what the bodies that regulate your institution require of you — the central bank, microfinance authority, deposit insurer, or equivalent in your market. Customers come to Bankayo as licensed or supervised lenders, not as a generic IT shop. Customizing Fineract here means shaping products, the chart of accounts, loan-loss provisioning, reports (including income statement and balance sheet), credit bureau connections, and operating procedures so the tenant can produce what those supervisors expect. The exact circulars and returns differ by country; that fit is part of the engagement, not a one-size Apache install left for you to interpret alone.

Tenant configuration

What you can change in the tenant through Fineract APIs, shown in Bankayo, without forking the Apache codebase:

Products and charges — loan, savings, share, and deposit products; charges; product mix.
Organization — offices, currencies, funds, tellers, payment types, SMS campaigns.
Accounting — chart of accounts, journal entries, closures, provisioning.
System configuration — global configurations, codes, data tables, hooks, external services, account number preferences.
Access — users and roles (Fineract permission sets).
Documents and messaging — templates (Mustache) and SMS campaigns.

That tenant layer is still Fineract. It is not a guide to patching Fineract Java modules, writing a new SPI, or replacing the API. For platform-level change of that kind, start at Apache Fineract. Bankayo’s work on backend, integrations, and compliance (internal and supervisory) is how we customize Fineract for you on top of that core.

Apache Fineract — project home.
Fineract REST and platform docs from that site when you need request payloads, release notes, or contributor setup.

Then come back here for the operator path on the same engine.

Fineract help, Fineract UI, and Fineract customization