LakiConnect | LakiPay Docs

What is LakiConnect?

LakiConnect is LakiPay's connected-accounts layer — a platform infrastructure that enables marketplaces, aggregators, SaaS platforms, and multi-vendor systems to onboard merchants, accept payments, split funds, and manage settlements through a single unified API.

LakiConnect is not a separate payment processor. Wallet, mobile-money, and bank payment flows use the same LakiPay payment stack. LakiConnect adds identity, configuration, routing, and fee splitting on top of those flows.

Core Concepts

Master Merchant (Platform)

The business integrating LakiConnect. Authenticates with a master API key and is responsible for onboarding connected merchants, configuring fee rules, and receiving settlement notifications.

Connected Merchant

A seller, vendor, service provider, or branch account linked to the master merchant. Transactions can be attributed to a connected merchant, which determines wallet crediting and fee splits.

Split Settlement

When a deposit succeeds, LakiConnect automatically credits:

The connected merchant wallet with merchant_net (gross amount minus platform commission and LakiConnect master fee).
The master merchant wallet with master_merchant_fee_net when a non-FREE fee model is configured, accompanied by a derived MASTER_FEE_<parent_id> transaction linked via parent_transaction_id.

Fee Models

Three fee models are supported:-

FREE (no split)
PERCENT (percentage of transaction)
FIXED (flat amount per transaction)

Supported Use Cases

Marketplaces & Platforms — One master API key, many connected sellers. Each seller's transactions are tracked, settled, and reported independently.
Franchise & Branch Settlement — Central platform collects a commission on each connected deposit.
Compliance & Onboarding — Per-connected KYC documents with admin review; status changes trigger webhook notifications.
Delivery Platforms & Aggregators — Route payments to individual service providers with automatic fee deduction.

Architecture Overview

LakiConnect separates platform responsibilities from payment execution. The master merchant configures the ecosystem; each payment runs through a validated, fee-aware pipeline.

Master Merchant (Platform)

Owns API credentials, merchant onboarding, and platform rules

Authenticates via X-API-Key
Creates and manages connected accounts
Configures fee rules (default + per-connected overrides)
Configures outbound webhook URL and secret
Initiates payments with X-Connected-Merchant-Id header

Payment flow

End-to-end processing through LakiConnect

1
Payment request
Master calls POST /payment/direct or /payment/checkout
2
Relationship validation
LakiConnect validates master ↔ connected relationship
3
Fee resolution
Fee config resolved (per-connected override → master default)
4
Transaction creation
Record created with master_merchant_id, merchant_net, master_merchant_fee_net
5
Settlement & events
On success: wallets credited; outbound webhooks dispatched

merchant_net credited to connected merchant wallet

Webhooks notify your platform on status and settlement events

Authentication

API keys, required headers, and dashboard authentication for master and connected merchants.