Most payment APIs ask you to paste a secret into a config file. MCP does not have to.
Connect MCP · Full docs · Add to Claude · Add to Grok Bot
What happens when you click
Your client opens Connect with lomi. You sign in or create an account, pick the organization, and approve. The client stores a scoped token. From then on it can call the same merchant tools you would hit over REST: checkouts, customers, webhooks, refunds.
Why this matters for a shop in UEMOA
Wave and cards already finish on the phone. The remaining drag is everything around the charge: building the session, chasing webhooks, reconciling the receipt. An assistant that can create a checkout URL and confirm the transaction cuts that loop without teaching every teammate the API.
Two doors, one product
Humans with a lomi. account (or who want one) use the one-click buttons. Agents with no account yet connect the guest MCP URL, register, provision a test merchant, and get tools on the same session once a test key exists. Live money still needs a human on the dashboard.
Start here
Use lomi.africa/connect for the buttons, or read the full guide at docs.lomi.africa/build/mcp. Hosted endpoint: https://mcp.lomi.africa/mcp.