lomi.

Website   •   Docs   •   Blog

About lomi.

lomi. is payment infrastructure for merchants and their customers across West Africa and beyond. We publish integrator tooling (API, SDKs, CLI, plugins) as open source. Production payment processing is not self-hostable today. Merchants use dashboard.lomi.africa.

Our platform simplifies product, services, usage, and subscription billing while ensuring the highest levels of security, reliability, and compliance.

Roadmap

We are progressively open-sourcing the monorepo toward eventual self-hosting for operators with their own provider and compliance setup. That is not available in production today. See docs.lomi.africa/resources/open-source for the current public tree.

• Currently open-source:

  • Documentation website: apps/docs
  • CLI: apps/cli
  • Merchant MCP server: apps/mcp
  • Agent plugin (marketplace install): apps/tools/agent-plugin (lomiafrica/agent-plugin)
  • SDKs: apps/sdks
  • E-commerce plugins: apps/plugins
  • Events boilerplate (separate repo): lomiafrica/events

• Opening soon:

  • Merchant dashboard: apps/dashboard
  • Shopify extension: apps/plugins/shopify

• Proprietary:

  • API service: apps/api (lomiafrica/api)
  • Admin dashboard: apps/admin
  • Merchant phone app (lomi. POS): apps/pos (lomiafrica/pos)

All open-source repositories will be merged into the monorepo in the coming months.

Payment infrastructure

lomi. integrates with the SPI, the official Central Bank-backed payment interoperability platform. With lomi., you can accept payments across 8 UEMOA countries (Benin, Burkina Faso, Côte d'Ivoire, Guinea-Bissau, Mali, Niger, Senegal, Togo). Our platform enables Bank-to-Bank, Bank-to-Wallet, Wallet-to-Bank, and Wallet-to-Wallet transactions through our suite of APIs.

The platform provides instant payment confirmation and settlement, allowing you to send payments using SHID, MCOD, or MBNO aliases without ever sharing account numbers. We offer native support for the West African CFA Franc (XOF).

For fellow fintechs, we built an SDK around this infrastructure: pi-spi-sdk - a community TypeScript SDK for the PI-SPI Business API (apps/sdks/pi-spi-sdk).

Documentation

For comprehensive documentation, visit docs.lomi.africa

License

This project is dual-licensed:

1. The majority of the codebase is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). This means you can freely use, modify, and distribute this code while ensuring that any modifications you make are also open-source.

2. Certain files marked with /* @proprietary license */ are under lomi.africa's LLC Commercial License. These files require a valid commercial license from lomi. for production use.

See the LICENSE file for the complete terms of both licenses.

Contributing

We welcome contributions to lomi.! This document outlines how to submit changes and which conventions to follow.

Prerequisites

You should be familiar with GitHub issues and pull requests, have read our documentation, and have cloned the monorepo for local development (git clone https://github.com/lomiafrica/lomi./) or installed the CLI via npm install -g lomi.cli. Local setup is for contributors — not for running your own payment processor.

Contribution process

1. Issues First: Before working on a change, make sure there's an issue for it. Find an existing issue or open a new one.

2. Fork & Branch: Fork the repository and create a branch from develop with a descriptive prefix:

   • fix/ for bug fixes
   • feat/ for features
   • docs/ for documentation changes

3. Make changes: Keep your commits small and focused and ensure that your contribution doesn't modify files marked with `/* @proprietary license *

4. Submit PR: Open a pull request against the develop branch. Include a clear description following the What-Why-How-Testing structure.

5. Code review: A team member will review your PR within a few hours/days.

For detailed contribution guidelines, please see our CONTRIBUTING.md.

Community & support

Join our community Discord for discussions and help, follow @lomiafrica on Twitter for updates, or connect with us on Slack. Submit issues on GitHub for bug reports and feature requests, or contact us directly at [email protected].

Security

For security vulnerabilities, please follow our Security Policy. Please do not report security vulnerabilities through public GitHub issues.