Protocol intelligence / Framework

EMV Agentic Payments – Framework for Specifications

A draft framework for card-based agentic payments and future specification work.

Specification state: draftPrimary evidence available

StewardEMVCo

Stack layerFramework

Version1.0 DRAFT

Last evidence check28 September 2026

Merchant answer / Source-backed reference

A draft framework for card-based agentic payments and future specification work. Frames consumer intent and delegated authority for card-payment scenarios. A draft is not a production protocol, certification or merchant integration. Individual merchant eligibility and deployed configuration require confirmation. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.

What this establishes
The documented role and version scope in the source ledger.

What it cannot establish
Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.

Claim-to-source mapping

description: A draft framework for card-based agentic payments and future specification work. · verified · Checked 2026-09-28 · Sources: emv-draft, emv-news
Scope: Public documentation; not an authenticated merchant test
role: Frames consumer intent and delegated authority for card-payment scenarios. · verified · Checked 2026-09-28 · Sources: emv-draft, emv-news
Scope: Public documentation; not an authenticated merchant test
version: v1.0 DRAFT · verified · Checked 2026-09-28 · Sources: emv-draft, emv-news
Scope: Public documentation; not an authenticated merchant test
version: 1.0 DRAFT · verified · Checked 2026-09-28 · Sources: v11-emv-draft
Scope: Framework draft, not a deployed payment protocol

Evidence dates and document versions remain attached to the ledger below. Editorial presentation reviewed 30 September 2026; this is not a new source verification.

Version-aware protocol intelligence

Current version. Clear scope.

Current version1.0 DRAFT

Current statusdraft framework

Published date2026-09-01

First observed / last verified2026-09-28 / 2026-09-28

Official EMVCo resource/news publication date.

Scope: Framework draft, not a deployed payment protocol · Layer: Framework · Steward: EMVCo

Merchant impact

Framework draft open for feedback; comment period ends 30 September 2026.

Track requirements and provider guidance; do not claim final specification compliance.

Public implementation evidence: Consultation; comments due 2026-09-30

Merchant action today: Track the published consultation and final scope.

Unknowns: Your enabled version, provider rollout, plan and region require merchant-side confirmation.

EMVCo version source ↗

Source capture hashes

v11-emv-draft: SHA-256 c04b411868d0a2d0d2c8cb3ad69405cb53a3ac41b108424f19a4c15fe23318c1

Previous versions

Retrospective source research, first observed by us in September 2026. This is a reviewed subset, not a claim of complete upstream release history.

No earlier version is verified in this record. Unknown is not proof that none exists.

Documented role

What it helps with

Frames consumer intent and delegated authority for card-payment scenarios.

Keep the scope clear

What it does not solve

A draft is not a production protocol, certification or merchant integration.

The merchant work

Track the published consultation and final scope.
Ask payment partners what is implemented today.
Keep draft requirements separate from live obligations.

Individual merchant eligibility and deployed configuration require confirmation.

Version	1.0 DRAFT verified · 2026-09-28
Discovery	Outside scope verified · 2026-09-28
Checkout	Framework context; not a checkout API verified · 2026-09-28
Payment	Card-based agentic payment framework verified · 2026-09-28
Authorization	Consumer intent / delegated authority verified · 2026-09-28
Transport	Not prescribed as a general agent transport verified · 2026-09-28
Adoption	Consultation; comments due 2026-09-30 verified · 2026-09-28

Compare protocols ↗

Append-only history

What we observed, and when.

First house observation: 28 September 2026. Earlier dates, where known, are effective dates researched retrospectively.

2026-09-01

Effective date

Market changed

v1.0 draft framework released for comment

Before / previous scope

Framework work under development

Observed evidence

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.

First captured by us: 2026-09-28. Earlier effective dates are researched retrospectively.

EMVCo source ↗EMVCo source ↗View entity →

2026-09-01

Effective date

Evidence improved

1.0 DRAFT; 1 scoped version record(s) now linked.

Before / previous scope

V1 record: v1.0 DRAFT; no structured prior-version timeline.

Observed evidence

1.0 DRAFT; 1 scoped version record(s) now linked.

Merchant impact: Track requirements and provider guidance; do not claim final specification compliance.

First captured by us: 2026-09-28. Earlier effective dates are researched retrospectively.

EMVCo source ↗View entity →

Open the September baseline →

Evidence ledger

Go to the source.

Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.

EMV Agentic Payments – Framework for Specifications v1.0 DRAFT
EMVCo · official primary · Checked 2026-09-28
Claim scope: Card-based agentic payment framework
Draft, not a deployed payment rail or merchant certification.
Source ID: emv-draft · Published: 2026-09-01
Request for framework feedback
EMVCo · official primary · Checked 2026-09-28
Claim scope: Consultation status
Comment period closes September 30, 2026.
Source ID: emv-news · Published: 2026-09-01
Emv Draft — V1.1 source capture
EMVCo · official primary · Checked 2026-09-28
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: c04b411868d0a2d0d2c8cb3ad69405cb53a3ac41b108424f19a4c15fe23318c1
Source ID: v11-emv-draft · Published: Not stated

Dispute a fact or suggest a source