Product Model
This page maps agent-facing docs to the current KleePay frontdesk product.
Dashboard home
The main dashboard is the wallet home. It summarizes total assets as an approximate USD value and reconciles:
- Balance: funds available in the wallet
- On cards: funds allocated to cards
The standalone wallet overview page has been removed; home is the wallet surface.
First-run order
For a new user, the safest mental model is:
- Verify the account and complete KYC.
- Fund Balance.
- Create and fund a virtual card.
- Connect a device with
klw. - Let the agent create scoped payment authorizations.
Card creation can also be agent-assisted after Balance is funded and a device is connected. That is a valid advanced path, but dashboard-first setup is easier to inspect and debug.
Activity and statement export
KleePay separates live activity from the formal settled statement.
| Surface | Purpose |
|---|---|
| Activity | Real-time, all-status feed for deposits, withdrawals, card spend, allocations, recalls, refunds, and adjustments. Rows open a shared detail drawer. |
| Statement export | A formal, settled-only statement you export as a PDF from the Activity page. Not a separate navigable surface — it is a download for accounting and reconciliation. |
Agents should use Activity-oriented tools when checking whether a payment is in flight, settling, reversed, completed, or declined. The statement export is for settled reconciliation.
Cards
Cards are merchant-facing payment instruments. Agents can inspect safe metadata and request actions, but raw card credentials are not part of the agent context.
Important card facts:
- Cards can be created, funded, paused and resumed, and reviewed through activity.
- Card spend may show merchant presentment currency first, with USD billing as secondary context.
- Card lifecycle and balance should be checked before creating a payment authorization.
Wallet and assets
The wallet funds cards. USDT is the live funding asset today; USDC is shown in the deposit and withdrawal pickers but gated as coming soon. Deposit and withdrawal flows show network-specific arrival estimates.
Wallet operations include:
- deposit address retrieval
- wallet balance checks
- wallet history
- allocation from balance to card
- recall from card to balance
Devices
The Devices page is the user-facing home for agent connections. In the current frontdesk route structure it is served from /dashboard/api-keys, but the product surface is labeled Devices. It shows connected and not-connected devices, install commands, setup-command expiry, and device management.
The default device scope is user-level. Card-scoped setup is an advanced opt-in for users who want finer isolation.
Authorizations
KleePay uses authorization-centered language:
- scoped authorization
- recurring authorization
- verification authorization
Do not describe this as giving an agent a free-spend card. The key boundary is that every payment permission should be explicit, signed, scoped, and auditable.