The Universal Commerce Protocol's Governing Council has approved the Payments Tech Council charter, and nominations for the founding cohort are now open. Organizations have until July 28 to apply, with review targeted for August 4 and the founding membership expected to be announced around August 11.
This is the third governance body to stand up in the protocol's domain-council wave — and it's the one that matters most.
What was announced
Per the official announcement, the Payments Tech Council will operate under the UCP Governing Council alongside the other Domain Technical Councils, with a remit to:
- drive interoperability within the payments ecosystem,
- expand the choice of payment options available through the protocol,
- incorporate verification flows to increase security, and
- support diverse international market needs.
Selection is based on payments domain expertise, ecosystem representation, and — notably — demonstrated contributions to the protocol's health and adoption. Applications go through the nomination form; the announcement is explicit that candidates should be committed to UCP's "open, vendor-agnostic approach."
Key dates: nominations close July 28 · review completes ~August 4 · membership announced ~August 11 (tentative).
What the charter actually commits to
The approved charter — proposed jointly by Google and Shopify — lays out a three-phase roadmap:
- Phase 1: the payment instruments that dominate US-type markets — card tokens (DPANs), e-wallets, and buy-now-pay-later — plus common challenge flows including 3DS2, and standardization of the risk data hosts share with businesses and payments partners.
- Phase 2: geographic and instrument expansion — local payment methods including UPI and APAC e-wallets, stored value and split-tender, "Agentic Tokens" (network cloud tokens), and loyalty constructs like pay-with-points.
- Phase 3: preparation for Europe's 2027 Digital Payment Credentials enforcement with identity-linked payments for restricted verticals, and expansion beyond consumer-to-business flows into agent-led remittances, peer-to-peer, and agent-to-agent payments.
Readers who follow the repo will notice how much of Phase 1 is already in motion: 3DS2 support is in active review, and standardizing what risk data platforms share is precisely the debate running through the current signals proposals. The charter doesn't start the work so much as give work already sprinting a place to live.
Why this is the council that matters
Regular readers will recognize the shape of this moment. Our July ecosystem report documented the capability cliff: across the verified fleet — more than 11,000 stores at the July census, 12,900+ verified today among nearly 15,000 monitored domains, growing daily — checkout is declared nearly universally, and declared payment capability is zero. The fleet is staged at the payment line, waiting for the rails, the standards, and the trust layer to settle.
The Payments Tech Council is the standards half of that sentence getting an org chart. Consider what's already in flight on the payment seam: the payment-terms RFC (#587) went from proposal to two candidate implementations in a single week; the ap2_mandate authorization flow and signature encoding are being hardened in public; saved payment methods just got routed through identity-linking infrastructure. The work was already sprinting — what it lacked was a dedicated governance body to own it. As of August 11, it will have one.
There's a structural detail worth noticing, too. The Food Ordering and Lodging councils that preceded this one are vertical — each owns one industry's slice of the protocol. Payments cuts across every vertical: the same seam serves retail, grocery, travel, and food ordering, which is precisely why the spec has been migrating payment constructs from the shopping vertical into the common namespace. The Payments TC is the protocol's first horizontal council — its decisions will touch every transaction the ecosystem ever processes.
Who should be applying
The announcement casts a deliberately wide net: payment networks, processors and PSPs, wallets, BNPL providers, issuers, and payments-infrastructure builders all fit the "payments domain expertise" brief. The selection criteria reward organizations that have already shown up in the repo — which, based on the public record of the past two months, is a meaningfully larger group than it was in the spring.
If your organization processes, moves, verifies, or secures payments and has UCP ambitions, the form closes July 28. That is not a long runway — it suggests the Governing Council wants the founding cohort seated before the next spec release lands.
Where we stand — and what we'll measure
UCP Checker will not be seeking a seat. Our position hasn't changed since the first council formed: the meter doesn't join the bodies it measures. Independence is what makes our data useful to every participant — including, eventually, every member of this council.
What we will do is what we always do: track the output — from the public record, measured the same way for every organization involved, member or not. When the founding membership is announced, we'll report it as published: who holds seats, and how the cohort maps onto the capability and adoption data we already publish. When the council's decisions become spec, they'll appear on the protocol tracker. And when spec becomes manifests in the wild, it shows up in the capability data and the monthly ecosystem reports — where, one day soon, the payment line finally moves off zero.
The nomination window closing on July 28, the review on August 4, the announcement on August 11 — and a spec release targeted for the same month. August is shaping up to be the month the money layer of agentic commerce gets serious. We'll be watching all of it.
About UCP Checker
UCP Checker is the independent validation and observability layer for the Universal Commerce Protocol. We crawl, validate and grade every public UCP manifest we can find, run the merchant directory, the UCP Score and live adoption stats, and track the spec as it evolves so you don't have to — measured the same way for everyone, without picking winners.
Sources
- Inviting nominations for UCP Payments Tech Council — official announcement
- Payments Tech Council Charter Proposal (#594)
- Nomination form
- State of Agentic Commerce — July 2026 — the capability cliff
- RFC #587: Payment terms and scheduled payments
- Previous governance coverage: UCP Tech Council Expands · Attribution Ships into Core · Lodging Charter · Food Ordering Charter