Build AI agents that autonomously pay & collectDocs

Let agents pay & collect.You stay in control.

Accept M-Pesa payments in chat, auto-settle PayBills and Tills, and disburse payouts with programmable guardrails and instant settlement.

Works with agent tools

Connect through MCP, OAuth, API keys, CLI, or direct HTTP.

OpenClaw
Hermes
Codex
Claude
Any MCP client

Agent setup

One setup path per agent environment.

Install the CLI for shell-based agents, or connect through MCP, OAuth, and API keys where supported.

$npm install -g lipafy

Core Infrastructure

Payment controls for agent-initiated work.

A unified platform for payment intents, policy guardrails, wallet holds, verified destinations, and real-time reconciliation.

Kenyan PayBills & Tills

Instant lookup, STK push collections, and autonomous payouts for PayBills (Internet, Water, Utilities), Buy Goods Tills, and mobile money.

  • 100+ verified billers
  • Auto-resolved paybills
  • Masked privacy

Autonomous Execution

Autonomous execution within approved policy thresholds; requests exceeding limits pause for human dashboard review.

  • Sub-3s settlement
  • Threshold automation
  • Zero human latency

Spending Guardrails

Set daily budgets, per-payment caps, and payment rail rules. Agents operate strictly within your configured boundaries.

  • Daily & monthly caps
  • Per-agent scoping
  • Whitelisted billers

Dual-Custody Approvals

Escrow hold protection and multi-sig sign-offs for large transactions before funds move across banking rails.

  • Multi-sig review
  • Separation of duties
  • Immutable audit logs

How Lipafy works

Prepare, control,
execute, reconcile.

Lipafy sits between the agent, the wallet, and supported payment rails. The agent prepares a payment, Lipafy checks the rules, and people approve when required.

Feeshown first
Approvewhen required
Confirmafter final status

Agents can act only within the rules you set.

OAuth connects supported apps once. Every payment still passes identity, balance, beneficiary, fee, spending-limit, and approval checks before money moves.

Spend limits

Daily caps, per-request caps, and category allow/block lists per key.

Human approvals

Pause over-threshold requests until the user approves or denies them.

Audit records

Every completed payment leaves a record linked to its wallet, requester, fee, and beneficiary.

Local payment rails

Send supported KES payments and M-Pesa payouts while keeping the underlying routing private.

Spend rules checked first
Approval only when required
Receipts after completion
View controls

Set the rules. Let agents act. Keep every payment in control.

Connect

Connect agents through MCP, CLI, or API.

Use OAuth where available, or scoped API keys for terminal and self-hosted agents.

$npx lipafy

OAuth connectors

Use the MCP endpoint in hosts that support browser-based connection flows.

Terminal agents

Run the CLI from Codex, Hermes, OpenClaw, or other shell-based agents.

API-key agents

Issue a scoped key per agent and apply spending controls.

Get started

Add payment controls
to every agent request.

Set limits, approve requests, show fees clearly, and reconcile local payments without exposing routing credentials.