Commerce Agents Reference — Development skill for Claude Code

Claude Commerce Agents for any merchant on any payment processor

*A reference implementation of Anthropic's Claude Commerce Agents blueprint for merchants whose payments run through Stripe, Adyen, Worldpay, CyberSource or Clover, with Shopify's example running beside it unchanged.*

What this is

On 2 September 2026 Anthropic published the Claude Commerce Agents blueprint ([anthropics/commerce-agents](https://github.com/anthropics/commerce-agents)): two assistants a merchant runs on its own site, one that helps customers find, compare and buy, and one that helps staff run the store. The blueprint ships the conversation loops, the safety gates, the skills and the presentation cards. It ships no payment step: a store implements a small set of backend functions, and the checkout is a link the server attaches to a card after the model has finished its turn.

Shopify published an example the same week ([Shopify/claude-for-commerce-examples](https://github.com/Shopify/claude-for-commerce-examples)) in which that link opens Shopify's own checkout page. A merchant on any other stack has to supply the link, the tender figures, the orders and the payments reporting itself. This reference implementation supplies them for five processors and leaves the blueprint untouched.

It adds three things to the blueprint.

• A processor layer. psp_commerce/gateway.py defines one PaymentGateway protocol. psp_commerce/adapters/ holds one HTTP client per processor and a simulated gateway that runs every demo and test with no credentials. A merchant picks one of four checkout integration models (the processor's hosted page, the merchant's own page over the processor's API, the processor's drop-in component inside the merchant's page, or a payment link) with one environment variable.
• A third-party layer. Every merchant serves the Universal Commerce Protocol (UCP) over the Model Context Protocol (MCP), with the same discovery document and tool names Shopify's stores serve