Unverified50% confidenceFactExact time
Under a shared payment token architecture, neither the agent nor the merchant can access the user's original payment information, and all security verification is executed uniformly by the payment service provider.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
9/7/2026
First Seen
Valid until: 12/6/2026
Sources
Related Entities
Related Claims
UnverifiedIn the Shared Payment Token flow, the payment service provider is responsible for verifying the token's validity, amount limits, and expiration date, and transactions that violate the rules are directly rejected.74% similarUnverifiedPaymentKit independently custodies payment tokens, separating the token custody layer from specific processors and hosting it independently so that payment credentials are not tightly bound to a single processor.72% similarUnverifiedUCP adopts a Shared Payment Token mechanism in which the payment service provider returns an encrypted token rather than the raw card number, ensuring that neither the agent nor the merchant can access the user's raw payment information.69% similarUnverified传统支付体系围绕人类操作设计，需要人工输入信用卡号、点击确认、通过验证码等，不适合需要秒级完成多次交易的AI代理68% similarUnverified传统支付网关（如Stripe、PayPal）的授权模型是全有或全无，即便使用受限密钥其粒度也仅限于API操作类型，无法根据交易上下文进行动态决策65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/872988API
curl https://kongchang.com/api/v1/knowledge/claims/872988MCP
get_claim(id=872988)