Server-side payments
Charge from your server when you own the UX
Direct charges call POST /charge/* from your backend — Wave, MTN MoMo, or card with Payment Elements. Use when embedded UI or custom mobile-money flows matter more than a hosted checkout page.
When it fits
Wave and MTN from your app
Create charges server-side; customers approve on their phone or open the launch URL from your UI.
Embedded card collection
POST /charge/card returns a client_secret for lomi. Payment Elements inside your application.
Webhooks for pending states
Mobile money often starts PENDING — your integration listens for completion events rather than assuming instant success.
Network and platform flows
Operators can delegate charges to connected member accounts with the Lomi-Account header — see <a href="/network" class="underline hover:text-foreground">Network</a>.
Prefer less custom UI?
Most teams should start with hosted checkout or Relay store plugins before direct charges.
See pricing