◆ Railspan module

Proposed offering

Part of Railspan, the modular payments and banking platform. This page details the module scope within that offering.

Core Banking Platform

Your products. Your customer experience. Account operations you can explain.

A proposed white-label core for customer, savings, lending and accounting operations, scoped around your institution and integrations.

Discuss your workflow Explore the proposed workflow

Concept-stage implementation service. The foundation has been reviewed in source; this RZIFI offering has not been delivered or deployed for a customer.

The operating problem

Give the team a path from question to decision.

A product change can affect customer accounts, repayment schedules, interest, accounting and reporting at once. Teams need one traceable operating view before they can safely replace spreadsheets or migrate a book of accounts.

Design a branded operations experience around Apache Fineract 1.x, a headless financial-services platform. Its customer, configurable loan and savings, accounting and reporting APIs provide the foundation to evaluate. RZIFI proposes the customer interface, product setup, integration adapters and operational controls around that foundation. Begin with one product and a synthetic portfolio, then validate the selected version against your accounting policy, local requirements and operating model. This is a proposed implementation, with no deployed RZIFI core or production-readiness claim.

Designed for

Banks, microfinance institutions, credit unions, fintechs and money-service providers assessing a configurable account engine within their own authorized operating model.

Explore the workflow

From product setup to a reconciled account

Illustrative workflow with synthetic data. This is a static product concept, with proposed integration and control behavior to validate during a pilot.

CORE-DEMO-0024Synthetic scenario · no live operation

Configure and review the product
Proposed control
Agree interest and fee examples, accounting mappings, business dates and approval roles. Review test outcomes before enabling a product.
Prepare the customer and application
Synthetic application
Use a synthetic customer and savings application. A live implementation would require the institution's identity checks, account eligibility and authorized review.
Review activation and funding evidence
No live action
Show a proposed maker/checker activation and funding reference. The example does not activate an account, accept a deposit or confirm a provider transaction.
Explain the intended account entry
Illustrative only
Illustrate how an authorized entry would link the account, provider reference and reviewed ledger mapping. An AI explanation cannot authorize or create the entry.
Reconcile before resolving exceptions
Proposed reconciliation
Compare provider evidence, account records and ledger totals. Keep missing or timed-out outcomes unknown until investigated; do not repost or retry on assumption.
Review the business-date close
Human sign-off
Review interest and fee checks, journal totals and open breaks before an authorized close. Retain evidence and handle later corrections through approved reversal/adjustment rules.

This synthetic path illustrates proposed controls from configuration to close. No account is opened, funds received, interest posted, ledger entry created or period closed by this page.

Capabilities and scope

Start with what exists. Scope the rest.

Source review identifies building blocks. Integration, configuration and deployment acceptance still determine what the customer implementation can do.

Foundation behavior reviewed

Implementation found in upstream source. No runtime or production claim follows from this review.

Customer records, lifecycle commands and linked account overview
Loan product creation, configuration and accounting-rule mapping
Savings product creation and configuration APIs
Loan application, repayment-schedule calculation and approval/disbursement commands
Savings application, activation, interest and account-closure commands
Journal-entry retrieval and balanced journal-entry creation API
Predefined report execution and available export-type discovery

Technical source notes · 23 October 2026

Proposed customer implementation

New work to design, integrate and test against your requirements.

Branded staff experience for customer records, account servicing, product configuration and exception queues
Configured savings and lending products with reviewed interest, fee, schedule and general-ledger mappings
Customer-specific onboarding, identity, payment-provider and finance-system adapters with authorized data boundaries
Maker/checker approvals, audit evidence, reconciliation and business-date/period-close controls mapped to the operating model
Migration rehearsals with record counts, opening-balance controls, portfolio-to-ledger checks, sign-off and rollback criteria
AI-assisted account explanations and exception investigation with source references, uncertainty and human review

Roles, report access and data boundaries are mapped to the customer operating model. Shared multi-customer administration and enterprise identity require explicit scope.

Scope boundary

Fineract is the proposed account and portfolio foundation. A branded interface, connectors, migration, enterprise identity, operating dashboards and control configuration require implementation and acceptance. The core does not itself provide a banking license, deposit-taking authority, payment rail, remittance network, FX execution, safeguarding arrangement or compliance service. AI may assist investigation and explanations; it cannot autonomously approve credit, AML decisions or account entries. No availability, regulatory approval, certification or performance outcome is promised.

Business use cases

Choose the workflow worth improving.

Bank savings and deposit servicing

Configure an agreed savings product, review a customer application and service account changes with a traceable view of interest, charges and accounting consequences.

Value to validate: Reproduce agreed balances, interest examples and journal mappings across business dates before accepting a product for use.
Integration needed: Customer identity/onboarding, authorized funding and withdrawal providers, statements and the institution's general ledger. Other deposit types need separate fit validation.

Lending lifecycle operations

Carry a loan from application and schedule review through human credit approval, authorized disbursement, repayment servicing and exception handling.

Value to validate: Test repayment allocation, schedule changes, reversals, arrears scenarios and portfolio-to-ledger agreement using the selected product rules.
Integration needed: Loan origination, credit decision ownership, approved payout/collection providers and finance reporting. Lending policy and decisions remain with the institution.

Microfinance and credit-union operations

Bring member or client records, savings and loan servicing into a branded staff workspace with branch responsibilities and exception follow-up.

Value to validate: Check the institution's individual/group product rules, branch access and portfolio reports against representative scenarios. Membership shares require separate scope.
Integration needed: Member/client registry, field operations, collection channels, branch structure and finance mappings; local and institution-specific rules need validation.

Fintech and money-service account operations

Evaluate customer account records and a product subledger alongside a licensed bank or money-service provider, then reconcile each authorized provider outcome to the account record.

Value to validate: Prove account-to-provider references, duplicate handling, unknown outcomes and reconciliation before enabling any posting connector. Wallet or stored-value fit requires separate assessment.
Integration needed: Contracted bank/payment/remittance services, safeguarding evidence and separately governed KYC/AML systems. The core supplies no payment rail, FX execution, compliance decision or operating license.

Compare approaches

A custom implementation should earn its place.

An existing SaaS package may be the better choice for standard needs. Compare the same workflow, workload, geography, data boundary and support commitment. No savings or performance advantage is assumed.

Vendor observations checked 23 October 2026; not RZIFI prices or normalized sales quotes. Unknown setup cost does not mean zero.
Approach	When to consider it	Observed commercial basis	What needs checking
RZIFI proposalProposed offering	A specific workflow, integration or deployment requirement justifies dedicated engineering.	Scoped discovery and implementation, with optional recurring operations. Request a quote.	Selected license, tenant boundaries, integration acceptance, operating ownership and total cost.
Apache Fineract 1.x ↗	Institutions evaluating a headless core with control over their interface and implementation.	Apache-2.0 open-source foundation; software licensing is distinct from implementation, hosting, support and operating cost.	Choose and validate a supported release, secure deployment and operating owner. This is RZIFI's proposed foundation, not a turnkey RZIFI service or Apache endorsement.
Mambu ↗	Institutions comparing a managed core with configurable lending and deposit products.	Official product page offers demo/expert contact. No numeric public price verified; request a written quote for the exact scope.	Compare contracted products, usage, integration, migration, support, data residency and exit terms. No source-code or rebranding rights are assumed.
Temenos Core ↗	Banks evaluating broader core modernization and institution-specific banking requirements.	Official page directs buyers to sales. No numeric public price verified; request a written license/SaaS and implementation quote.	Match modules, local requirements, deployment, integration, migration and operating responsibilities before comparing total cost.
Thought Machine Vault Core ↗	Banks and fintechs assessing programmable products and a core ledger foundation.	Official page offers contact/demo. No numeric public price verified; request a written quote for the selected deployment and scope.	Validate product configuration, delivery and support scope. Vault Payments is a separate offering; payment connectivity is not assumed to be included in a core quote.

Deployment and customization

Choose the data boundary and the operating owner.

Begin with a dedicated sandbox and synthetic data. A customer cloud, managed environment or on-premises target requires its own agreed architecture, tenant boundary, security configuration, availability and recovery evidence. Select a supported Fineract release and validate upgrades, migration, reconciliation, close controls, access, backup/restore and incident ownership before considering live use. Branding and connector delivery remain scoped work.

Brand and experience: Agree domains, logos, interface theme, notification email, accessibility and the upstream notices that must remain.
Data and identity: Define users, roles, document or record access, secrets, retention and export. Validate separation with positive and negative access scenarios.
Operation and change: Name who monitors the service, handles incidents, maintains connectors and applies upgrades. Include backup, restore and rollback evidence.

Commercial scope

Price the implementation you actually need.

Request a scoped proposal covering product-fit discovery, configuration, branded experience, integration, migration rehearsals and acceptance evidence, with optional ongoing operations. Identify infrastructure, third-party licenses, model/API usage, payment providers, taxes and support commitments separately. Define volume assumptions and responsibilities before comparing vendor quotes; there is no verified RZIFI price, delivery date or savings claim.

Bounded pilot

One workflow and agreed test data. Define the acceptance cases and limitations before implementation.

Production target

Validate the selected integrations, authorization, recovery, upgrades and operating handover. Release follows observed acceptance.

Enterprise extension

Scope buyer-specific identity, audit, regional deployment, recovery and support commitments. Certification is a separate requirement.

These are potential delivery scopes, not existing service tiers or committed calendar dates. Discovery is part of the agreed delivery scope; any separate discovery invoice is accounted for in the implementation quote.

Purchasing questions

Make the decision with the boundaries in view.

Is this a deployed RZIFI core banking system?

This is a proposed offering backed by a review of Apache Fineract 1.x APIs, not a deployed service. Discovery selects the product, version and operating scope; implementation and observed acceptance are required before any release claim.

Can banks, fintechs and money-service providers use the same package?

Their needs and permissions differ. A bank may assess savings and lending servicing; a fintech or money-service provider may assess an account subledger with contracted providers. Each scope needs product-fit, accounting, data and regulatory review. Software does not confer a banking or money-services license.

Can the interface carry our brand?

A customer-branded interface is proposed implementation work. Apache-2.0 permits modification subject to its terms, including applicable notices; it does not grant Apache trademark rights. We review the selected distribution and all UI/dependency licenses, preserve required notices and do not imply Apache endorsement.

What does migration and close require?

Agree source ownership, mapping, record counts, balances, transaction history and accounting policy. Rehearse migration, reconcile portfolio and ledger totals, resolve exceptions, define rollback and obtain business sign-off. Business-date processing and period close require separately tested controls, approvals and retained evidence.

What role can AI play?

A proposed assistant can explain account activity, retrieve authorized evidence and help staff investigate exceptions. Humans retain responsibility for credit and AML decisions, account entries, corrections and close approvals. Model access, privacy, evaluation and audit controls need explicit implementation.

How should we compare commercial options?

Request written quotes on the same products, account/transaction volumes, migration, connectors, hosting, support and exit requirements. No vendor sales quote was obtained for this page, and no price or savings advantage is assumed. The Apache software license is available at apache.org/licenses/LICENSE-2.0; operating a core still has delivery and ongoing costs.

What does a scoped implementation include?

Discovery identifies the workflow, data boundary, selected edition, integrations and acceptance criteria. Implementation and optional ongoing operations are quoted against that scope. There is no standard package or committed list price at this concept stage.

Can it run in our environment?

A dedicated customer environment is the first design target. Customer cloud, managed hosting and on-premises options are evaluated separately against the chosen foundation, identity requirements and operating owner. A tested deployment and recovery procedure are required before a commitment.

What evidence is needed before launch?

The agreed scope should name authorization and integration tests, data migration checks, backup and restore, upgrades, vulnerability handling and operating responsibility. Certifications, regulatory approvals, service levels and performance outcomes are not implied by a proposed offering.

Start with your operating problem

Show us the workflow that is costing your team time.

Discuss the requirements, the foundation and the work needed before a launch. The next step is a scoped conversation.

Discuss this offering