Decentralised News · Agentic Finance · Decision research
By Heath Muchena · Source review 2026-11-14 · Instrument version 1.0.0
What Matters
A date becomes decision-useful when its event type and scope travel with it. These thirteen primary publications trace selected payment, commerce and identity developments from April 2025 to November 2026. They establish what was announced or released, with stated limits. They do not measure market adoption or prove that a capability is available everywhere today.
Agentic finance timelines often compress several different events into the word “launch.” A network can announce a programme, a developer group can publish a protocol and a consumer product can start a restricted rollout. Treating those dates as equivalent makes the ecosystem look more complete than the source evidence establishes.
DN rebuilt this selection from the originating organizations’ publications. Every entry has a stable event ID, a source date and a stated interpretation. The most recent entry is OpenAI’s 13 November 2026 ChatGPT Wallet announcement. Its initial US eligibility and per-purchase approval requirement remain part of the record.
| Record class | What the date establishes | Additional evidence needed |
|---|---|---|
| Programme or product announcement | A named organization publicly described an initiative. | Eligibility, implementation and observed operation. |
| Specification release | A documented protocol or version was introduced. | Which parties implemented which version. |
| Limited rollout | A bounded availability statement was made. | Current access for the user, country and payment method. |
| Pilot or collaboration | A trial or joint effort was announced. | Results, production coverage and any adopted standard. |
DN Evidence Block
Sources reviewed: 2026-11-14 · Evidence type: Thirteen originating-organization publications, opened and checked on 13 November UTC / 14 November Africa/Johannesburg.
Scope: A selected historical event register covering 29 April 2025–13 November 2026. All dates below are primary-publication dates; exact deployment or collaboration-start times are not inferred.
- Every numbered entry points to the organization’s own dated announcement or report.
- Released specifications, announced programmes, pilots, collaborations and limited rollouts retain separate classifications.
- The original idea list was a research prompt. Unsupported dates and incident claims were omitted rather than treated as evidence.
- The scope checker uses this reviewed register and labelled synthetic claim-selection examples.
Not established by this work: No transaction volumes, market shares, universal availability, integration reliability, identity accuracy or current account eligibility were independently measured.
Original DN instrument · version 1.0.0
DN Milestone Scope Register
Select a documented milestone, the claim you want to make and the relevant reference date. Preserve its source date, event stage and scope in a downloadable record. A historical announcement cannot establish current availability or measured adoption.
Enter your assumptions or load a labelled example. Required blank numbers stay missing; unknown evidence remains unknown. Use nonpersonal labels only. This instrument makes no network requests and uses no persistent browser storage.
Use your own inputs
No current result. Complete inputs or load an illustrative example.
A selected, reviewed set of thirteen primary publications. It is not an exhaustive history, an adoption dataset, a current eligibility test, a universal standards register or a classifier of free-form claims. Source-date comparisons use calendar days. Source scope is preserved, not independently tested.
1. 2025-04-29 — Mastercard announces Agent Pay
Record type: Programme announcement.
Mastercard announced its Agent Pay programme and agentic tokens. Its release also described planned work with Microsoft and other providers. The dated evidence is a programme announcement with a roadmap, rather than a count of completed agent purchases. [1]
Decision boundary: For a procurement brief, preserve the distinction between the network’s announced capabilities and the particular implementation a supplier can demonstrate.
Stable record: DN-EVT-20250429-MC. Date basis: primary publication date.
2. 2025-04-30 — Visa introduces Intelligent Commerce
Record type: Programme announcement.
Visa introduced Intelligent Commerce at its Global Product Drop, describing APIs, a partner programme and tokenized credentials for AI commerce. The announcement established Visa’s initiative and stated direction. It did not independently establish that every merchant, card or agent could transact through it that day. [2]
Decision boundary: Use this date to locate the programme’s public introduction. Verify product, market and partner eligibility separately for a current deployment.
Stable record: DN-EVT-20250430-VISA. Date basis: primary publication date.
3. 2025-05-06 — Coinbase launches x402
Record type: Protocol release announcement.
Coinbase introduced x402 as an open payment protocol built around HTTP payment interactions. The launch described stablecoin payments for APIs, applications and agents. This is a dated protocol introduction; the announcement’s future-facing commercial language is not a measurement of transaction demand. [3]
Decision boundary: A timeline can establish when the protocol became publicly introduced. Assess a particular version, network, facilitator and paid service before calling an integration available.
Stable record: DN-EVT-20250506-X402. Date basis: primary publication date.
4. 2025-09-16 — Google announces Agent Payments Protocol
Record type: Protocol release announcement.
Google announced AP2 as an open framework for agent-led payments and pointed developers to a public specification and reference implementations. The release described mandates that preserve a user’s instructions and purchase approval. Its list of collaborating organizations should not be converted into a list of proven production deployments. [4]
Decision boundary: Keep the specification event separate from any later evidence that a particular merchant, issuer or agent supports the required flow.
Stable record: DN-EVT-20250916-AP2. Date basis: primary publication date.
5. 2025-09-29 — OpenAI introduces Instant Checkout and ACP
Record type: Protocol release and limited product introduction.
OpenAI announced Instant Checkout and the Agentic Commerce Protocol, developed with Stripe. The initial product scope was single-item purchases by US ChatGPT Plus, Pro and Free users from US Etsy sellers. Further merchants and regions were described as coming later. [5]
Decision boundary: The same announcement contains a protocol release and a bounded product introduction. Its historical eligibility should not be carried forward as a claim about today’s experience.
Stable record: DN-EVT-20250929-ACP. Date basis: primary publication date.
6. 2025-10-14 — Visa releases Trusted Agent Protocol
Record type: Protocol release announcement.
Visa announced Trusted Agent Protocol and said the material was available through its developer centre and GitHub. The release described agent recognition, consumer recognition and payment information, while identifying the initial phase with the Visa network. [6]
Decision boundary: A released recognition protocol does not by itself establish a merchant’s adoption, a user’s authorization for a specific purchase or successful payment execution.
Stable record: DN-EVT-20251014-TAP. Date basis: primary publication date.
7. 2026-01-11 — Google launches Universal Commerce Protocol
Record type: Protocol release announcement.
Google launched UCP for interactions across the shopping journey. The announcement distinguished that protocol release from a new checkout feature that would soon reach eligible US retailer listings in AI Mode and Gemini. Those verbs describe different stages. [7]
Decision boundary: Do not use the standard’s launch date as the deployment date of every associated consumer feature. Keep the product announcement’s region and eligibility conditions.
Stable record: DN-EVT-20260111-UCP. Date basis: primary publication date.
8. 2026-01-29 — Sumsub announces AI Agent Verification
Record type: Vendor product announcement.
Sumsub announced AI Agent Verification, describing a connection between automated activity and verified human identity within its Know Your Agent framework. This supplies a primary date and the vendor’s stated approach. It does not establish a universal KYA standard or independently validate the product’s prevention claims. [8]
Decision boundary: Retain the named framework and supplier when describing identity capabilities. A familiar acronym can conceal different verification and authority models.
Stable record: DN-EVT-20260129-SUMSUB. Date basis: primary publication date.
9. 2026-03-18 — Stripe and Tempo introduce Machine Payments Protocol
Record type: Protocol release announcement.
Stripe introduced MPP, co-authored with Tempo, as a specification for agents and services to coordinate payments. Its announcement also described accepting payments through Stripe’s PaymentIntents API. This is evidence of the release and described integration, rather than evidence of broad service adoption. [9]
Decision boundary: Compare the protocol layer, supported payment method and actual service integration separately. A common “agent payments” label does not make MPP and every earlier protocol interchangeable.
Stable record: DN-EVT-20260318-MPP. Date basis: primary publication date.
10. 2026-04-28 — Google announces AP2 stewardship transition and version 0.2
Record type: Governance announcement and specification update.
Google’s own announcement is dated 28 April. It described donating AP2 to the FIDO Alliance and releasing version 0.2 with changes for human-not-present payments. A syndicated recap on the following day should not replace the date on this primary announcement. [10]
Decision boundary: Governance, specification version and product rollout are distinct dimensions. A newly documented autonomous flow does not establish universal merchant or issuer acceptance.
Stable record: DN-EVT-20260428-AP2FIDO. Date basis: primary publication date.
11. 2026-09-11 — Ant publishes an AMP and KYA collaboration update
Record type: Progress report and collaboration announcement.
Ant International’s page is dated 11 September and reports that Ant, Mastercard and Visa had begun work on a KYA interoperability framework. It states that shared principles would preserve each network’s verification and decisioning processes. The publication date is not presented here as the exact day collaboration began. [11]
Decision boundary: Record the collaboration as announced work. It is insufficient evidence that one completed global onboarding standard had replaced the separate network processes.
Stable record: DN-EVT-20260911-ANT. Date basis: primary publication date.
12. 2026-11-05 — Zetrix and CAICT announce a KYA service and cross-border pilot
Record type: Service and pilot announcement.
Zetrix AI and CAICT announced a KYA service and a cross-border pilot. The release says pilot results would be submitted for consideration in standards discussions. A planned submission is distinct from an adopted international standard. [12]
Decision boundary: Treat this milestone as an announced service and pilot scope. Production coverage, pilot outcomes and any later standards decision require their own records.
Stable record: DN-EVT-20261105-ZETRIX. Date basis: primary publication date.
13. 2026-11-13 — OpenAI begins the ChatGPT Wallet rollout
Record type: Limited product rollout announcement.
OpenAI announced that ChatGPT Wallet would begin rolling out through dots, initially for US ChatGPT Pro subscribers aged 18 and over with eligible US-issued cards. Users review and approve each purchase with a security check. Broader delegated purchasing was described as a future direction. [13]
Decision boundary: This is a fresh, explicitly limited rollout. Preserve its user, region and approval conditions; it does not support a claim that unattended purchasing is generally available.
Stable record: DN-EVT-20261113-WALLET. Date basis: primary publication date.
Methodology, limitations and corrections
DN selected primary publications that directly establish a dated agent-payment, commerce or identity development. Each record preserves the source URL, publication date, stage, scope and stable ID. A later summary can help locate a source, but does not override the original publication’s date. Where the report says work had already begun, the date is retained as the report date rather than invented as the project’s beginning.
This edition omits proposed entries for which the required primary evidence was not established, including the supplied claims about an exact Instant Checkout discontinuation date, an incident date and several claimed standards or network milestones. Omission is not a finding that an event did not occur. This is a selected register, not a complete chronology.
The local instrument compares a reader’s selected claim type against the record’s documented classes and declared scope. “Supported” means that selected class is present in the retained source scope; it does not verify the reader’s full prose or a present deployment. The exported JSON includes the underlying event record. Dates, labels and source changes should create a documented new register version rather than silently changing historical entries.
For corrections, identify the claim, source and date when contacting Decentralised News. A new record-creation timestamp does not refresh its underlying evidence.
Change log: version 1.0.0, 2026-11-14. Initial documentation review, original instrument and labelled examples.
Frequently asked questions
Does a protocol release mean a shopping agent can pay everywhere?
No. A specification describes a way for implementations to interact. Real availability also depends on participating systems, versions, products, regions and eligibility. The timeline retains those distinctions.
Why use source-publication dates rather than call every entry a launch?
The primary document reliably dates the announcement or report. It may describe a same-day release, a limited rollout, work already under way or a future capability. The wording of each entry preserves that stage.
Does the latest ChatGPT Wallet entry mean purchases are fully delegated?
The 13 November announcement describes per-purchase user review and a security check. It presents broader delegated purchasing as a future direction. The historical record therefore keeps those approval and eligibility limits.
Can this register prove which company was first?
No. A selected source set cannot establish exhaustive historical priority. It records these documented publications and the claims they support.
Primary sources
- Mastercard announces Agent Pay — primary announcement. 2025-04-29 primary publication and the specific event stage described in section 1. Reviewed 2026-11-13.
- Visa introduces Intelligent Commerce — primary announcement. 2025-04-30 primary publication and the specific event stage described in section 2. Reviewed 2026-11-13.
- Coinbase launches x402 — primary announcement. 2025-05-06 primary publication and the specific event stage described in section 3. Reviewed 2026-11-13.
- Google announces Agent Payments Protocol — primary announcement. 2025-09-16 primary publication and the specific event stage described in section 4. Reviewed 2026-11-13.
- OpenAI introduces Instant Checkout and ACP — primary announcement. 2025-09-29 primary publication and the specific event stage described in section 5. Reviewed 2026-11-13.
- Visa releases Trusted Agent Protocol — primary announcement. 2025-10-14 primary publication and the specific event stage described in section 6. Reviewed 2026-11-13.
- Google launches Universal Commerce Protocol — primary announcement. 2026-01-11 primary publication and the specific event stage described in section 7. Reviewed 2026-11-13.
- Sumsub announces AI Agent Verification — primary announcement. 2026-01-29 primary publication and the specific event stage described in section 8. Reviewed 2026-11-13.
- Stripe and Tempo introduce Machine Payments Protocol — primary announcement. 2026-03-18 primary publication and the specific event stage described in section 9. Reviewed 2026-11-13.
- Google announces AP2 stewardship transition and version 0.2 — primary announcement. 2026-04-28 primary publication and the specific event stage described in section 10. Reviewed 2026-11-13.
- Ant publishes an AMP and KYA collaboration update — primary announcement. 2026-09-11 primary publication and the specific event stage described in section 11. Reviewed 2026-11-13.
- Zetrix and CAICT announce a KYA service and cross-border pilot — primary announcement. 2026-11-05 primary publication and the specific event stage described in section 12. Reviewed 2026-11-13.
- OpenAI begins the ChatGPT Wallet rollout — primary announcement. 2026-11-13 primary publication and the specific event stage described in section 13. Reviewed 2026-11-13.
Turn the finding into a decision
Before funding an integration, identify the exact capability you need and use the register to locate its primary announcement. Then request current documentation and a bounded demonstration for the relevant product, country, payment method and user type. DN’s payment-protocol comparison can help structure that implementation question.
Related DN research
Disclosure: Analysis and instrument results are editorial. Where labelled affiliate links appear, DN may receive compensation when you sign up or buy through them. Commercial relationships do not determine findings. No tested integration or guaranteed outcome is implied.
