x402 Foundation: API Lists 50 Members, TSC Lists Three

The x402 Foundation has two public membership records that do not quite align. On 13 August 2026, a Linux Foundation API listed 50 members, while the foundation's own members page rendered 49 logos. The missing name on the page was WalletConnect Foundation, which the API classified as an associate member.

A separate record is smaller. The project's current Technical Steering Committee file names three participating organisations: Coinbase, Cloudflare and Stripe. That committee oversees technical direction and approves proposals, but the project's charter also allows contributors and maintainers outside those three organisations to produce code, documentation and other technical work.

Those distinctions matter. Membership is not the same as technical control, associate membership is free, and a seat on the governing board is not a vote on every specification change.

What Coinbase Contributed

Coinbase created x402 around HTTP status code 402, "Payment Required," as a way for software to request and settle payments over the web. The Linux Foundation announced the intended foundation and contribution on 2 April 2026. The body became operational on 14 July, when the Linux Foundation said formal, open governance was active and named 40 members.

The public repository is now held by the x402 Foundation and carries an Apache-2.0 licence for the code. Its stated scope includes crypto and fiat networks rather than a single blockchain or asset. That makes the governance structure relevant to card networks, processors, cloud providers and crypto companies alike.

Linux Foundation chief executive Jim Zemlin described the objective as keeping "the payment layer of the internet neutral." The membership list shows broad institutional interest. It does not, on its own, establish production adoption.

One Foundation, Two Public Member Counts

The 14 July launch announcement listed 40 members: 17 Premier, 18 General and five Associate. On 13 August, the Linux Foundation's public project API returned 50: 17 Premier, 24 General and nine Associate.

The additions in the API were Arkham, Cyclops, ETHGas, Ledger, Monoma and Satoshi Holdings at General level, plus Hedera Foundation, INFTF MTU, PPPA and WalletConnect Foundation at Associate level. The Premier tier remained at 17.

Yet the x402 members page rendered only 49 logos on the same date: 17 Premier, 24 General and eight Associate. It omitted WalletConnect Foundation. This may be a publishing lag or a difference between the data sources, but neither page explains it. Until the foundation reconciles them, the defensible statement is that its API lists 50 while its website displays 49.

What the Membership Tiers Buy

The 50 organisations in the API are not all paying members. The foundation publishes three tiers. Premier membership costs $200,000 a year and includes an appointed seat on the Governing Board. General membership costs $25,000, $50,000 or $75,000 a year depending on employee count; General members collectively vote for one board representative. Associate membership costs $0 and is limited to qualifying academic and nonprofit organisations.

That means "50 members pay in" is not an accurate description. Based on the published tier definitions and the API roster, 41 organisations sit in fee-bearing tiers and nine sit in the free Associate tier. It also means board influence is uneven: each Premier member is entitled to an appointed seat, while the General tier shares one elected representative.

The published benefits therefore imply 18 member-designated board seats if all 17 Premier entitlements and the single General seat are filled. HaiPay did not find a current public board roster that confirms every seat is occupied, so this should not be reported as the board's verified headcount.

Technical Oversight Is a Separate Structure

The project's Technical Charter assigns technical oversight to a Technical Steering Committee, including coordination of technical direction, approval of proposals and releases, and representation in other standards bodies.

The current TSC file names Coinbase, Cloudflare and Stripe, represented by Erik Reppel, Rohin Lohe and Steve Kaliski. GitHub's history shows that file was added on 12 May 2026 and had not been amended by 13 August.

It would still be inaccurate to say those three companies alone "write the spec." The charter makes contributor status open to anyone who contributes code, documentation or other technical artifacts, and it describes maintainers as contributors who have earned write access. The three listed organisations currently hold the committee seats that oversee and approve the work.

Adding a representative requires a majority vote of the TSC, and a candidate must previously have been a contributor or maintainer. Certain decisions, including changes to the project's core principles or the charter, require a 75% supermajority. If all three current representatives cast a yes-or-no vote, all three affirmative votes would be needed. The charter says abstentions are not counted toward the number necessary, so describing every such decision as requiring absolute unanimity would overstate the rule.

Support Is Not the Same as Membership

The April announcement named 22 organisations expressing initial intent and support. Six did not appear in the 13 August API roster: Ampersend.ai, Base, Microsoft, PPRO, Sierra and thirdweb. The comparison illustrates an important distinction: endorsing a proposed standard is not the same commitment as joining its governing foundation.

The inverse is also true. A membership logo does not prove that a company has deployed x402 in a production payment stack. The public roster records organisational participation, not implementation status.

The Published Activity Figures Average About 32 Cents

The x402 homepage displayed 75.41 million transactions and $24.24 million in volume under a "Last 30 Days" heading on 13 August. Dividing the displayed volume by the transaction count gives an implied average of approximately $0.3214 per transaction.

That arithmetic is reproducible. The time period is not. HaiPay compared the live page with Internet Archive captures dated 6 July, 19 July and 6 August. All four displayed the same transaction count, volume, buyer count and seller count.

The page therefore does not provide evidence that the figures roll forward every 30 days. It does not state when the measurement began, when it last refreshed, how buyers and sellers are defined, or whether test and incentivised activity are excluded. The $0.3214 figure is a calculation from the displayed aggregates, not a measurement of current average transaction size.

What a Debit-Card Ceiling Does — and Does Not — Show

The small implied ticket size helps explain why x402 attracts attention, but it does not by itself prove that card networks cannot support agent payments. The Federal Reserve's Regulation II guidance caps interchange for a covered US debit transaction at 21 cents plus five basis points of the value, with a possible additional one-cent fraud-prevention adjustment. Applied mechanically to $0.3214, that ceiling is about $0.2202, or 68.5% of the payment.

That is a narrow benchmark, not a merchant fee quote. The cap does not apply to every issuer or transaction, interchange is only one part of card acceptance cost, commercial pricing can differ, and an on-chain transfer is not a like-for-like substitute. The comparison shows why a fixed per-transaction component is awkward at very small values; it does not establish the actual cost of any x402 transaction or rule out every card-based design.

What Would Make the Public Record Stronger

Four disclosures would make x402 easier to assess: a reconciled member count across the Linux Foundation API and x402.org; a dated methodology for the activity dashboard; a current list of production implementations; and a maintained record of changes to the TSC and Governing Board.

The evidence available today supports a measured conclusion. x402 has attracted a wide group of payments, technology and crypto organisations. Its code sits under an open licence and its technical charter creates a route for outside contributors. At the same time, the public website and API disagree on the membership total, the current TSC file names only three participating organisations, and the headline activity figures do not demonstrate a rolling 30-day measurement.

Those are not reasons to dismiss the standard. They are the facts readers need in order to distinguish institutional backing, technical governance and measured adoption.