Skip to main content
Skip to content
Agentic Finance

Agentic Checkout: Prove the Order Before You Retry

Compare documented checkout controls and reconcile confirmed, duplicate, unresolved and unclassified purchases without invented reliability rankings.

Agentic Checkout: Prove the Order Before You Retry
Reading options: audio, text size & sections
DECENTRALISED NEWS · CHECKOUT STATE AND AUTHORIZATION

A payment acknowledgement does not establish a purchase. Before an agent retries, reconcile the merchant’s order, the payment state and the authority for that specific purchase.

What Matters

An agent checkout needs evidence of what was authorized, what the merchant accepted and what happened to payment. Protocol documentation can describe those controls; it cannot establish comparative failure rates. DN’s reconciliation ledger separates confirmed purchases, closed failures, duplicates, unresolved cases and missing classifications, without turning an incomplete record into a reliability score.

Evidence Block

Reviewed 12 November 2026. This revision compares documented responsibilities and versioned interfaces, not observed vendor performance. Google UCP references below use the 2026-04-08 implementation documentation; the AP2 comparison uses specification v0.2. Product documentation establishes described capabilities, subject to eligibility and implementation. DN has not run a comparative checkout, conversion, adoption or interface-usability study. All numeric examples below are invented scenarios.

The Claim and the Evidence

The attractive claim is that an agent can handle a purchase so smoothly that checkout disappears. The useful question is more precise: can the system prove which purchase the user authorized, establish whether it happened once, and resolve uncertainty without creating another financial obligation?

Consider an agent ordering a laptop. It receives a timeout after submitting payment. The merchant might have created an order; the payment might be authorized but not captured; or neither step might have completed. “No response” does not distinguish these outcomes. Issuing a new purchase request changes the problem: there may now be two orders to reconcile.

The same issue appears in a screen, a headset or a background purchasing workflow. Removing a visible checkout page changes the interaction surface. It does not remove the need for a merchant record, an authorization boundary and a dependable way to retrieve the result.

ClaimEvidence that would support itWhat documentation alone cannot show
The checkout supports retries safelyDefined operation identifiers, idempotency behavior, retention windows and a tested reconciliation pathAn end-to-end duplicate rate across merchants
The agent can buy autonomouslyA specific delegation, enforceable constraints and supported payment credentialsPermission to substitute any item, seller or price
A new interface makes payment easierA supported interaction plus a defined usability studyLower error rates or widespread crypto adoption
The transaction is completeMatched checkout, order and payment records at a stated cutoffSuccessful delivery, refund handling or satisfaction

Five States to Keep Separate

DN uses five review states: intent, the purchase constraints the user approved; checkout, the merchant’s concrete offer; payment, the authorization or transfer status; order, the merchant’s purchase record; and fulfillment, the later delivery, cancellation or refund outcome. This is an editorial organizing method, not a universal protocol state machine.

Record the identifier and authority for each state. A merchant’s checkout total should be reconciled against the payment instruction, while the order should refer to the accepted checkout. A later refund belongs in the same purchase history. A customer-facing success message should identify which state it describes, especially when settlement or fulfillment remains pending.

That distinction also improves incident handling. A completed order with a delayed notification needs a different response from a declined payment, a duplicate order or a charge without a matched order. Assigning every timeout to one “failed” bucket conceals the next action.

What the Documented Systems Cover

The systems below occupy different parts of a purchase. They are compared by responsibility, not ranked by an invented percentage. An integrator must verify the supported version, merchant access, credential rules and actual implementation before deployment.

ACP and Stripe: Checkout State and Scoped Credentials

The Agentic Commerce Protocol checkout reference describes creation, retrieval, updates, completion and cancellation of checkout sessions. It assigns the merchant authority over the checkout’s items, prices and related calculations. Its request interface includes an optional idempotency key; the integrator still needs to establish how a particular merchant implements retries and retrieves state. ACP checkout reference.

Stripe’s shared payment tokens provide a separate credential boundary. Its documentation describes token constraints such as permitted usage, currency, amount and expiry. A constrained credential can limit what may be charged, but it does not by itself prove that an order was created or delivered. Confirm the relevant token profile and supported integration rather than assuming every token has identical rights. Stripe’s current token description.

Explore Agentic Commerce Protocol Stripe Agentic Commerce

UCP and AP2: Commerce State and Purchase Authority

Google’s UCP documentation describes commerce integration and preserves the merchant’s role in the transaction. Access and feature availability need separate checks. The versioned native-checkout reference describes session operations and responses; its order-lifecycle guidance specifies signed webhook handling and freshness checks. A valid event signature establishes origin and integrity within that scheme, not that a delayed event represents the newest order state. UCP order lifecycle, version 2026-04-08.

AP2 v0.2 describes a Checkout Mandate and a linked Payment Mandate, with corresponding receipts. It distinguishes direct approval from autonomous execution under previously approved constraints. Its Trusted Surface must be non-agentic, and verification is assigned to deterministic processing. These are protocol requirements, not proof that an arbitrary application implements them. Commerce APIs and the full dispute-resolution process remain separate concerns. AP2 v0.2 specification.

Google UCP Documentation AP2 Specification

Visa and Mastercard: Network and Credential Integration

Visa’s Intelligent Commerce documentation describes agent validation, purchase instructions and tokenized credentials. Those responsibilities help establish who is requesting a payment and what authority is attached. Production access, issuer participation and the merchant’s order integration are separate questions. A published capability should not be read as universal availability or a measured checkout-success rate. Visa’s implementation documentation.

Visa Intelligent Commerce

Mastercard’s June 2026 Agent Pay for Machines announcement describes credentialing, permissioning and settlement infrastructure for machine transactions. It is evidence of the provider’s stated architecture and offering, not an independent result for duplication, authorization or delivery. The buyer’s useful test is whether the intended integration exposes the records and constraints needed for the purchase. Mastercard’s announcement.

Mastercard Agent Pay

MPP and x402: Paid Resources Still Need Reconciliation

Stripe describes the Machine Payments Protocol as supporting machine payments across payment methods, with a request, payment requirement, authorization and resource response. Its payment tooling can support reporting and refunds. Session-oriented MPP documentation also describes spending authority over repeated interactions. These features should be assessed against the service’s charging and delivery model, rather than treated as a substitute for physical-order management. MPP session documentation.

Explore Machine Payments Protocol

Coinbase’s current x402 FAQ makes the retry boundary explicit: a pending settlement is not a failed payment. Reconcile the returned transaction before requesting another authorization. The FAQ also distinguishes payment replay protection from request-level idempotency; the latter’s payment-identifier extension is not enabled by default in the described CDP SDK. Subscriptions, invoices and holds remain billing-system responsibilities rather than automatic protocol features. x402 implementation FAQ.

Explore x402

Before Retrying, Find the Existing Purchase

A practical incident runbook starts with the intended purchase identifier, then follows the original checkout and payment references. Check the authoritative status before issuing another state-changing instruction. If the result remains unknown, preserve the reservation or escalation state that the implementation requires. A new request should not silently create a new purchase identity.

Keep two records separate: the event log, which may contain many attempts, and the purchase ledger, which represents what the user meant to buy. One purchase can produce several API calls and webhook events. Counting those calls as separate purchases inflates both the denominator and the apparent workload.

A useful retry test deliberately interrupts the response after the server accepts an operation, then checks whether the client can recover the same purchase. It should also cover repeated callbacks, stale events, expired credentials and a user cancellation during uncertainty. These are proposed integration tests; DN has not performed them across the named providers.

DN Checkout Reconciliation Ledger

This local instrument checks a simple partition of one cohort. At the chosen cutoff, classify each intended purchase once. Put a confirmed duplicate in the duplicate category first, even if its remediation is pending. Otherwise classify it as confirmed exactly once, closed without purchase or outstanding payment, or unresolved. The residual count is unclassified, meaning the record is incomplete.

DN Checkout Reconciliation Ledger

The prefilled counts are invented examples. Enter aggregate counts for one defined cohort and cutoff. Count each intended purchase once; retries are part of that purchase. No account connection, credentials or transaction identifiers are needed.

Classify confirmed duplicates first. Otherwise use confirmed once, closed without purchase, or unresolved. Any remainder becomes unclassified. A duplicate still awaiting remediation belongs only in the duplicate category.

No cohort reconciled.

Version 1.0.0. Creation time is not verification. Editing any input invalidates the previous export. A blank cutoff leaves the observation boundary undocumented; keep it with the record before comparing cohorts.

A Worked Cohort, Without an Invented Loss Rate

Suppose a team reviews 1,000 intended purchases. It has matched 920 exactly once, closed 45 without a purchase or outstanding payment, identified 8 purchases affected by duplication and left 12 unresolved. Those categories account for 985 purchases. The remaining 15 are unclassified.

The queue for review is 8 + 12 + 15 = 35 purchases. Classification completeness is 98.5%; the confirmed-once share is 92%. These percentages answer different questions. The first measures how much of this entered cohort has a category; the second measures its known once-completed share at the cutoff. Neither establishes provider reliability or eventual fulfillment.

At an assumed 12 minutes per queued purchase, the model produces 7 review hours. It does not multiply every unresolved case by a purchase value and call the result a loss. Some cases may reconcile successfully; a duplicate may be reversible; an unresolved payment may never settle. Measuring money at risk requires transaction-level amounts, settlement status and recovery assumptions.

Methodology and Machine-Readable Output

The arithmetic is explicit: classified purchases equal the four entered outcome counts; unclassified purchases equal attempts minus classified; the review queue equals duplicates plus unresolved plus unclassified. Review hours equal the queue multiplied by assumed minutes, divided by 60. Counts must be nonnegative integers and cannot sum above the cohort. Empty cohorts have undefined percentages, exported as null.

The JSON record preserves inputs, definitions, limitations, a version and creation timestamp. An optional cohort cutoff provides observation context; creation time is not an audit timestamp. The accompanying JSON Schema specifies field types and structural constraints. The calculation code enforces arithmetic consistency; a schema alone does not prove that real transactions were classified correctly. Any input edit invalidates the previous export.

Invisible and Spatial Checkout: Change the Surface, Keep the Evidence

A headset payment is already a concrete interaction, but its documented scope matters. Apple’s Vision Pro guidance describes reviewing Apple Pay details and confirming with a double-click of the top button followed by Optic ID or the applicable passcode flow. That supports a claim about Apple Pay on a named device. It does not establish autonomous crypto settlement, universal headset support or a measured adoption curve. Apple’s Vision Pro payment guide.

For an ambient shopping scenario, preserve an accessible way to inspect the seller, item, quantity, total, delivery terms and permission being granted. If the user approved a standing mandate, show its limits and how to stop future use. If the user is confirming a particular purchase, bind that confirmation to the actual offer. These are design questions to test, not evidence that a fully invisible checkout is preferable.

SurfaceEvidence to retainBoundary to test
Screen or spatial displayThe offer shown and the purchase approvedWhether the user can inspect changes before committing
Voice commandThe interpreted instruction and the separate authorizationWhether a command is mistakenly treated as authenticated permission
Background agentMandate, constraints, execution and revocation historyWhether substitutions or retries exceed that mandate
Haptic feedbackThe event the feedback denotesWhether confirmation remains accessible without relying on a vibration alone

Apple’s haptic guidance treats tactile feedback as part of an interface, with consistency and complementary feedback important to its design. It does not supply an error-rate benchmark for haptic-only crypto confirmation. WCAG’s guidance for financial or legal submissions allows several approaches to error prevention, including reversibility, checking or confirmation. It is not a prescription that every payment use the same gesture. Apple haptics guidance; WCAG 3.3.4 explanation.

Accordingly, this article does not forecast an irreversible transition away from screens by 2030. A valid comparison would specify users, tasks, accessibility needs and error definitions, then measure alternatives. For the distinction between a spoken command and wallet authority, see Passkey Wallet Security: Recovery Paths and Authority.

What a Real Comparative Benchmark Would Require

A defensible test would fix the purchase task, merchant sample, integration version, payment method, region, retry policy and observation window. It would distinguish ordinary declines from implementation errors and uncertainty. It would follow orders beyond authorization into refunds or fulfillment where those outcomes are part of the claim. Report excluded merchants and missing results, not only successful runs.

For interface claims, a separate study would need participant selection, task difficulty, accessibility coverage, false-confirmation and missed-confirmation definitions, and confidence intervals. A demonstration that a payment can be triggered is not enough to conclude that it is safer or easier. Until those data exist, this guide provides a documented control comparison and an honest cohort ledger.

The Checkout Is Only One Layer

Wallet authority, resource-payment handling and platform access need their own reviews. These existing DN guides provide related context; this article does not rank providers or infer commercial relationships from their inclusion.

Best Wallets for AI Agents 2027 x402 Cost & Reliability Benchmark Best Crypto Platforms for AI Agents

Frequently Asked Questions

Which protocol is the most reliable?

This review cannot establish that ranking. The protocols cover different responsibilities, and public documentation does not provide a controlled, comparable end-to-end outcome study.

Does a payment receipt prove that the merchant created an order?

It establishes only what the receipt’s scheme and status actually represent. Match it to the authoritative checkout and order record before treating the intended purchase as complete.

Why does the ledger count duplicates before unresolved cases?

A duplicate can still need remediation. Giving it priority keeps that purchase in one category and prevents the same case from inflating the review queue twice.

Can a haptic signal or spoken command authorize payment?

An interface signal and a payment authorization are separate components. The implementation must establish the relevant permission and confirmation process; this review supplies no haptic-only or voice-only security verdict.

Does the tool send purchase data anywhere?

The instrument calculates locally from aggregate inputs. It contains no network request or storage call and asks for no transaction identifiers. A downloaded file contains the counts the user supplied, not independently verified transaction evidence.

Primary Sources and Scope

The linked primary documentation supports the specific capabilities described above. Historical launch pages are retained for context; current versioned specifications govern the comparisons. Vendor statements are attributed to their providers. They are not independent measurements.

Corrections and Change Log

12 November 2026: Replaced architecture ratings and comparative “best” labels with a responsibility comparison. Updated the AP2 description to v0.2 and x402 retry boundaries. Replaced the overlapping probability model with a mutually exclusive cohort ledger. Added spatial, voice and haptic evidence limits; removed the unsupported inevitability forecast and duplicate article-level schema. The canonical address and existing supporting links are retained.

Method and commercial boundary: This is a primary-source review and an original reconciliation method. It does not recommend a provider or certify an integration. Corrections should identify the protocol version, source or reproducible behavior that changes a stated claim. It provides information, not individualized payments, security or legal advice.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.