For merchants, payment providers, issuers, and product or security teams, the right response to agentic commerce is not to treat an AI agent as a customer holding an unrestricted wallet. Treat it as a separate actor operating under a customer’s authenticated, limited instruction. Your controls should establish who gave permission, what they approved, which agent acted, and whether the final payment matched that approval.
What “access to a wallet” should mean
Agentic commerce describes AI agents searching, comparing, or making purchases for people. A customer authorizing an agent to buy something is delegating authority; it should not mean handing the agent the customer’s underlying payment credentials or blanket authority to spend.
The control problem has two distinct identity questions: is this an agent your systems can recognize, and did the customer authorize this particular transaction? Recognizing approved agent traffic does not establish customer consent. Conversely, a valid customer instruction does not by itself identify which agent later submitted a payment request.
Visa describes agent-specific tokens and payment instructions authenticated by the user. OpenAI and Stripe describe purchase flows using customer confirmation and permissioned payment tokens. Those are vendor descriptions of mechanisms, not evidence that all agents, merchants, issuers, or processors support them or that any interaction is risk-free. See Visa Intelligent Commerce, OpenAI’s Instant Checkout and Agentic Commerce Protocol description, and Stripe’s agentic commerce overview.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
How a permissioned purchase can work
Authenticate the customer’s instruction
In Visa’s described Intelligent Commerce flow, a user may add a Visa card, complete step-up verification, and set up a passkey for future instruction authentication. When an agent proposes a purchase, the user is asked to approve it and authenticates the payment instruction with the passkey. Visa says the initial purchase flow is facilitated through guest checkout using key entry or form fill; this is a description of that flow, not a guarantee that every merchant integration works the same way. Visa Intelligent Commerce overview
Use a delegated credential rather than exposing the original
Stripe says Shared Payment Tokens let agents initiate payments with a buyer’s permission and preferred payment method without exposing the payment credentials themselves. OpenAI describes Instant Checkout as passing purchase information between the user and merchant: the merchant accepts or declines the order, processes payment through its provider, and handles fulfillment and support. It says users explicitly confirm each step and that encrypted payment tokens are authorized for specific merchants and amounts. Confirm the current feature scope and availability before relying on either vendor’s description for a live integration.
Rank #2
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Match the authorization request to what was approved
Visa says its controls check that credential requests match the authenticated instruction and that the eventual authorization request is for the intended merchant and correct amount. That is the critical boundary between a permissioned purchase and an agent changing the deal after approval. A passkey or agent signature alone is not enough if the payment request can drift from the approved transaction.
Keep the outcome with the instruction
Visa describes commerce signals as supporting dispute resolution by connecting the purchase outcome to the instruction. Operationally, that means retaining a usable record of what the customer authorized and what happened at checkout, subject to your organization’s retention and dispute rules.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRank #3
Controls to put in place before enabling agent checkout
- Define the customer instruction. Record what the customer approved and require an authenticated instruction before the agent retrieves or uses a payment credential. A broad consent such as “shop for me” is not a useful transaction boundary unless your product defines its limits.
- Set enforceable transaction scope. At minimum, decide how merchant and amount are bound to the approval; Visa’s description specifically discusses those checks. If your product offers further constraints—such as a spending cap, category, time window, or purchase count—verify that the integration actually enforces them rather than assuming those limits are part of a token.
- Protect the underlying credential. Prefer delegated or tokenized payment credentials that do not expose the customer’s raw payment details to an agent. Stripe describes Shared Payment Tokens as designed to avoid credential exposure.
- Recognize the agent and the customer separately. Use verifiable agent identity and intent signals where supported, while preserving a means to recognize the consumer behind the request. Visa’s Trusted Agent Protocol specifications describe agent-specific cryptographic signatures and fields for agent intent, consumer recognition, and optional payment information. Its initial specifications apply to Visa’s network in this phase; Visa also notes alignment work with standards bodies including IETF, OpenID Foundation, and EMVCo. This is not a universal cross-network standard. Visa Trusted Agent Protocol announcement
- Recheck at authorization time. Compare the payment request against the authenticated instruction at the point of payment. A change in merchant or amount should not silently inherit approval for the original transaction.
- Design the exception path. Decide what happens if the agent changes the item, quantity, shipping details, merchant, or total after approval. Require renewed confirmation, reject the transaction, or route it for review according to a policy you can test. The reviewed vendor descriptions do not specify every exception policy.
- Preserve evidence and operational ownership. Keep the original instruction, authentication and identity evidence, merchant and amount, and purchase outcome available to the teams responsible for disputes, refunds, fraud review, and customer support. Define how permissions are revoked and how incidents are handled.
- Test the whole merchant journey. Check agent-originated traffic against bot defenses, checkout, fraud review, fulfillment, customer service, refunds, and guest or authenticated checkout. Visa identifies bot detection, agent-driven checkout, and consumer visibility as merchant challenges.
How the approaches differ
These systems address different parts of the trust problem, so a product comparison should cover authority, identity, enforcement, payment handling, and actual deployment—not just whether an agent can complete checkout.
| Approach | What the cited description covers | Questions to verify before deployment |
|---|---|---|
| Visa Intelligent Commerce | Agent-specific tokens, user-authenticated instructions using passkeys, credential checks, network transaction controls, and purchase outcome signals. Visa overview | Issuer and network participation; token lifecycle; the instruction constraints supported; enforcement for merchant and amount; and how evidence reaches dispute handling. |
| Visa Trusted Agent Protocol | Cryptographic agent signatures and information for agent intent, consumer recognition, and optional payment data. Visa says the initial specifications apply to its network in this phase. Visa announcement | How merchants verify agents, integration effort, how the customer is recognized, and what interoperability exists beyond the stated network scope. |
| OpenAI/Stripe Agentic Commerce Protocol and Shared Payment Tokens | OpenAI describes an open protocol for coordinating agent and merchant purchases; Stripe describes permissioned shared tokens that avoid exposing credentials. OpenAI says the merchant controls payment processing and fulfillment. OpenAI; Stripe | Processor support, checkout handoff, customer confirmation, merchant-of-record responsibilities, and integration requirements. |
| Stripe Link agentic controls | Stripe says Link is intended to provide visible customer controls, including spending limits or explicit agent permissions. Stripe overview | Whether the controls are available for the target customer and geography, how permissions are revoked, and how users see the scope of access. |
| Machine-native payment approaches such as x402 and MPP | Visa’s report discusses x402 and MPP as machine-native payment approaches, with very small average payments affecting fee economics. These are not the same use case as ordinary consumer retail checkout. Visa report, updated July 14, 2026 | Payment size, settlement rail, fees, reversal and dispute model, and whether the use case is machine-to-machine micropayment rather than a consumer purchase. |
Where machine payments fit—and where they do not
Onchain protocol activity can help explain why machine-native payment systems are being discussed, but it should not be confused with retail card purchases. Visa’s report, summarizing Visa/Artemis figures and updated July 14, 2026, gives x402 adjusted volume of roughly $15.0 million across 109.6 million transactions since its May 2025 launch. The same report gives MPP activity of about $25,000 across roughly 115,000 transactions in its first few weeks after a mid-March 2026 launch. These are reported onchain protocol figures, not measures of card spending or broad consumer adoption. Visa’s onchain payments report
Rank #4
- Ultra-Compact FIDO2 Security Key - Plug-and-stay or carry on a keychain. This USB-A hardware security key offers portable, always-on protection for desktop and mobile use. (Item Size: 0.75 X 0.74 IN x 0.25 IN)
- USB-A Hardware Key for All Devices - Works with USB-A ports on PC, Mac, Android, and other laptop/notebook device. Enables secure, cross-platform login with FIDO2.0 passkey support.
- FIDO Certified Security Key - Meets FIDO and FIDO2 standards. Works with Google, Microsoft, GitHub, Dropbox, and more. Please check service compatibility before purchase.
- Passwordless Login with Passkey - Supports passkey login via WebAuthn and CTAP2. Enjoy password-free sign-ins where supported. Not all websites or services currently support passkeys.
- Advanced Multi-Factor Authentication - Offers 200 FIDO2 passkey slots and 50 OATH-TOTP slots. Strong, flexible 2FA/MFA support across various apps and authentication platforms.
For a consumer retail transaction, the central questions remain whether the customer approved that purchase and whether the merchant, amount, and outcome can be tied back to the instruction. A machine-native payment rail does not answer those questions by itself.
What adoption signals do—and do not—show
Visa’s Trusted Agent Protocol announcement cites Adobe Data Insights figures from August 2025: AI-driven traffic to U.S. retail websites increased by over 4,700% year over year, and 85% of shoppers who had used AI to shop said it improved their shopping experience. The first figure is a reported change in U.S. retail-site traffic, not purchases or activity in all markets; the second describes surveyed shoppers who had used AI, not all shoppers. Neither establishes that an agent has safe or authorized payment access. Visa announcement citing Adobe Data Insights
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Deployment is a governance decision, not just an integration
Before enabling live transactions, verify availability for your markets, supported issuers and processors, merchant eligibility, logging, revocation, and incident response. Vendor feature descriptions are not proof that a capability is live for every integration or interoperable across networks. A passkey setup may support authentication; Visa’s described flow does not say that a hardware security key is required. If you recommend one as an optional way to use a passkey, confirm that the customer’s identity provider supports the device.
The operational standard is straightforward: let an agent act only within authority the customer deliberately granted, recognize both agent and customer, compare the final payment with the approved instruction, and retain evidence of the result. These controls can reduce risk and make disputes more tractable, but they do not eliminate fraud, errors, or payment disputes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
