Adyen announced Adyen Agentic this week, and the most strategically useful line in the release is the one most coverage will skip.
"Without having to bet on which ecosystems ultimately win."
That is the protocol-fragmentation problem stated plainly, and it is the question every commerce leader is quietly stuck on. UCP, ACP, AP2, Meta's AI checkout, whatever ships next quarter. Each agentic platform operates on different protocols, different product data formats, and different cart and checkout requirements. Integrating with each one individually is a series of bets on which platforms matter, made before anyone knows the answer.
Adyen's pitch is to be the abstraction layer that removes the bet. Integrate once. They translate that integration across every protocol and platform. The merchant participates in new channels without rebuilding each time the landscape shifts.
The structure is worth noting because it maps to how agentic commerce actually decomposes. Three layers: Agentic Feed for product and inventory distribution, Agentic Cart for checkout and order orchestration, Agentic Payments for authentication and fraud. Discovery, cart, transaction. The same three layers every brand has to solve, packaged as infrastructure.
The detail that matters most for brands: merchant of record preservation is built into the payments layer. This is the same architectural choice Google made with Universal Cart and Visa made with Intelligent Commerce. The platforms have collectively decided that the merchant stays the merchant of record. That question is now settled across every major agentic commerce rail.
What is not settled, and what an abstraction layer cannot solve for you, is whether your product data is good enough to be useful once it is translated. Adyen Agentic distributes your catalog across every platform. If that catalog is incomplete, unstructured, or inaccurate, the universal translator faithfully distributes incomplete, unstructured, inaccurate data everywhere at once.
The abstraction layer solves the integration problem. It does not solve the data quality problem. Those remain two different builds, and the second one is still the brand's job.
The protocol-agnostic infrastructure thesis is right. Build for the layer, not the platform. Just remember that what flows through the layer is still yours to get right.