Skip to main content

KleePay Docs

KleePay connects AI agents to scoped card payments without exposing unrestricted card credentials. Agents can inspect safe card metadata, move funds when authorized, and create locally signed payment authorizations for specific payment intents.

Start from the KleePay web app, or create an account if you do not have one yet.

The big picture​

KleePay separates two very different ways to pay — an AI agent buying online for you, and a person (or, soon, a robot) tapping in person — and secures each the right way.

How an agent pays online​

Your agent never holds a chargeable card. It asks klw — the KleePay Local Wallet on the same device — to sign a scoped authorization: an amount range, one merchant, a short time window. The agent then places the order at the merchant's checkout, and when the merchant charges the card, KleePay compares the charge against your active authorizations and approves it only on a full match. Anything else — wrong amount, wrong merchant, too late, or a charge you never authorized at all — is declined.

YOUR DEVICEAI agentClaude Code, Codex, any MCP agentklw · KleePay Local Walletsigning keys never leave the deviceTHE AUTHORIZATIONScoped authorizationamount$12.00 ± 25% driftaccepts $9.00 – $15.00merchantstore.comvalid forthe next 30 minutessigned with your device key1signs2places a $12.00 orderWHEN THE MERCHANT CHARGESstore.comthe merchant — charges the card34KleePay checks the charge· amount inside the authorized range?· merchant matches?· inside the time window?compared againstfull match → approvedanything else → declined

Paying in person — today your phone, tomorrow a robot​

Add the same card to Apple Pay or Google Wallet and tap at a physical terminal: it behaves like any normal debit card, with no authorization step. What protects that path is what protects Apple Pay itself — the device's secure chip holds a device-specific token, never your real card number, and produces a fresh one-time cryptographic proof for every tap. And because that chip is smartwatch-class hardware, the same card is designed to extend to robots: a payment chip on board lets a robot tap to pay under the same account, limits, and audit trail.

WHO TAPSYour phone or watchcard added to Apple Payor Google WalletFUTUREA robotpayment chip on board —like a smartwatch'sIN THE STOREPOS terminaltap to paytapWorks like a normal cardno authorization step — thesecure chip holds a devicetoken, never your card number,and proves itself on every tap
Why this beats a normal cardAn ordinary card can be charged by anyone who has its details — the number, expiry, and CVV. A KleePay card cannot: any online charge that does not match one of your authorizations is simply declined. Save the card at a small shop, check out on a site you do not fully trust, even let the details leak — stolen card details are useless, and a merchant that kept your card on file cannot bill you out of the blue.
QuickstartComplete KYC, fund Balance, create or fund a card, connect klw, then authorize the first agent payment.Devices and klwUnderstand setup commands, device connection state, token expiry, and local keystore recovery boundaries.Agent integrationConnect Claude Desktop, Codex, OpenClaw, or another MCP-compatible agent to KleePay.MCP toolsReview the 17 local tools for cards, wallet operations, scoped authorizations, and audit flows.HTTP APIUse the local REST interface when an agent or integration does not support MCP.Product modelMap docs terms to the current frontdesk product: Devices, Activity, Balance, On cards, and scoped authorizations.
Core modelKleePay does not give an agent unrestricted card access. Every charge is denied by default and approved only when it matches a scoped local authorization, bounded by card, amount, merchant, and TTL.

What is documented here​

  • setting up klw (KleePay Local Wallet) and the local signer daemon
  • understanding Devices and setup-command lifecycle
  • connecting MCP-compatible agents to KleePay
  • using the local HTTP API at http://127.0.0.1:7723
  • creating scoped, recurring, and verification authorizations
  • managing card and wallet operations through safe local tools
  • mapping agent actions to current frontdesk surfaces such as Activity, Balance, and Cards (plus statement PDF export)

Current coverage​

These docs cover the current developer-facing KleePay flow: device connection, local signer setup, MCP tools, local HTTP fallback, scoped authorizations, and the frontdesk product concepts an agent needs to reason about payments safely.