Platforms and marketplaces

Pay out to connected merchants on one integration

An Operator organization acts on behalf of Member Accounts (real lomi. merchants with acct_... ids). Add Lomi-Account to API calls with your operator secret key to create charges, checkout sessions, refunds, and reads for each connected account.

Learn about Network Network docs

Core concepts

Operator and member accounts

You hold the operator API key; each member is a connected organization with its own branding and payment methods at checkout.

Delegated API calls

Same public endpoints as direct merchants, plus Lomi-Account: acct_... on requests that target a member.

Capabilities per membership

Permissions such as payment.create or refund.create are granted per operator–member relationship and environment.

Reporting in the dashboard

Operators review delegated performance in the Network panel; member-scoped transactions require the header on API reads.

Key facts

Onboard sub-merchants with KYC and settlement configuration per connected account.
Route charges with platform fees and pass-through settlement rules.
Designed for marketplaces, SaaS platforms, and payment facilitators in UEMOA.

Network vs standard merchant account

Use a standard merchant account when you only process for your own business. Use Network when you collect on behalf of multiple merchants and need split payouts.

How to launch on Network

Apply for a platform or marketplace use case with lomi. compliance.
Create connected merchant accounts and complete their KYC.
Route checkout sessions or charges with Network headers and settlement rules.

Network FAQ

Do sub-merchants need their own lomi. login?

Connected accounts are provisioned by the platform; end merchants complete KYC through your onboarding flow.

Single merchant?

If you only process for your own organization, use standard checkout or direct charges without Network headers.

See pricing