Visa Intelligent Commerce
Card networks
Visa program and capabilities for agent-assisted commerce using tokenized credentials, spending controls, and contextual network signals.
An independent view · Payments + agents
Agents can already choose. Paying requires more: permission, limits, and evidence. This is a place to understand the ecosystem and build with sound judgment.
Open sources. Clear concepts. Documentation separated from test evidence.
01 / Explore
Protocols, networks, wallets, and checkout, alongside tools to evaluate, observe, and coordinate agents. Open any profile to inspect its technical summary and primary source.
These profiles reflect official documentation reviewed on the stated date. They do not constitute certification, own testing, or production access. A payment API alone does not prove support for autonomous payments.
General evaluation, observability, orchestration, and identity tools support system building. Their inclusion does not imply they execute payments or grant authorization to do so.
Card networks
Visa program and capabilities for agent-assisted commerce using tokenized credentials, spending controls, and contextual network signals.
Protocols
Visa specification to identify authorized agents to merchants using cryptographic signatures and verifiable session metadata.
Card networks
Mastercard framework for agent-initiated payments with dynamic tokens, cardholder intent verification, and traceability across merchant and issuer.
Protocols
Open SD-JWT credential specification to chain user mandates, amount or payee constraints, and cryptographically verifiable proofs.
Protocols
Open protocol (Agent Payments Protocol) to structure verifiable intent, cart, and payment mandates across agents, merchants, and providers.
Protocols
Open standard (Agentic Commerce Protocol) to discover catalog items, negotiate checkout sessions, and delegate scoped payment credentials.
Protocols
Universal Commerce Protocol specification for publishing machine-readable merchant capabilities and standardizing cross-platform checkout flows.
Protocols
Protocol built on HTTP 402 (Payment Required) to settle machine-to-machine micropayments per web or API request.
Payment infrastructure
Stripe Shared Payment Tokens allowing an agent to initiate a charge constrained to a specific merchant, amount, and time window.
Payments & commerce
PayPal services and developer capabilities connecting software agents to checkout flows, orders, tracking, and buyer identity.
Commerce platforms
Shopify and Shop Pay capabilities enabling agents to query catalogs, assemble carts, and prepare verified checkout sessions.
Payment infrastructure
Very Good Security tokenization vault and proxy allowing agents to operate with payment credentials without exposing raw PCI data.
Payment infrastructure
Programmable vault and tokenization infrastructure to isolate cards and sensitive credentials when an agent executes payments.
Payment infrastructure
Network and programmable balance/identity infrastructure designed for autonomous payments between software agents and digital services.
Payment infrastructure
Crossmint wallet and checkout infrastructure providing agents with programmable treasury and purchase flows for digital or physical goods.
Web tools
Web tooling to automate browser steps and checkout forms; requires external authorization and payment execution controls.
Protocols
Machine Payments Protocol specification to negotiate charges, receipts, and verifiable settlement between automated clients and servers.
Card networks
American Express initiative focused on agentic commerce experiences, cardmember trust, and controls in AI-assisted payments.
Payments & commerce
Adyen agentic commerce capabilities covering network tokenization, authentication, and payment processing for merchants serving agents.
Payment infrastructure
Checkout.com adoption of ACP and payment infrastructure to process agent-delegated charges for enterprise merchants.
Developer tools
Mercado Pago developer plugin and integration tooling to assist technical implementation; not an autonomous agent payment protocol.
Payment APIs
Traditional payment sources API in Colombia (cards, Nequi, PSE); requires building mandate verification and spending limits separately.
Testing & evals
Adversarial red-teaming and evaluations for model-powered applications. Supporting tool; does not execute payments.
Observability
Observability for model applications: execution traces and analysis. Supporting tool; does not execute payments.
Observability
Semantic conventions for instrumenting generative AI operations. Supports observability; not a payment network.
Durable orchestration
Durable orchestration to coordinate tasks and recover agent workflows. Payment requires a separate integration and its controls.
Durable orchestration
State persistence for agent workflows. Supporting tool; saving state does not prove a payment was executed.
Identity & policy
Policy engine to govern agent tool calls. Supports authorization decisions; does not process payments.
Wallets & SDKs
Agent-oriented wallet infrastructure. Consult the provider documentation for supported capabilities, networks, and terms.
Wallets & SDKs
Toolkit for connecting wallets and on-chain actions to agents. Capabilities depend on the selected tools and integrations.
Wallets & SDKs
Wallet and key management infrastructure for agentic payments. Consult the provider's policy engine and integration requirements.
Developer tools
Developer tools for integrating Stripe services with agents. Inclusion as integration tooling does not certify autonomous payment safety.
Identity & policy
Bot verification via Web Bot Auth signatures. Identifying an automated agent is distinct from authorizing it to make a payment.
Identity & policy
OAuth 2.0 Token Exchange standard. Identity and delegation building block; not a payment execution protocol.
Try another name or clear the filters to return to the full directory.
Catalogue included in this edition. View raw public JSON data.
Could not check for updates. Keeping the profiles from this edition and their official sources. You can try again.
02 / Learn
Three core ideas to read the ecosystem critically. Open introductory material before moving to advanced guides and labs.
01 · Authorize
Define what the agent may pay for, to whom, for how much, and until when. Authorization must be verified before execution; if the scope changes, a new decision is required.
02 · Isolate
Tokenization replaces raw credentials with scoped references. It reduces exposure, but does not replace authorization controls or guarantee by itself that sensitive data is never touched.
03 · Verify
Idempotency allows repeating a request without duplicating its effect, within provider guarantees. Reconciliation compares records and outcomes to detect missing, duplicate, or pending charges.
03 / Discuss
The directory and fundamentals are open. The free community is the space to exchange implementation questions and share public references with a verified account.
Share concepts and sources; protect client data, credentials, and live payment information.
Free access · With account
Explore the space and its participation guidelines. Identity and permissions are verified before posting.
Enter the community04 / Go deeper
Pro brings together advanced material: guides, reproducible labs, and workshops. It is the paid layer of the portal; consulting is engaged separately.
Review the scope and available content before requesting access. The directory, fundamentals, and free community remain the open entry point.
Protected access
Decision-making guides and reproducible labs to test claims. Access depends on your account and active permissions.
Terms are shown before any purchase.This directory uses public references. Search runs in your browser; this page never asks for banking credentials or card numbers. Never share client data or real payment records in public spaces. When joining the community or requesting Pro access, review the applicable terms and data notice.
Trademarks belong to their respective owners. Their inclusion guides readers to official documentation and does not imply affiliation, endorsement, or production recommendation.