FAQ
Frequently asked questions
Clear answers to what institutions most often ask about implementing, securing and operating Nexus Kilima.
How is Nexus Kilima deployed?
You can deploy in the cloud or on-premise, depending on your regulatory and operational needs. We help you choose the right model during onboarding.
How long does implementation take?
Most institutions go live within a few weeks. The exact timeline depends on your product configuration, integrations and data migration.
How secure is the platform?
Security is foundational: encryption in transit and at rest, multi-factor authentication, role-based access control, immutable audit trails, tested backups and continuous monitoring.
Who develops and maintains Nexus Kilima?
Nexus Kilima is developed and maintained by Masha Nexus as one of its flagship financial technology products.
How does pricing work?
We provide a tailored quote based on your institution’s size, products and requirements, contracted through a custom proposal rather than fixed list prices.
Can the platform be customised and white-labelled?
Yes. Products, workflows, roles and limits are configurable, and higher tiers add full white-labelling and custom modules under your own brand.
What support and training do you provide?
All plans include support with clear SLAs; higher tiers add priority and 24/7 coverage plus a named success manager. Role-based training is included in implementation.
Where is my data hosted, and can it work offline?
Hosting can be cloud or on-premise, with data residency aligned to your requirements. The platform is also designed to keep working where connectivity is intermittent.
How are updates and releases handled?
Updates follow a managed release schedule with clear release notes, coordinated to minimise disruption. Every release is documented in the Download Center.
Can it integrate with our existing systems?
Yes. Nexus Kilima is API-first, integrating with core systems, payment rails, mobile money and third-party services.
Does it support mobile money and QR payments?
Yes — mobile-money transfers and QR-based payments are supported for customers, agents and merchants.
Which institutions is it built for?
Banks, microfinance institutions, SACCOs, credit unions, cooperatives and NGOs across Africa.
How do you handle KYC and compliance?
KYC workflows and compliance controls are configurable to your local regulatory requirements, with full audit trails for accountability.
How does licensing work?
Nexus Kilima is licensed on a subscription basis per engagement; your proposal specifies the licensed modules, users and support level.
How do we get started?
Book a demo through our contact page. Our team will assess your needs and prepare a tailored proposal and implementation plan.
Still have questions?
Our team is happy to help. Reach out and we will respond within one business day.