ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

Park Ji-soo, CEO of Blockchain Infrastructure Company Suho IO: AI Agents Must Satisfy Four Verification Conditions Before Placing Orders and Processing Payments on Behalf of Users

At the 'Stablecoin Issue Briefing 2026' event in Seoul, Park Ji-soo, CEO of blockchain infrastructure company Suho IO, proposed that for AI agents to execute commercial transactions on behalf of users, four infrastructure conditions are required: agent identity confirmation (KYA), conversion of natural language into executable conditions, independent verification, and transaction status management. Drawing an analogy to South Korea's Open Banking system, he explained that fragmented POS terminals, ERP systems, delivery services, and financial services require unified standards so that agents can truly complete the entire process from order placement to payment.

2026-11-19 21:20 GMT+8

A shop owner tells an AI agent, 'Help me order 60 cases of milk; confirm delivery before paying.' The agent can understand this request and plan the steps—checking inventory, placing the order, waiting for delivery, confirming receipt, and triggering payment. But the question is: by what authority does it make these decisions on the owner's behalf? Who verifies that each step actually occurred after completion? And if something goes wrong, who bears responsibility?

Park Ji-soo, CEO of blockchain infrastructure company Suho IO, outlined four infrastructure conditions for such scenarios at the 'Stablecoin Issue Briefing 2026' event held in Seocho-gu, Seoul, on November 19, 2026. The first condition is Agent Identity Confirmation (KYA, Know Your Agent): the system must know which agent is acting, whom it is authorized by, and where its permission boundaries lie. The second is the conversion of natural language into executable conditions: vague requests like 'order 60 cases of milk and pay' must be broken down into verifiable execution parameters such as quantity, price, delivery confirmation criteria, and payment trigger points, with a record of the conversion process retained to trace causes in case of errors. The third is independent verification: when an agent claims payment has been completed, its report alone is insufficient; actual approval records and source data must be cross-checked for consistency. The fourth is transaction status management: the system must be able to track which stage the transaction is currently in—from order placement and delivery confirmation to approval and payment.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Park Ji-soo argues that these four conditions are indispensable; without them, the cause and liability of transaction issues cannot be defined. He provided a counterexample: if a merchant ships goods based solely on an agent's claim that 'I have paid,' while the payment was actually incomplete or the amount was incorrect, the merchant may bear the risk.

His argument draws clear inspiration from an analogy: South Korea's Open Banking. In the past, users wishing to check balances across different banks or transfer funds had to connect separately to each bank's interface. Open Banking unified these interfaces into public standards, allowing any authorized application to access data from multiple banks using a single set of methods. Park Ji-soo believes that agent transactions face similar fragmentation problems—POS terminals, ERP systems, delivery platforms, and financial services operate independently. For an agent to complete a transaction, it must adapt to each one individually. If these execution-layer services are also standardized, agents could call upon them just as they call upon Open Banking APIs.

However, this analogy has its limits. Open Banking solves the standardization of data access, whereas agent transactions involve multi-step execution and cross-system state coordination. A transaction involving 'ordering, delivery, confirmation, and payment' is far more complex than simply 'checking a balance'; inconsistency in the status of any intermediate link could lead to errors. Park Ji-soo himself acknowledges that even if preset conditions are correct, the transaction will still fail if the order or delivery information itself is erroneous.

Suho IO is currently participating in a four-year research project led by the Electronics and Telecommunications Research Institute (ETRI) in South Korea, connecting revenue and inventory information, ordering systems, logistics, and settlement services to empirically verify whether agent transactions can run smoothly from start to finish. Speaking at the event, Park Ji-soo stated that their goal is not merely to draw a blueprint for public infrastructure but to first successfully execute specific transactions.

For readers interested in the commercial applications of AI agents, these four conditions provide a concrete evaluation framework: when any agent transaction solution claims to be 'secure' or 'trustworthy,' one should ask whether it possesses the capabilities of identity confirmation, condition conversion recording, independent verification, and status tracking. Missing any one of these will break the chain of accountability.

Sources

  • byline.network바이라인네트워크↗
Continue researching →