Announcing new Tech Council members

[amithanda]

The Tech Council was established as the primary technical governing body for the Universal Commerce Protocol (UCP) to lead the technical direction and foster open-source collaboration.

To match the strong interest by contributing organizations, the UCP Governing Council, which oversees the protocol’s overall governance, is excited to announce that we are expanding our Tech Council seats to 16, welcoming 5 new members:

New Tech Council members:

• Greg Smith (Amazon)
• James Andersen (Meta)
• Patrick Jordan (Microsoft)
• Prasad Wangikar (Stripe)
• Scot DeDeo (Salesforce)

The new members join current Tech Council members, including Google, Shopify, Etsy, Target, and Wayfair. They bring the experience and reach necessary to ensure UCP benefits every developer and business, regardless of their platform or payment provider. Having this level of leadership onboard is a win for the entire ecosystem, as we build a future of agentic commerce that stays open, integrated, and accessible to all.

Excited for what's ahead!

[haunic]

Amit, once you want to enter the travel space (for a travel domain working group), count on us (Amadeus) and our customers (airlines, hotels, travel agencies). We are already heavily testing UCP, formalizing suggestions, and talking to our beloved Google contacts.

[reshadat]

+1 to forming a travel WG. Useful to know Amadeus is already testing and formalizing.
The gaps I keep landing on when sketching where shopping stops being a clean fit:

• Hold-against-inventory distinct from checkout's session TTL
• Multi-party buyer : cart and checkout expose a single buyer shape, but travel routinely splits booker, traveler, and payer
• Price TTL, since travel prices move in seconds via yield management
• Standardized modify / reprice / reconfirm with fare-difference accounting (Order has open-string adjustments, but not a shared travel modify contract)
• Multi-supplier itinerary as a composed entity rather than independent line items

Some of these probably extend cleanly off shopping. Others (multi-party identity, hold-against-inventory) feel structural enough to want capability-level primitives.

Would be useful to align on which gaps Amadeus has found absorbed by extensions versus which feel structural. Happy to contribute design work.

[wherka-ama]

Amit, once you want to enter the travel space (for a travel domain working group), count on us (Amadeus) and our customers (airlines, hotels, travel agencies). We are already heavily testing UCP, formalizing suggestions, and talking to our beloved Google contacts.

@amithanda, @pemamian : thatnks a lot for adding Amadeus logo ❤️ That's great to be amongst such a nice company 👍 However, just a tiny little request coming from our branding team - do you mind incresing it a little bit please?
I've already created a PR: #488

CC: @haunic

[davidsolheim]

Such an exciting time to be in software development!

[bbasantgit]

I am a digital tech leader for a retail company . How can I join , learn and contribute to this UCP Tech Council ?

[amarshat]

Congrats to the new Tech Council members — great to see the ecosystem forming.

I’m Amar from Paysafe. We operate across wallets and acquiring, so UCP aligns closely with how we’re thinking about agentic commerce.

I’ve been exploring a simple layering:

UCP checkout → AP2-style authorization → wallet-native settlement

Specifically, using wallet-to-wallet transfers as the execution layer for a UCP payment step, without exposing reusable payment credentials to agents.

Putting together a short note on this - focused only on the settlement layer. Would love guidance on how best to engage or contribute this to the discussion.

[mattsuma]

Count on us (Satsuma.ai) to open omnichannel retail, restaurant, and automotive!