# What is lomi.?
Source: https://docs.lomi.africa/start/overview

lomi. is payment infrastructure for Africa. One integration for cards, mobile money, checkout, billing, and payouts.

***

title: 'What is lomi.?'
description: 'lomi. is payment infrastructure for Africa. One integration for cards, mobile money, checkout, billing, and payouts.'
-----------------------------------------------------------------------------------------------------------------------------------

lomi. is payment infrastructure for 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.

<DocsStartHere title="Start here">
  <DocsStartColumn heading="Accept a payment" lead="Send a customer to checkout or a payment link.">
    <a href="/start/create-account">Create an account</a>
    <a href="/start/first-payment">Make a test payment</a>
    <a href="/build/accept/checkout">Hosted checkout</a>
    <a href="/build/accept/payment-links">Payment links</a>
  </DocsStartColumn>

  <DocsStartColumn heading="Build an integration" lead="Call lomi. from your app, the terminal, or an agent.">
    <a href="/start/integration-journey">Integration journey</a>
    <a href="/start/cli-quickstart">CLI quickstart</a>
    <a href="/start/sdk-quickstart">SDK quickstart</a>
    <a href="/build/mcp">MCP</a>
  </DocsStartColumn>
</DocsStartHere>

## When should I use lomi.?

Use lomi. when you want to:

* Accept Wave, Apple Pay, Google Pay, 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 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 multiple payment methods.
* **Dashboard**: a web back-office to sell goods, services, subscriptions, and more.
* **lomi. POS**: the merchant phone app 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 by [creating an account](https://dashboard.lomi.africa).**

## Transparency and compliance

lomi. is built for visibility into fees, transaction flows, and payout processing:

* **Production**: payments run on lomi., [create an account](https://dashboard.lomi.africa). The stack is **not self-hostable today**.
* **Open source**: integrator tooling and documentation are published progressively, see [open source](/resources/open-source).
* **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](/resources/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](/start/integration-journey)                |
| Compare API, SDK, CLI, and MCP       | [How to use lomi.](/start/integration-journey#how-you-call-lomi) |
| Get running from the terminal        | [CLI quickstart](/start/cli-quickstart)                          |
| Call the API from your app           | [SDK quickstart](/start/sdk-quickstart)                          |
| Let an AI assistant call lomi.       | [MCP](/build/mcp)                                                |
| See which payment channels are live  | [Payment channels](/build/payment-channels)                      |
| Accept a first online payment        | [Make a test payment](/start/first-payment)                      |
| Add checkout to an app or store      | [Hosted checkout](/build/accept/checkout)                        |
| Sell without writing checkout code   | [Payment links](/build/accept/payment-links)                     |
| Sell tickets or appointments         | [Event bookings](/build/accept/events)                           |
| Define your catalog before checkout  | [Products](/build/billing/products)                              |
| Compare every integration option     | [Choose an integration](/build/choose-integration)               |
| Connect your backend to events       | [Webhooks](/build/reliability)                                   |
| Let customers manage billing         | [Customer portal](/build/billing/customer-portal)                |
| WooCommerce or Shopify store         | [E-commerce extensions](/build/ecommerce-extensions)             |

## How does the platform fit together?

The typical flow is:

1. Create an account and complete onboarding.
2. Get your test API keys from the dashboard (or run `lomi login` for CLI access).
3. Create a checkout session with `lomi checkout create`, a payment link, or a payment request.
4. Let the customer pay with a supported method.
5. Confirm the result from the API, dashboard, or webhook.
6. Move to live keys when your integration is ready.

The API reference has exact request and response details. The product guides explain which product to use and how to ship the flow.

<DocsNextSteps>
  <DocsNextStep href="/start/create-account" hint="Open the dashboard">
    Create an account
  </DocsNextStep>

  <DocsNextStep href="/start/integration-journey" hint="Sandbox to live">
    Integration journey
  </DocsNextStep>

  <DocsNextStep href="/start/first-payment" hint="First money in sandbox">
    Make a test payment
  </DocsNextStep>

  <DocsNextStep href="/build/choose-integration" hint="Pick a product">
    Choose an integration
  </DocsNextStep>
</DocsNextSteps>
