OpenAI and Meta have joined forces to bridge the "last mile" of Agent commerce

Core Viewpoint

Personal Agent Protocol, PPP

Sierra and Meta jointly released the Personal Agent Protocol Poppy v1.0 | Image source: Sierra official blog

In the past, personal assistants could only access enterprise websites as invisible visitors, making it difficult for merchants to identify who was coming, and they were reluctant to entrust sensitive operations like checking orders, changing addresses, booking flights, or financial pre-approvals to them.

The core issue that Meta and Sierra's Poppy aims to solve is trust; it allows enterprises to confirm three things when a request is received using cryptographic methods—which assistant is knocking, which user it represents, and what permissions it has.

The core of the Poppy protocol consists of "doorplate," "foundation," and "bi-directional authorization."

"Doorplate." Enterprises integrating Poppy will place a configuration file at the standard path /.well-known/poppy on their websites. You can think of it as a visitor guide posted at the store entrance, clearly stating which communication endpoints are open, how to log in, and what operations are allowed. When an assistant comes knocking, it no longer has to guess how to click web buttons; it can refer to the doorplate to act according to the rules.

"Foundation." Poppy does not overturn the existing communication methods of the internet; it is directly built on OAuth authorization, HTTPS encrypted transmission, OpenAPI, and model context protocols. If a user is only checking product prices, the assistant can converse as an anonymous visitor; once account operations are involved, authorization login is required to verify the user's identity.

"Bi-directional Authorization." On the user side, they can decide whether to grant the assistant read-only access or allow modifications and transactions; on the enterprise side, it defines how far external assistants can go on its territory. Only when both sides agree does an interaction count as established.

From the release information, it can be said that Sierra and Meta's collaboration to promote this protocol is very complementary. Sierra, founded by former Salesforce co-CEO Bret Taylor and former Google executive Clay Bavor, focuses on helping enterprises build their own customer service agents, naturally sitting on the "receiving" side; Meta's personal assistant Muse is a typical "visitor," needing to knock on countless websites' doors. Both the receiving and visiting parties contributed equally to establish this standard. Currently, when Muse accesses participating sites, it defaults to prioritizing the Poppy protocol.

Open protocols often face the cold start problem of which came first, the chicken or the egg. This time, the real enabler for Poppy crossing the threshold is the e-commerce infrastructure giant Shopify.

At the time of the protocol's release, Shopify automatically enabled and generated Poppy discovery files for every merchant in over 175 countries without requiring any manual configuration from merchants. Coupled with over 100 design partners, including representatives from Delta Airlines, 1Password, Okta, and Cloudflare, this access control system had a significant coverage on its first day.

Cashless Agents

Having solved the entry issue, the next challenge is payment.

Most people's instinctive reaction to letting an Agent pull out their wallet is resistance. OpenAI's ChatGPT Wallet is designed with a clear purpose: to allow the Agent to push transactions to completion without ever touching real financial information.

In the actual shopping process, users can have their dot search for products, compare prices, add items to the cart, and prepare the checkout page. However, once it comes to payment, the dot must stop and return the decision-making power to the human. After the user personally verifies the product list, total amount, and selected bank card, authorization must be completed through biometric methods such as facial recognition or fingerprint scanning for the transaction to be released.

OpenAI personal assistant dot (Rufus) initiates "Review purchase" checkout confirmation in conversation | Image source: OpenAI

The more critical security design is hidden in the background. Whether it's the running dot or the merchant receiving payment, neither will ever see your real credit card number throughout the transaction. After user authorization, the cooperating card organization network generates a one-time payment credential that includes a temporary card number, security code, and expiration date. The merchant only receives this temporary information, and your real card number remains concealed.

To implement this mechanism, OpenAI collaborated with American Express, Mastercard, and Visa, fully retaining the original credit card points, benefits, and chargeback protection. OpenAI also clarified at the launch that the ChatGPT Wallet is not a cryptocurrency wallet, does not operate on blockchain or stablecoin payments, and runs entirely on traditional fiat banking and card organization infrastructure.

From the public information, the commercial motivations of all parties are clear. For OpenAI, if personal assistants only provide suggestions and links, they will remain in the shopping guide phase forever; by keeping the checkout closed-loop within the conversational ecosystem, dots can transition from suggesters to closers. For traditional card organizations, once agents become new consumption entry points, no one wants to see transaction traffic diverted to new payment networks. Through this collaboration, the three major card organizations seamlessly reconnected the new channel to their clearing networks.

Even so, OpenAI's first step remains quite restrained.

The initial rollout of ChatGPT Wallet is limited to U.S. ChatGPT Pro subscribers aged 18 and older, supporting eligible U.S.-issued bank cards, including Amex, Visa, Mastercard, and cards issued by Chase. From the public information, it seems they want to test the waters with paying users, likely aiming for more stability in risk control.

When Giants Collaborate

Comparing these two pieces of news side by side reveals an interesting intersection.

In the initial core partner list for Poppy, Shopify, Stripe, PayPal, Visa, and Mastercard are all included; shifting to the ChatGPT Wallet side, the development partners are also Amex, Visa, and Mastercard. The only entities that truly span both sides are Visa and Mastercard, which appear on both the Poppy list and as Wallet development partners.

An even more intriguing detail is that OpenAI's name is prominently listed among the more than 100 design partners for Poppy.

The first batch of over 100 design partners for the Personal Agent Protocol, including OpenAI, Visa, and Mastercard | Image source: Sierra

In the consumer market, Meta's Muse and OpenAI's dots are direct competitors, both striving to capture the first entry point users open daily. However, once it comes to the enterprise access layer, the two giants find themselves at the same conference table, preparing to share the same access card. The reason is clear; airlines or retailers are unlikely to want to maintain a set of incompatible interfaces for each model vendor. The consumer side can showcase their strengths to grab entry points, but the business side must co-build the same pass.

There is also a signal on the technical front. Automatic transactions between agents were once seen by many as a potential scenario for stablecoins. However, from this round of implementation, both financial and e-commerce infrastructures have chosen a "standard authorization protocol plus one-time virtual card credential" progressive route, temporarily setting aside encryption solutions. By first integrating into mature risk control and clearing tracks, this route is the most hassle-free for traditional business systems.

Of course, there remains a suspense in the public information.

Poppy and ChatGPT Wallet have not yet clarified whether they are interconnected. In the future, when a user's dot enters a Shopify store that has activated the Poppy protocol, whether it can smoothly complete the handshake and then use the Wallet for payment remains to be verified later.

The Autonomy of Agents Stops at the Shopping Cart

By looking at Poppy's bi-directional authorization and ChatGPT Wallet's mandatory biometric identification together, one can see the common bottom line drawn by the industry—Human in the loop.

Whether it's reading data, modifying orders, or deducting real money, the assistant's autonomy is precisely paused in front of the shopping cart. It can compare prices across the internet for you and fill in the checkout fields, but ultimately, it is still the user who must flip the switch to confirm.

This design maintains security but also leaves several unanswered questions.

For example, the gray area of transaction liability. If the assistant misunderstands your intent when selecting products, or if it is misled into placing an order by hidden malicious prompts while browsing the web, even if you ultimately use facial recognition, whether the existing chargeback protection from banks can cover "the assistant's mistakes" has not been defined in public information.

The coverage and thresholds for participating in agreement transactions still exist. Shopify has driven a massive number of merchants, but when will countless long-tail websites on the internet display the Poppy sign? On the other hand, ChatGPT Wallet is currently only available to Pro subscribers in the United States; how much longer other markets and regular users will have to wait remains uncertain.

Moreover, the mandatory biometric identification for every transaction indeed maximizes the sense of security. But imagine a future where you are accustomed to having the assistant order coffee and buy daily necessities for you every day; having to pull out your phone to scan your face for every little task could turn the promised convenience of a fully automated assistant into new operational friction in high-frequency scenarios.

At this stage, where the assistant is not yet perfect and social trust has not been established, holding tightly onto the final "click to confirm" power may be the cost the industry must pay to gain entry, and it also determines the pace of commercialization for personal assistants.

Next time, when you ask the AI assistant to change the delivery address and conveniently settle the bill, it will no longer be treated as a web crawler kept outside. It will present its compliant identity to enter the store, understand the sign, fill the shopping cart, and then stop at the checkout page, handing the phone to you, waiting for your face to align with the camera.

Today's facial recognition is the last threshold before people entrust their assistants with trust. But one day, when everyone is accustomed to letting programs handle their daily consumption, will this confirmation become just a routine click that people casually dismiss? Just like all the authorization agreements that websites and references make you sign, almost no one truly understands them or is willing to read them carefully.