Kachyng Completes End-to-End Proof of Agentic Commerce: One Agent, Two Purchases, One Approved
In a live proof of Kachyng ACom, an AI agent tried to buy two products from the same merchant catalog. One was approved. One was rejected for exceeding its delegated spending limit. Every layer of the transaction ran on a single stack.
SAN FRANCISCO, Calif. — Today an AI agent tried to buy two products from the same merchant catalog. One was approved. One was rejected.
Every layer of that transaction ran on one stack. The agent storefront. The catalog. The signed offer. The checkout. The identity. The verification. The wallet authority. Ours.
Kachyng completed an end-to-end proof of Kachyng ACom, its agentic commerce platform. Here is what happened inside that flow.
The agent discovered products through an agent-readable storefront. It compared options and selected an item. The merchant catalog issued a signed offer, with price, terms, and merchant identity bound to the transaction. Checkout verified and consumed that offer. The agent's identity was resolved, its delegation chain validated, and its wallet authority evaluated.
Then a decision: approved, rejected, or escalated for human approval.
The lower-value product was approved. The higher-value product was rejected for exceeding its delegated spending limit. Same storefront. Same agent. Same checkout path. Different authority outcome.
One thing worth being clear about: the agent storefront is not the merchant's e-commerce store. Merchants do not rebuild their site, move their catalog into a marketplace, or replatform anything. Their existing catalog becomes agent-readable. The store humans shop stays exactly as it is. Agents get their own front door. Governed, verified, controlled.
There is a lot of important work happening right now on how agents and merchants communicate. But communication standards answer one question: how do the parties talk? They do not answer the harder one: should this transaction be allowed?
Who is this agent? Who delegated it? What is it permitted to spend, with which merchants, under what terms? Who is accountable when it is wrong? That is not a messaging problem. It is a control layer, and it has to hold no matter which standards win.
That control layer needs:
Agent identity and delegation.
Signed, verifiable merchant offers.
Wallet-bound authority and spending limits.
Approval-required flows.
Deterministic checkout execution.
Auditability from discovery to decision.
Payments has seen this before. Messaging formats come and go. The durable layer is always the one that decides trust and authority. That is the layer Kachyng built. Today it ran end to end:
storefront → catalog → signed offer → checkout → identity → wallet authority → decision
“The rejected transaction is not a failure. It is proof the control layer holds.”
Huge credit to the Kachyng team, distributed across two continents, who built every layer and ran them as one. And thank you to the design partner who ran this proof with us against a real merchant catalog. More on that soon.
If you are building agent experiences, merchant catalogs, wallets, or payment infrastructure, talk to us. If you are a merchant wondering what agentic commerce means for your store, talk to us.
About Kachyng
Kachyng Inc. is building payment infrastructure for autonomous AI agents. Headquartered in San Francisco, Kachyng's A-Commerce platform — comprising IDX, AGX, KYA, and PRX — provides the trust, identity, authorization, and payment routing layer that enables AI agents to transact on traditional financial rails. www.kachyng.com