September 2026 evidence baseline opened
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.
What we first observed on 28 September, with sources, scope and unresolved questions intact.
A product, standard or market condition changed.
Better evidence became available for our record.
A claim became more precise about eligibility, version or context.
Material sources disagree; the conflict stays visible until resolved.
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.
Earlier merchant integration tooling
Google describes UCP hub updates and a gradual US rollout
Merchant impact: Check current Merchant Center eligibility and enabled capabilities before commissioning another connector.
No Agent Connect launch in this house archive
Mastercard announces Agent Connect
Merchant impact: A new connectivity option to investigate. Partners expecting to use it are not verified live merchant integrations.
Framework work under development
v1.0 draft framework released for comment
Merchant impact: Track the consultation and final specification scope; do not treat a draft as a deployed merchant requirement.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: UCP merchant integration hub and AI performance insights
US rollout; later markets are future plans. Scale/performance statements are Google claims.
Claim scope: Merchant/agent connections and payment credentials
Begins in US; named partners exploring or expecting use are not verified live integrations.
Claim scope: Card-based agentic payment framework
Draft, not a deployed payment rail or merchant certification.
Claim scope: Alexa for Shopping, formerly Rufus
Page explicitly records May 13, 2026 rename. Earlier marketing metrics not reused.