Market changes connected to merchant decisions, protocols and tools.
Market changes use their effective date. Evidence improvements and clarifications use the date we recorded them; older releases are never passed off as this week’s launch.
V1 record: 2026-04-17 (stable in repository); no structured prior-version timeline.
2026-04-17 · repository identifies specification as beta; 5 scoped version record(s) now linked.
Merchant impact: Check the dated schemas and exact provider onboarding; published scope is not merchant enrollment.
Affected Scanner checks: ACP integration
Affected stack layer: Commerce
V1 record: 2026-08-25; no structured prior-version timeline.
2026-08-25; 4 scoped version record(s) now linked.
Merchant impact: Pin profile and capability versions; verify provider support before migration.
Affected Scanner checks: UCP discovery profile
Affected stack layer: Commerce
V1 record: v0.2; no structured prior-version timeline.
0.2.0; 2 scoped version record(s) now linked.
Merchant impact: Review authority and mandate handling with your payment provider; this is not a live payment test.
Affected Scanner checks: Payment information
Affected stack layer: Identity & trust
V1 record: Unknown; no structured prior-version timeline.
draft-httpauth-payment-01 · normative core; broader SDK/method versions separate; 1 scoped version record(s) now linked.
Merchant impact: Pin the core draft and payment-method documents separately. Do not substitute an SDK version for a protocol release.
Affected Scanner checks: Payment information
Affected stack layer: Payments
V1 record: Unknown; no structured prior-version timeline.
2; 2 scoped version record(s) now linked.
Merchant impact: Select a compatible transport, scheme and facilitator; do not treat payment-resource access as full retail checkout.
Affected Scanner checks: Payment information
Affected stack layer: Payments
V1 record: 2026-07-28; no structured prior-version timeline.
2026-07-28; 3 scoped version record(s) now linked.
Merchant impact: Check client/server version negotiation; tool transport is not a commerce integration.
Affected Scanner checks: None directly; reference / implementation guidance only.
Affected stack layer: Transport
V1 record: 1.0.0; no structured prior-version timeline.
1.0.1 repository release / 1.0.0 specification banner — scope unresolved; 3 scoped version record(s) now linked.
Merchant impact: Confirm the exact protocol schema and SDK alignment; agent coordination does not prove merchant adoption.
Affected Scanner checks: None directly; reference / implementation guidance only.
Affected stack layer: Agent coordination
V1 record: v1.0 DRAFT; no structured prior-version timeline.
1.0 DRAFT; 1 scoped version record(s) now linked.
Merchant impact: Track requirements and provider guidance; do not claim final specification compliance.
Affected Scanner checks: Payment information
Affected stack layer: Framework
No house observation
September 2026 evidence baseline opened
Merchant impact: Read every fact with its source, scope and checked date. This is the start of our observation history.
Affected Scanner checks: ACP integration
Affected stack layer: Commerce
Brief seed used the name Rufus
Amazon states Rufus was renamed Alexa for Shopping
Merchant impact: Keep the historical route and earlier naming searchable while using the current official name.
Affected Scanner checks: None directly; reference / implementation guidance only.
Affected stack layer: Commerce
Price and capability claims in supplied research seed
Current verification unresolved; prices withheld
Merchant impact: Do not use seed pricing or unverified capabilities to make a purchase decision.
Affected Scanner checks: None directly; reference / implementation guidance only.
Affected stack layer: Readiness / testing
Save the topics you want to check when you return. This does not subscribe you to email or schedule store scans.