UCP Checker
Industry

UCP Regional Working Groups: APAC, EMEA and LATAM

· 20 November 2026 · 9 min read

UCP is opening three working groups by region. On 20 November 2026 the protocol's maintainers invited nominations for UCP for APAC, UCP for EMEA and UCP for LATAM, three time-bounded Domain Working Groups sponsored jointly by the Shopping and Payments Tech Councils. Each has a charter on GitHub: #1117, #1118 and #1119.

None of them will write spec. Each will spend eight weeks mapping what a full shopping journey in its region needs from UCP, then hand the councils a roadmap readout and a ranked list of changes. Here is what each charter covers, who can take part, and what happens next.

What are the UCP regional working groups?

The UCP regional working groups are three eight-week Domain Working Groups, one each for APAC, EMEA and LATAM, that will identify the changes UCP needs to support end-to-end shopping and payments in those regions. All three charters start from the same observation, in the APAC charter's words: "early UCP launches focused on US commerce flows (card-based checkout, single-seller catalogs, Western postal addresses, tax added at checkout, and pickup at the seller's own stores)".

Until now, regional needs have reached the spec one issue at a time: a payment method here, an address field there. The charters say the point of a group is to look at the whole journey at once: "Bringing regional contributors together makes it much easier to look at the full [regional] shopping journey and help the Tech Councils have a broader view on UCP changes required to support region-specific requirements."

Each group delivers:

  • A roadmap readout: "A technical report for the Tech Councils and Governing Council covering priority shopping journeys and prioritized list of enhancements to UCP."
  • Optionally, follow-up recommendations, such as further working groups for market-specific needs.

What each region is looking at

Each charter lists areas the community has already raised, with the issues and PRs behind them.

Area APAC (#1117) EMEA (#1118) LATAM (#1119)
Payments Real-time and app payments (UPI Collect, Intent and Circle), hosted checkout handlers Account-to-account and bank redirects (iDEAL, Blik, Swish, SEPA), pay by invoice, BNPL Instant transfers and cash vouchers (Pix, Boleto, OXXO, Khipu)
Payment completed later QR codes, vouchers and payment codes (convenience store pay, bank transfer) Payments that settle via an in-session QR code or after checkout Barcodes or vouchers completed after the checkout session
Authentication — Strong Customer Authentication: delegated authentication, bank-app redirects, network tokens, exemptions when an agent starts the checkout —
Pricing and tax Tax-inclusive catalog and line-item prices, local currency formatting, platform-funded vouchers VAT-inclusive prices, multi-rate VAT breakdowns, prior-price disclosures Card installments with or without interest, local currency display, payment-method-funded discounts
Tax identity and invoices — — Payer tax IDs (CPF, CNPJ, RUT) and e-invoices (NF-e, CFDI, factura/boleta)
Addresses Province, city, district and street hierarchies — Neighbourhood (colonia, bairro), street number, building details, delivery reference notes
Pickup and delivery — Carrier parcel lockers and third-party pickup points (PUDO networks) Digital delivery of vouchers and non-physical goods
Marketplaces Offers from several sellers, seller attribution, checkouts that create more than one order Merchant-of-record attribution across multi-seller catalogs and orders Multi-seller catalogs, seller attribution, multiple orders per checkout
Consumer rules — Statutory right of withdrawal (cooling-off) on top of the return policy extension —

A dash means that charter's table of community issues doesn't list the area. The scope sections are broader: every charter covers addresses and pickup or delivery, pricing, and "local rules that affect schemas" (disclosures, consent fields, invoice data).

Some threads run through all three. Delayed payment confirmation (#641, #778, PR #1075) is cited by every charter, and so is marketplace support (#810 and its PRs). Address granularity (#447) is cited by APAC and LATAM; tax-inclusive pricing (#650, PR #681) by all three.

What UCP already has

The charters don't start from zero. Each names the building blocks it expects to extend:

  • Everywhere: context for language, currency and locality hints; money in ISO 4217 minor units; payment handlers under vendor namespaces.
  • EMEA: dev.ucp.common.payment.authentication for 3DS challenges, dev.ucp.shopping.buyer_consent, dev.ucp.shopping.policy.return, and unit_price and list_price for per-unit and reference pricing.
  • LATAM: dev.ucp.common.payment.terms (payment_term and payment_schedule) for installment schedules, and dev.ucp.common.payment.split_payments for paying with more than one instrument.

What is out of scope

All three charters rule out the same three things:

  • "Writing or merging spec changes." The groups deliver recommendations and starter proposals; spec changes still go through normal Tech Council review.
  • "Adding single-vendor payment handlers to the core spec." A provider's handler stays self-hosted under the provider's own namespace.
  • "Changing UCP's core architecture": capability negotiation, versioning and transports.

Who is running them and who can join

The charters name Amit Handa (Google) and Ilya Grigorik (Shopify) as proposed chairs of all three groups, with Twum Djin (Stripe) as a third proposed chair for EMEA. The Food and Lodging Tech Councils "may be consulted on vertical topics".

Each group needs at least three organisations, per the governance process. The nominations post asks for "agent platforms, regional marketplaces and retailers, commerce platforms, and payment providers active in APAC, EMEA, or LATAM" to review the charters and submit a form:

The nominations post doesn't give a closing date.

How it got here

Date Step
13 Nov 2026 The Governing Council reviews draft charters for regional working groups; members "agreed in principle with the proposals" and complete a final review before publishing them
20 Nov 2026 Charters published as #1117, #1118 and #1119; nominations open
Next The Governing Council approves each charter and its participant list; the eight weeks start then

The groups arrive as other councils open. Nominations for the Local Services and B2B Procurement Tech Councils opened on 14 November, and food got its own checkout draft a day earlier.

What happens next

Approval of charters and members. Each group runs "for eight weeks following Governing Council approval of the charter and participant roster". Neither has happened yet, so there is no start date.

Meetings in the open. Per the governance process, agendas are posted 24 hours before each meeting and notes are published within a week.

Readouts, then proposals. At the end of the eight weeks each group hands its readout to the Tech Councils and the Governing Council. Any spec change that follows goes through the normal council process, as a proposal like any other.

What it means

For stores and platforms outside the US: this is the stage at which regional needs get onto UCP's list. If your checkout depends on Pix, iDEAL, UPI, VAT-inclusive prices, parcel lockers or a tax ID on the invoice, the charter for your region is where that gets written down.

For payment providers: single-vendor handlers stay outside the core spec. The questions are about shared shapes, such as payments that complete after checkout, SCA when an agent starts the purchase, and installments.

For agent builders: nothing changes in the protocol today. The readouts are a useful early signal of what agents will be asked to handle: payments that complete after the session ends, tax-inclusive totals and multi-seller orders.

What we'll watch

  • The member lists and Governing Council approval for each group.
  • The three readouts: which changes each region ranks first, and where the regions agree.
  • Proposals that follow, on our Changes to UCP tracker, which lists every open proposal and recent merge, synced daily.

FAQ

Does UCP work outside the US? Yes, with gaps. UCP already carries language, currency and locality in context, uses ISO 4217 minor units for money and lets payment providers publish their own handlers. The regional working group charters say early launches focused on US flows and list what's missing for APAC, EMEA and LATAM.

What are the UCP regional working groups? Three time-bounded Domain Working Groups (UCP for APAC, UCP for EMEA and UCP for LATAM), sponsored by the Shopping and Payments Tech Councils. Each spends eight weeks producing a roadmap readout and a ranked list of changes for its region.

Will UCP support Pix, UPI or iDEAL? The charters name them as areas to look at: Pix, Boleto and OXXO for LATAM, UPI for APAC, and iDEAL, Blik, Swish and SEPA for EMEA. The groups recommend; they don't add payment methods to the spec, and single-vendor handlers stay outside the core spec.

How do I join a UCP regional working group? Submit the nomination form linked from the nominations post. The groups want agent platforms, regional marketplaces and retailers, commerce platforms and payment providers active in the region.

Who chairs them? The charters propose Amit Handa (Google) and Ilya Grigorik (Shopify) for all three, plus Twum Djin (Stripe) for EMEA.

When do they start? Eight weeks run from Governing Council approval of each charter and its participant list. That hasn't happened yet.

Is a working group the same as a tech council? No. A working group is time-bounded and hands its results to existing councils. A tech council is a standing body that owns part of the spec.


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, live adoption stats, the vertical guides and the authority-bound vendor map, and track the spec as it evolves so you don't have to — measured from two vantages (what a business declares, and what actually happens when an agent transacts), the same way for everyone, without picking winners.

Sources

Related coverage: UCP Agentic Donations working group · UCP's Bulk Product Discovery working group · The UCP Payments Tech Council · UCP payment extensions and Mercado Pago

What does a UCP agent find at your store?
Check it once and it gets its own status page.
Check a store

Keep reading

11 Nov 2026 UCP Agentic Donations Working Group: What It Will Study Industry · 9 min 11 Nov 2026 UCP B2B Procurement Council Approved: What Happens Next for Business Buying Industry · 7 min 4 Nov 2026 UCP Local Services Council Approved: What Happens Next for Bookings Industry · 6 min