UCP Agentic Donations Working Group: What It Will Study

UCP is getting a working group for donations. At its 30 October 2026 meeting, the UCP Governing Council passed the charter for an Agentic Donations Domain Working Group, filed as issue #924. On 5 November it told the proposed chair to invite nominations for the group's members.

The working group won't write a donations spec. Its job is a technical report on how giving maps onto the protocol UCP already has, and where it doesn't fit. Here is what the charter asks for, how it got here, and what happens next.

#What is the Agentic Donations working group?

The Agentic Donations working group is a time-bounded UCP group, sponsored by the Shopping Tech Council, that will study how an agent can help someone find a cause and give to it. It consults the Payments Tech Council. The charter's example: "Help me find an organization supporting wildfire recovery, and donate $50 once I approve."

Its one deliverable is a public technical report that recommends "the best way to map the Donations area to standard UCP constructs and existing Tech Councils". The Governing Council then uses the report to decide what comes next: work in the existing councils, focused proposals, another time-bounded group, or no new standard at all.

A working group isn't a council. At the 16 October Shopping Tech Council, the minutes record that a working group's deliverables "get absorbed into existing councils", while a council is a permanent swim lane of its own. Local Services and B2B Procurement got councils. Donations got a scoped working group under Shopping.

#Why donations aren't just checkout

The charter starts from what UCP already has: profiles, capability discovery, catalog and checkout, payment handlers, orders, identity linking. Its first question "is therefore not whether UCP needs a new Donations protocol", but how far a donation can be expressed with those.

What makes a donation different is the number of parties. The charter points out that the fundraiser, the payment collector, the beneficiary and the receipt issuer "may be different parties". A donation can also carry things a purchase doesn't: a designation (a restricted fund or purpose), a platform tip or donor-covered fee, privacy choices, a dedication, and recurrence. Confirmation, payment, delivery of funds and the receipt can happen at different times, confirmed by different parties.

The report has to give a disposition for sixteen donor cases. They include:

• trusted discovery of a legitimate organisation, campaign or fund, with who made each claim and how current it is;
• peer-to-peer and team fundraising;
• suggested and custom amounts, tips and covered fees;
• dedications and notes that need the donor's approval before they're shown;
• anonymity, while keeping identity where receipts or compliance need it;
• matching gifts, conditional pledges and recurring giving;
• non-cash gifts (stock, cryptoassets, donor-advised fund grants, in-kind), as boundary cases that may stay outside UCP;
• donor-only attestations, such as tax declarations an agent must not make on the donor's behalf;
• compliance review, holds and refusals, which are neither a payment success nor a decline;
• tax receipts by jurisdiction.

The charter is just as clear about what UCP shouldn't do. It should not claim to verify "nonprofit status, fundraiser legitimacy, tax treatment, or beneficiary impact". Ranking causes, running a registry and defining a new payment rail are all out of scope.

#The four options on the table

The report must compare at least four technical shapes, without picking one in advance:

Which council would own the result is a separate question. The charter lists Shopping, Payments, shared ownership, a dedicated Giving or Donations council, or no standing body at all. It also asks for a regulatory annex comparing representative obligations in Canada, France, the European Union, the United Kingdom and the United States, kept apart from what the protocol itself has to carry and not presented as legal advice.

#How it got here

The reshaping is the story. The first draft proposed a working group to build donations support. The Governing Council sent it back to answer a prior question: does UCP need anything new for donations, and if so, where should it live?

#What happens next

Nominations, then the member list. Under the governance process, chairs invite participants on the charter issue, and the Governing Council approves the final composition. Amit Handa wrote on 5 November that the Governing Council will give final approval "using the gov:approved tag" once the members are submitted. The issue doesn't carry that label yet.

A handover call. The Shopping Tech Council's action list has a handover meeting with the proposed chair, due 13 November.

Then the report. The charter says the report is due "within four weeks after Governing Council approval of the revised charter". It doesn't say whether that clock runs from the 30 October motion or from the final approval of the members, so we aren't giving a date.

The scope may still grow. A comment on 9 November asked for two more cases, or an explicit exclusion: carts with both a donation and a purchase, and the fair market value of gifts in kind or of benefits such as an event ticket. A GoFundMe contributor agreed both belong in the problem statement.

Outside UCP, GoFundMe.org publishes the Donor Agent Protocol, version 0.1, which the charter cites. It describes donations through three verifiable credentials: an intent mandate, a payment mandate and a receipt. Its page doesn't mention UCP. The charter gives the working group's reason for existing in those terms: a venue to see how these needs fit UCP "before separate approaches become difficult to reconcile".

#What it means

For nonprofits and fundraising platforms: nothing changes in UCP today. The report is where the sixteen cases get a disposition, so this is the stage to make sure your flow is in them. Nominations are open on the charter issue.

For agent builders: there is no donation capability to build against. A store's checkout isn't a donation flow, and the charter is clear that receipt delivery isn't proof that funds reached a beneficiary.

For payment providers: the charter rules out a donation-specific payment rail. The questions for payments are about composition: split payments to several parties, refunds and reversals, and compliance holds that aren't a decline.

#What we'll watch

• The working group's member list and the gov:approved label on #924.
• The technical report: which option it recommends, and which council it names as owner.
• Whether the Governing Council then charters a Giving or Donations council, sends work to Shopping and Payments, or decides no new standard is needed.

There's nothing for UCP Checker to validate until a capability exists. If one is proposed, we'll follow it the way we follow every draft: in the spec repo first, then on our vertical pages and in our test stores.

#FAQ

Does UCP support donations? Not yet. A working group for agentic donations had its charter passed by the Governing Council on 30 October 2026. It will write a technical report on how donations map to UCP, not a spec.

Was the Agentic Donations working group approved? The Governing Council passed the charter on 30 October 2026 and, on 5 November, told the chairs to invite nominations. It gives final approval, with the gov:approved label, once the member list is submitted and reviewed.

Who is running it? The charter names Prasad Wangikar of Stripe as proposed chair, the Shopping Tech Council as sponsor and the Payments Tech Council as consulted.

What is the difference between a working group and a tech council? A working group is time-bounded and hands its results to existing councils. A tech council is a standing body that owns a domain's spec, as Lodging, Food, Local Services and B2B Procurement do or will.

When is the report due? The charter says within four weeks of the Governing Council approving the revised charter. It doesn't say whether that runs from the 30 October motion or from final approval of the members.

Will UCP verify charities? No. The charter says UCP should not claim to verify nonprofit status, fundraiser legitimacy, tax treatment or impact. It asks how claims about those can be carried, with who made them and how current they are.

How do I take part? Comment on the charter, issue #924. Chairs invite participants there, and the Governing Council approves the final list.

#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

• Issue #924: Domain Working Group (DWG) Charter: Mapping Agentic Donations to UCP, UCP GitHub, filed 9 October 2026, revised 23 October 2026; open, label gov:needs-gc-review.
• Governing Council comment requesting a technical report, 18 October 2026; comment on nominations, 5 November 2026.
• Payments Tech Council meeting, 15 October 2026. UCP meeting minutes.
• Governing Council meeting, 16 October 2026. UCP meeting minutes.
• Shopping Tech Council meeting, 16 October 2026. UCP meeting minutes.
• Governing Council meeting, 30 October 2026. UCP meeting minutes.
• Shopping Tech Council meeting, 6 November 2026. UCP meeting minutes.
• Process for nominating new Domain Working Groups. UCP governance.
• Donor Agent Protocol (DAP) v0.1. GoFundMe.org.

Related coverage: UCP B2B Procurement council approved · UCP Local Services council approved · UCP's Bulk Product Discovery working group · The State of Agentic Commerce, October 2026