What is lomi.?
lomi. is an open-source payment processing platform built for francophone West African businesses in the UEMOA. One integration for cards, mobile money, checkout, billing, and payouts.
lomi. is a payment platform for businesses selling in francophone West Africa. It gives you one place to accept card and mobile money payments, send payment links, run hosted checkout, manage customers and subscriptions, receive webhooks, and reconcile transactions and payouts.
When should I use lomi.?
Use lomi. when you want to:
- Accept Wave, MTN MoMo, SPI, cards, and other local payment methods through one integration.
- Send a customer to a hosted checkout instead of building payment collection from scratch.
- Create payment links for invoices, services, events, donations, or product sales.
- Run recurring payments and customer subscriptions.
- Receive reliable webhook events for payments, refunds, subscriptions, and checkout states.
- Track balances, transactions, refunds, and payouts from one dashboard.
Payment complexity
The West African payment landscape is fragmented across many providers. That often forces merchants to maintain multiple integrations or depend on closed-source processors, which increases development time, transaction cost, and maintenance overhead.
lomi. addresses this with:
- APIs: one integration for cards, MTN MoMo, Wave, SPI (64+ mobile money operators and banks), and more.
- Dashboard: a web back-office to sell goods, services, subscriptions, and more.
- Mobile app: a soft POS to sell on the go and withdraw earnings.
- Control: reconciliation, refunds, payouts, hosted checkout, payment links, embeddable elements, direct charge APIs, and reporting.
Get started in francophone West Africa by creating an account.
Transparency and compliance
lomi. is built for visibility into fees, transaction flows, and payout processing:
- Hosted platform: production payments run on lomi.’s cloud, create an account. The payment stack is not self-hostable today.
- Open source: integrator tooling and documentation are published progressively, see codebase structure.
- Community governance: roadmap and product input via GitHub issues and pull requests.
- Compliance: BCEAO licensing (in fieri), PCI DSS level 4, certified card partners, GDPR and MACP with data flows through Cape Town and Dublin.
For the full product vision, see the manifesto.
What can I build first?
Most teams should start with one of these paths:
| Goal | Best starting point |
|---|---|
| Follow the full sandbox-to-live path | Integration journey |
| Get running from the terminal | CLI quickstart |
| Accept a first online payment | Make a test payment |
| Add checkout to an app or store | Hosted checkout |
| Sell without writing checkout code | Payment links |
| Define your catalog before checkout | Products |
| Compare every integration option | Choose an integration |
| Connect your backend to events | Webhooks |
| Let customers manage billing | Customer portal |
| WooCommerce or Shopify store | E-commerce extensions |
How does the platform fit together?
The typical flow is:
- Create an account and complete onboarding.
- Get your test API keys from the dashboard (or run
lomi loginfor CLI access). - Create a checkout session with
lomi checkout create, a payment link, or a payment request. - Let the customer pay with a supported method.
- Confirm the result from the API, dashboard, or webhook.
- Move to live keys when your integration is ready.
The API reference has exact request and response details. The Build guides explain which product to use and how to ship the flow.
What should I read next?
Onboarding
After your first payment works