Unified biller API
Utilities, telecom, financial services, government and recurring bills behind one integration.
Kapi payments gateway
Kapi is a bill payment gateway designed for AI-driven systems. It unifies biller integrations behind one API, routes each payment over the appropriate rail, and wraps agent-initiated payments in policy limits and approvals.
Guardrails for agents
Tool-calling schemas with policy limits, so an assistant can pay a bill without being trusted blindly.
Runs on your soil
Deployable on infrastructure you control, for data residency and regulatory requirements.
The integration problem
Bill payments in India mean many billers, several rails and a different failure mode for each. Kapi presents one interface for fetching a bill, validating it, paying it and reconciling the result, and handles routing across UPI, NEFT, IMPS, RTGS, BBPS and cards underneath.
Payments initiated by agents
When an assistant pays on a customer's behalf, the risk is no longer a bad UI but an unsupervised decision. Kapi exposes tool-calling schemas with explicit policy: per-transaction and per-period ceilings, allowed biller categories, and approval steps for anything outside the envelope. Every action is logged against the policy that permitted it.
Compliance posture
Built to PCI DSS Level 1 and ISO 27001 expectations and RBI requirements, with a sovereign deployment option where the whole gateway runs inside the customer's own environment.
The numbers.
Biller categories
- Utilities
- Electricity, water, gas, broadband
- Telecom
- Mobile, landline, subscriptions
- Financial services
- Cards, loans, insurance
- Government
- GST, income tax, property tax
Rails and controls
- Rails
- UPI, NEFT, IMPS, RTGS, BBPS, cards
- Agent interface
- Tool schemas for major model providers
- Deployment
- Managed or sovereign on-premise
Straight answers.
What stops an agent from making a payment it should not?
Policy is enforced at the gateway, not in the prompt. Limits, allowed categories and approval steps are configured server-side, and a request outside them is refused regardless of what the model asks for.
Can it run entirely inside our environment?
Yes. The sovereign deployment runs the gateway on your infrastructure so that payment and customer data stay inside your boundary.