Salesforce, Stripe, and Commerce Inc Join UCP: What It Means

Three New Entrants in One Week

In the span of four days in March 2026, the UCP ecosystem picked up three significant new participants: Salesforce Commerce Cloud, Stripe, and Commerce Inc. Each brings something different. Salesforce brings enterprise-scale merchant coverage. Stripe brings native payment token handling that simplifies a part of UCP integration that has been rougher than it should be. Commerce Inc is a newer entrant building full UCP platform support from the ground up.

This post covers each one: what they announced, what the technical integration looks like, and why it matters.

Salesforce Commerce Cloud

Salesforce Commerce Cloud (SFCC) powers hundreds of enterprise retailers, including brands across fashion, consumer goods, and specialty retail. These are merchants that have historically required custom integration work to reach programmatically. Adding UCP support to SFCC means an agent that implements the standard UCP spec can now reach a large slice of enterprise retail without bespoke partnerships.

What Salesforce Announced

Salesforce is adding UCP as a native checkout channel in Commerce Cloud, alongside existing channels like web storefront and mobile app. The implementation is being built on top of Commerce Cloud's existing Order Management System (OMS), which means UCP-initiated orders flow through the same fulfillment pipeline as all other orders. Merchants do not need a separate integration or a separate inventory pool.

The capability set in the initial release covers Catalog Access, Checkout, and Order Management. Cart Management and Identity Linking are listed as Q2 2026 additions. This is a meaningful gap: agents targeting SFCC merchants at launch will need to use the sessionless checkout path rather than the full cart-based flow. Given that SFCC merchants typically have larger catalogs with more variants and configurable products, this is a limitation worth noting.

Technical Integration Points

SFCC's UCP implementation is exposed through Commerce Cloud's existing API gateway. The /.well-known/ucp manifest for SFCC merchants points to endpoints under the standard Commerce Cloud API hostname. This means if you are already familiar with SFCC's API structure, the UCP endpoints will feel familiar: the same authentication patterns, the same regional deployment model, the same rate limiting infrastructure.

One SFCC-specific consideration is merchant configuration. SFCC is a multi-tenant platform, and each merchant instance is configured independently. UCP capabilities are enabled at the merchant level by their Salesforce administrator. An agent cannot assume that all SFCC merchants support UCP just because the platform does. The /.well-known/ucp manifest is the authoritative source: if the manifest does not include a checkout endpoint entry, that merchant has not enabled UCP checkout.

Catalog response schemas from SFCC merchants include a catalog_source: "sfcc" field in the metadata. This is not required by the UCP spec but is consistent with SFCC's practice of including platform provenance in API responses. Some agents are using this to route SFCC-originated catalog data through SFCC-specific enrichment logic, though the standard UCP product schema is fully sufficient for most use cases.

Why Enterprise Merchants Matter

SFCC's catalog of merchants fills a gap that Shopify and Google Shopping do not cover well. Shopify dominates independent and mid-market DTC brands. Google Shopping aggregates across many merchant types. SFCC powers many of the large, branded retailers that consumers associate with specific names rather than platforms. Getting these merchants into the UCP ecosystem expands the range of agent-accessible commerce meaningfully.

For an agent that wants to help a consumer shop for, say, athletic gear, the difference between UCP-accessible merchants and non-accessible merchants is increasingly the difference between useful and not. SFCC's entry makes a large category of brand-direct purchasing accessible without browser scraping or manual checkout.

Stripe

Stripe's announcement is technically the most interesting of the three. Stripe is not implementing UCP as a platform or merchant. Stripe is implementing the UCP Payment Token Exchange specification directly in its API, which changes how the payment leg of UCP transactions works for any merchant using Stripe as their payment processor.

The Problem Stripe Solves

The UCP payment flow has always been conceptually clean: consumers pre-authorize a payment method through an identity provider, the agent passes a one-time payment token at checkout, and the merchant's payment handler resolves the token against the actual payment network. In practice, the token exchange step has been a pain point.

Before Stripe's implementation, a merchant using Stripe for payment processing had to build a custom bridge: receive the UCP payment token, call out to the identity provider to resolve it against a Stripe payment method, then use the Stripe API to complete the charge. This bridging logic was non-trivial, had to handle token expiry, and was a source of implementation bugs in several early UCP merchant integrations.

Stripe's implementation eliminates the bridge. Stripe now supports UCP payment tokens as a native payment method type in its API.

How It Works Now

A merchant using Stripe can pass a UCP payment token directly to the Stripe Charges or Payment Intents API:

POST /v1/payment_intents
Content-Type: application/x-www-form-urlencoded

amount=4999&
currency=usd&
payment_method_types[]=ucp_token&
payment_method_data[type]=ucp_token&
payment_method_data[ucp_token][token]=ucppt_01HXYZ...&
payment_method_data[ucp_token][consumer_identity]=cit_01HABC...&
confirm=true

Stripe handles the resolution against the identity provider's token registry, validates that the token is unused and unexpired, charges the underlying payment method, and returns a standard Payment Intent result. The merchant's code does not change materially from how it handles any other Stripe payment. Stripe absorbs the UCP-specific complexity.

Implications for Developers

This significantly lowers the bar for UCP checkout implementation on Stripe merchants. If you are a developer building a Shopify-independent UCP checkout for a merchant that uses Stripe, you no longer need to implement the token exchange yourself. You pass the UCP payment token to Stripe the same way you would pass a card token.

There is also a webhook consideration. Stripe fires a payment_intent.succeeded event with a payment_method_type: ucp_token field when a UCP-sourced payment completes. Merchants who are tracking revenue by source should update their Stripe webhook handlers to recognize this payment method type and attribute it correctly.

Stripe's UCP support is live in all regions where Stripe operates. The Stripe UCP documentation covers the token schema, error codes specific to UCP token validation failures, and testing procedures using Stripe's standard test mode.

Broader Payment Ecosystem Impact

Stripe processing a large share of online commerce, its native UCP support creates a forcing function for other payment processors. Adyen has been working on UCP token support, and Stripe shipping first increases the competitive pressure to finalize that work. For the UCP payment token exchange to become truly universal, every major payment processor needs to support it natively. Stripe's implementation is a significant step toward that outcome.

UCPList tracks payment handler UCP capabilities in the payment handlers category. The Stripe listing has been updated to reflect native UCP token support as of March 2026.

Commerce Inc

Commerce Inc is less well-known than Salesforce or Stripe, but its UCP announcement is worth understanding because of the approach it represents.

Commerce Inc is a platform founded in 2025 with UCP as a core design assumption rather than a retrofit. Where Shopify and Salesforce are adding UCP support to platforms built before UCP existed, Commerce Inc built its merchant tooling with UCP-native APIs from the start.

What Commerce Inc Offers

Commerce Inc provides a full commerce platform stack: product catalog management, order management, payment processing integration, and fulfillment coordination. What distinguishes it is that every layer of this stack exposes a UCP-compliant interface by default. There is no separate "enable UCP" toggle. Merchants on Commerce Inc are UCP-capable from the moment they create their store.

The platform supports the full March 2026 UCP capability set: Cart Management, Catalog Access, Checkout, Identity Linking, and Order Management. This makes it one of the few platforms currently at full spec parity.

Technical Architecture

Commerce Inc uses a UCP-first API design, meaning the UCP endpoint schema is the primary schema, not an adapter layer over a proprietary schema. This has practical consequences for response consistency. Product schemas from Commerce Inc merchants closely match the canonical ucp.dev specification examples, with minimal proprietary extensions. Agents targeting Commerce Inc merchants encounter fewer schema edge cases than they do with platforms that bolt UCP onto an existing proprietary API.

The platform also provides a developer sandbox that supports all UCP capabilities, including simulated edge cases: inventory depletion mid-session, price changes between catalog fetch and checkout, token expiry during a cart session. This is useful for agent developers who want to test error handling without relying on production merchant behavior.

Why It Matters for Ecosystem Health

Commerce Inc's significance is not its current merchant count, which is smaller than Shopify or SFCC. Its significance is what it demonstrates: that building a UCP-native platform is viable, and that the protocol is mature enough to serve as a primary API contract rather than a secondary integration target.

This matters for the long-term trajectory of UCP adoption. If the only path to UCP support is retrofitting existing platforms, adoption will always be slower and more inconsistent than the spec warrants. UCP-native platforms like Commerce Inc create a reference point for what clean UCP implementation looks like and raise the quality bar for retrofitted implementations.

What to Watch

The addition of Salesforce, Stripe, and Commerce Inc in a single week indicates that enterprise momentum behind UCP is accelerating. The practical areas to watch over the next quarter:

Salesforce's Cart Management and Identity Linking timeline. If those ship in Q2 as announced, SFCC merchants become full-capability UCP targets and enterprise agent use cases become significantly more tractable.

Other payment processors following Stripe. Adyen in particular: many SFCC and enterprise merchants use Adyen as their primary processor. Adyen shipping native UCP token support would remove the remaining payment bridging complexity for a large merchant segment.

Commerce Inc merchant growth. The platform is actively recruiting merchants from Shopify and SFCC with UCP-native tooling as a differentiator. If it gains meaningful merchant count, it becomes a genuine third-tier UCP platform alongside Shopify and Google Shopping.

All three entrants are now listed in the UCPList directory. The Stripe entry is in payment handlers. Salesforce Commerce Cloud and Commerce Inc are in platforms. Capability status and verification dates are kept current as new features ship.