Agent Card Payments Compared: Visa, Stripe, Ramp & FluxA

Key takeaways

• Visa Intelligent Commerce and Mastercard Agent Pay define how AI agents transact on card rails, with live transactions now completed across the United States, Europe, Australia, New Zealand, and ASEAN. Both are infrastructure layers delivered through issuing and platform partners rather than products you integrate directly.
• Stripe, Ramp, Slash, and Robinhood each ship agent-facing card products with very different scopes: programmatic commerce for developers, corporate spend management, MCP-native business banking, and consumer credit.
• FluxA AgentCard takes a different approach: single-use, amount-locked virtual cards issued on demand from a co-wallet, paired with stablecoin-native protocol support across x402, AEP2, and MCP, so agents can pay both card-only merchants and machine-native endpoints from one balance.

Introduction

AI agents crossed a threshold in 2026. They research vendors, compare prices, and queue purchases on their own, and the payments industry has decided to meet them: Visa expects millions of consumers to use AI agents for purchases by the 2026 holiday season, and every major payment company now ships some form of agent card.

The result is a crowded landscape that is easy to misread. Visa and Mastercard offer network-level credentials you cannot integrate directly. Stripe, Ramp, Slash, and Robinhood ship card products aimed at four completely different buyers. FluxA issues single-use cards from an agent's own wallet. These solutions sit at different layers of the stack, and choosing the wrong layer costs you months.

This guide breaks down what each agent card solution actually does, who it is built for, and how they differ on the dimensions that matter: credential models, card lifecycle, stablecoin support, and protocol compatibility.

If you want platform by platform scoring instead of a head to head breakdown, our ranking of the best virtual cards for AI agents covers the same landscape from that angle.

What are agent card payments?

Agent card payments are transactions where an AI agent pays with a card credential issued for machine use rather than a card belonging to a human. The agent receives a tokenized or single-use credential with built-in controls: spending limits, merchant restrictions, expiry windows, and an audit trail tying every charge to a specific agent and authorization. This lets agents buy SaaS subscriptions, book travel, and pay at any card-accepting merchant without ever holding a real card number.

Which card networks support AI agent payments?

Both Visa and Mastercard now run dedicated agent payment programs, and both have moved from pilots to live transactions across multiple continents. They operate at the infrastructure layer: their credentials reach agents through issuing banks and platform partners, not through a direct integration.

What is Visa Intelligent Commerce?

Visa launched Intelligent Commerce in April 2025 to let AI agents transact securely across the Visa network. The approach centers on AI-ready tokenized credentials that replace standard card numbers, so agents transact without ever touching raw card data. Users keep control through preset dollar limits, merchant category restrictions, and real-time approval prompts.

Visa Intelligent Commerce at a glance:

• Launched: April 2025; Intelligent Commerce Connect added April 2026
• Built for: Issuers, processors, and platform partners
• Credential model: AI-ready tokenized card credentials with preset limits and merchant controls
• Trust layer: Trusted Agent Protocol, open framework since October 2025
• Status: Hundreds of live agent-initiated transactions across pilot partners including Ramp, Skyfire, Nekuda, and PayOS

In October 2025 Visa added the Trusted Agent Protocol, an open framework that helps merchants distinguish legitimate AI agents acting for consumers from malicious bots. Pilot partners including Ramp, Skyfire, Nekuda, and PayOS have completed hundreds of real-world agent-initiated transactions in closed beta, and Visa reports more than 100 partners building across the ecosystem.

The most significant recent step came in April 2026 with Intelligent Commerce Connect, a network-agnostic entry point to agentic commerce delivered through a single Visa Acceptance Platform integration. It handles payment initiation, tokenization, spend controls, and authentication in one place.

Intelligent Commerce Connect accepts agent transactions across four protocols:

• Trusted Agent Protocol (TAP)
• Machine Payments Protocol (MPP)
• Agentic Commerce Protocol (ACP)
• Universal Commerce Protocol (UCP)

Visa expects millions of consumers to use AI agents for purchases by the 2026 holiday season.

What is Mastercard Agent Pay?

Mastercard announced Agent Pay in April 2025 as its Agentic Payments Program, introducing Agentic Tokens, dynamic credentials built on the same tokenization rails that power contactless payments, card-on-file, and Payment Passkeys. Microsoft, IBM, and Braintree were named at launch, and Mastercard later co-developed the Verifiable Intent trust standard with Google.

Mastercard Agent Pay at a glance:

• Launched: April 2025
• Built for: Issuers and platform partners
• Credential model: Agentic Tokens built on existing tokenization rails
• Rollout: All US cardholders by November 2025; Australia, New Zealand, Europe pilot, and ASEAN through 2026
• Trust layer: Verifiable Intent standard co-developed with Google

Distribution has moved fast. The Agent Pay rollout timeline:

• September 2025: Citi and US Bank cardholders pilot Agent Pay
• October 2025: Agentic Tokens reach PayPal's wallet
• November 2025: All US Mastercard cardholders enabled
• January 2026: Commonwealth Bank and Westpac complete Australia's first Agent Pay transactions
• February 2026: Westpac completes New Zealand's first agentic transaction
• March 2026: A Santander pilot delivers Europe's first live end-to-end payment executed by an AI agent, conducted within Santander's regulated payment framework and not yet a commercial rollout
• April 2026: Authenticated agentic transactions go live across ASEAN markets, starting with Singapore and Malaysia

The ASEAN rollout was developed in collaboration with UOB and local bank partners, alongside plans for a regional AI Centre of Excellence in Singapore.

Which fintech platforms offer virtual cards for AI agents?

One layer up from the networks, fintech platforms package agent credentials into products developers and businesses can actually use. Stripe, Ramp, Slash, and Robinhood each ship one, and they serve very different buyers.

What is Stripe's agent card offering?

Stripe approaches agent cards as part of a broader agentic commerce stack rather than a standalone card product. Through Stripe Issuing and the Stripe Agent Toolkit, developers programmatically create scoped virtual cards, including single-use cards for a specific purchase.

Stripe agentic commerce at a glance:

• Launched: SPT and ACP in 2025; Machine Payments Protocol in March 2026
• Built for: Developers and merchants in the Stripe ecosystem
• Credential model: Issuing virtual cards via Agent Toolkit, plus Shared Payment Tokens scoped by merchant, time, and amount
• Protocols: ACP co-developed with OpenAI, MPP for stablecoin and fiat agent payments
• Adoption: Etsy and URBN on SPTs; Browserbase and Parallel charging agents via MPP

The deeper primitive is the Shared Payment Token, launched in 2025, which lets an agent initiate a payment using a buyer's permission and saved payment method without exposing the underlying credentials. Every SPT is:

• Scoped to a specific business
• Limited by time or amount
• Revocable at any time
• Monitored through webhook events

Etsy and URBN brands including Anthropologie and Urban Outfitters adopted SPTs early. In March 2026 Stripe expanded SPT support to carry Mastercard Agent Pay, Visa Intelligent Commerce, and buy now, pay later methods including Affirm and Klarna.

Stripe also co-developed the Agentic Commerce Protocol with OpenAI, the open specification behind Instant Checkout in ChatGPT, and in March 2026 introduced the Machine Payments Protocol, which lets businesses accept payments directly from agents in stablecoins as well as fiat with a few lines of code. Browserbase uses it to charge agents per browser session, and Parallel charges agents per API call for web access.

Stripe's strength is its developer ecosystem and its position on the merchant side. If you are building agents that buy from Stripe-powered businesses, the integration is native.

What are Ramp Agent Cards?

Ramp Agent Cards are virtual cards that let AI agents spend on behalf of businesses, built on Visa Intelligent Commerce with policy controls enforced before any transaction clears.

Ramp Agent Cards at a glance:

• Launched: March 2026, currently in early access
• Built for: Finance teams automating corporate spend
• Card model: Tokenized credential generated per transaction, scoped to one agent and one purchase
• Agent access: API, MCP, or CLI
• Controls: Spend caps, approval chains, and merchant restrictions applied before authorization
• Network: Visa Intelligent Commerce, with the Trusted Agent Protocol handling merchant trust

Because the agent only ever receives a temporary tokenized credential, raw card data never reaches it, which keeps PCI exposure off the table. The product sits inside Ramp's broader agent ecosystem of policy agents and AP automation.

In April 2026 Ramp and Visa expanded their partnership with a renewed multi-year issuing agreement covering agentic corporate bill pay. Ramp's strength is exactly this lane: procurement, vendor payments, and expense workflows with human oversight built in.

What is Slash's agent card product?

Slash offers agent-native banking and cards through MCP, so any MCP-compatible agent can operate a full business banking stack under mandatory human approval.

Slash for Agents at a glance:

• Launched: MCP server went live in March 2026
• Built for: Businesses that want an AI-native neobank
• Card model: Virtual and physical cards with daily, monthly, or lifetime limits
• Agent access: One MCP server URL, compatible with Claude, ChatGPT, Cursor, and custom agents
• Controls: Agents draft and submit actions, execution requires explicit human sign-off
• Stablecoins: On and off ramps built into the platform

The security design is distinctive: card numbers are encrypted before they ever reach the agent, and because no agent has unilateral execution power, a prompt injection attack cannot drain the account.

Slash's MCP integration covers cards, ACH payments, invoices, and transaction queries for the more than 5,000 businesses on the platform. Slash's strength is breadth: cards, banking, treasury, and crypto in one place, operated conversationally.

What is the Robinhood Agentic Credit Card?

The Robinhood Agentic Credit Card is a dedicated virtual Gold Card that an AI agent can spend on while the human keeps sole control of the limits, announced in May 2026 alongside Robinhood's Agentic Trading beta.

Robinhood Agentic Credit Card at a glance:

• Launched: May 27, 2026, in beta
• Built for: US consumers with personal AI agents
• Card model: Persistent virtual card, separate from the user's primary card, deletable at any time
• Agent access: MCP servers scoped to Robinhood's own surfaces
• Controls: Spending limits only the user can change, with optional approval on every transaction

The card matters less for its features than for what it signals: a major US consumer brokerage treating MCP as a payments rail. It is the newest entrant in this comparison and the only one aimed squarely at individual consumers.

What is FluxA AgentCard?

FluxA AgentCard issues single-use, amount-locked virtual cards on demand from a FluxA Wallet. The card is created for one task, funded at a specific amount, and permanently invalidated the moment the payment settles, with any unused balance returning to the wallet automatically.

FluxA AgentCard at a glance:

• Built for: Developers and teams running autonomous agents
• Card model: Single-use, amount-locked, provisioned on demand with no pre-registration
• Funding: Drawn from the FluxA Wallet balance per task
• Agent access: CLI, HTTP API, and MCP server
• Controls: Cards inherit the wallet's mandate policies, including spending caps, validity windows, and one-click revocation
• Audit: Every issuance, charge, and closure is logged with the agent's identity and mandate context
• Scale: More than 127,000 AI agents have created FluxA wallets, processing over 200,000 payment requests per month as of June 2026

This is the disposable virtual card model: one task, one card, zero lingering credentials. Even a fully compromised agent cannot exceed the amount locked into the card it holds, and a leaked card number points to a credential that has already closed.

The card solves the credential problem. FluxA Agentic Checkout solves the next one: actually completing a browser checkout. The checkout skill fills delivery, billing, and payment fields on validated routes, currently standard Shopify checkout and Stripe-hosted payment pages.

Every run starts in preview mode before execution, and the skill hands off explicitly to a human whenever CAPTCHA, 3DS, or login walls appear. Card issuance and checkout execution work as one flow inside the same AI agent wallet, governed by the same mandate.

How do the major agent card platforms compare?

The seven solutions above sit at different layers of the stack and make different architectural choices. The table below gives the one-screen view, and the six dimensions that follow go deeper.

Who is each agent card platform built for?

• Visa / Mastercard: Issuing banks, payment processors, and platform partners that want to enable agent-initiated transactions on top of existing card network rails.
• Stripe: Developers building agent-powered commerce applications, and merchants that want to sell through AI agents on Stripe's payment infrastructure.
• Ramp: Finance teams at businesses that want AI agents to handle procurement, vendor payments, and corporate spend with policy controls built in.
• Slash: Businesses that want an MCP-native neobank where agents manage cards, banking, invoices, and crypto under human approval.
• Robinhood: US consumers who want a personal AI agent to spend on a dedicated virtual credit card with user-controlled limits.
• FluxA: Developers and teams deploying autonomous agents that need to pay across both card rails and stablecoin rails from a single budget-governed wallet.

How does each platform give AI agents payment credentials?

• Visa / Mastercard: Visa issues AI-ready tokenized card credentials through Intelligent Commerce, and Mastercard issues Agentic Tokens through Agent Pay. Both are delivered through issuing partners, not directly to agents.
• Stripe: Programmatic virtual card creation through Stripe Issuing and the Agent Toolkit, plus Shared Payment Tokens that let an agent pay with a buyer's saved payment method without exposing credentials.
• Ramp: Tokenized credentials generated per transaction on Visa Intelligent Commerce, requested by the agent through API, MCP, or CLI, currently in early access.
• Slash: Virtual and physical cards created through Slash's MCP server by any compatible agent, with card numbers encrypted before they ever reach the agent.
• Robinhood: A dedicated virtual Gold Card provisioned for agent use through Robinhood's MCP servers, currently in beta for US accounts.
• FluxA: Single-use virtual cards issued on demand from the FluxA Wallet, funded at a specific amount per task, with no pre-registration or approval queue.

What happens to an agent card after a transaction?

• Visa / Mastercard: Tokenized credentials persist under the controls the user set, such as dollar limits and merchant category restrictions. Revocation happens at the token level.
• Stripe: Issuing cards can be configured as single-use or persistent. Shared Payment Tokens expire on their time and amount limits and can be revoked at any time.
• Ramp: Each credential is scoped to a single agent and a single transaction, then expires. Spend posts to the business's Ramp account for reconciliation.
• Slash: Cards persist until closed, with daily, monthly, or lifetime limits the agent can adjust within its permissions.
• Robinhood: The virtual card persists under user-controlled limits and can be deleted at any time without touching the primary card.
• FluxA: The card is permanently invalidated the moment the payment settles, and any unused balance returns to the wallet automatically. This is the core advantage of single-use cards for AI agents: a leaked credential points to a card that has already closed.

Do agent cards support stablecoins?

• Visa / Mastercard: Visa runs active stablecoin settlement pilots, and Mastercard is extending agent credentials toward public blockchains in early deployment. Neither offers native stablecoin support inside its core agent card framework today.
• Stripe: The Machine Payments Protocol accepts stablecoin payments from agents alongside cards and buy now, pay later methods, and x402 integration covers USDC on Base.
• Ramp: Agent Cards are fiat corporate cards. Ramp offers stablecoin business accounts as a separate product line.
• Slash: Stablecoin on and off ramps are built into the platform, so businesses can move between fiat and crypto natively.
• Robinhood: The Agentic Credit Card is a fiat credit product with no stablecoin component.
• FluxA: Stablecoin-native by design. The wallet holds USDC, agents make autonomous payments over x402 and AEP2, and the same balance funds single-use cards for merchants that only accept card payments.

Which agent protocols does each platform support?

• Visa / Mastercard: Visa's Intelligent Commerce Connect accepts agent transactions across the Trusted Agent Protocol, the Machine Payments Protocol, the Agentic Commerce Protocol, and the Universal Commerce Protocol. Mastercard co-developed the Verifiable Intent trust standard with Google.
• Stripe: Co-developed the Agentic Commerce Protocol with OpenAI, ships the Machine Payments Protocol, and exposes agent tooling through the Stripe Agent Toolkit and MCP.
• Ramp: Agents request credentials through API, MCP, or CLI, with Visa's Trusted Agent Protocol handling merchant-side trust.
• Slash: Built around MCP. Any MCP-compatible agent, including Claude, ChatGPT, and Cursor, gets access to the full banking API through one server URL.
• Robinhood: MCP only, scoped to Robinhood's own trading and banking surfaces.
• FluxA: x402 supported natively at the HTTP level, AEP2 embeds signed payment mandates inside x402, A2A, and MCP calls, and the FluxA MCP server exposes payment, payout, mandate, and card issuance tools to any agent framework.

Can developers build on these agent card platforms?

• Visa / Mastercard: Yes. Both are infrastructure layers explicitly designed for partners to build on.
• Stripe: Yes, through Stripe Issuing, the Agent Toolkit, and the open ACP and MPP specifications.
• Ramp: No. Agent Cards are designed for Ramp's own corporate customers.
• Slash: Partially. The MCP server is open to any agent, but it operates on Slash business accounts rather than serving as issuing infrastructure for other platforms.
• Robinhood: No. The card is scoped to individual Robinhood accounts.
• FluxA: Yes. The wallet, card issuance, mandates, and payout tools are exposed through HTTP API and MCP, and AEP2 is published as an open specification.

Why do developers choose FluxA AgentCard?

The platforms above each solve part of the agent payment problem for a specific buyer. FluxA is built for the case where the agent itself is the user: it needs to pay machine-native services and card-only merchants from one budget, autonomously, without a human clicking confirm on every transaction.

Through one wallet, agents get:

• Single-use cards for the card-only web. SaaS tools, marketplaces, and travel sites that will never support an agent protocol still accept a FluxA AgentCard, because it settles like any other card payment.
• Protocol-native payments for everything else. x402 support at the HTTP level, and AEP2 mandates embedded directly inside x402, A2A, and MCP calls for high-frequency machine commerce in USDC.
• One mandate instead of per-transaction approvals. With Intent-Pay, the human approves a budget once, and every spend inside it is auto-signed while anything off-mission is blocked at the wallet. Teams can set up an agent wallet and issue a first card in about ten minutes.
• Spending controls every agent deployment needs. Per-agent monthly limits, host-scoped policies, approval gates, and audit logs are enforced at infrastructure level, not in application code an agent could route around.

FluxA runs in production today: more than 127,000 AI agents have created FluxA wallets, processing over 200,000 payment requests per month as of June 2026. Reforge VC's autonomous research agent Ava and OpenClaw's ClawPi social gifting circle both transact through FluxA wallets.

Which agent card solution should you choose?

The answer depends on which layer you are building at and who pays the bill.

• Best for issuers and platforms building on card rails: Visa Intelligent Commerce and Mastercard Agent Pay. They set the standards, but they are infrastructure that partners build on, not products a developer integrates on a Tuesday afternoon.
• Best for the Stripe ecosystem: Stripe, especially if your agents buy from Stripe-powered merchants or you want to sell through ChatGPT.
• Best for corporate spend: Ramp, with agents handling procurement and vendor payments under accounting-grade controls.
• Best for MCP-operated business banking: Slash, an entire neobank operable through MCP with a human signing off on every execution.
• Best for individual consumers: Robinhood, one personal agent and one virtual card per person.

FluxA is built for the remaining case, which is also the fastest growing one: autonomous agents that need to pay both machine-native services and ordinary card-only merchants from a single budget. One mandate covers the mission, x402 and AEP2 handle the protocol-native payments in USDC, and a single-use AgentCard covers everything that still wants a card number. If your agent is the user, that is the architecture designed for it.

For a scored ranking across all of these platforms, the 8 best virtual card platforms compared takes the rankings view of the same market.

FAQs

How do single-use virtual cards work for AI agents?

The agent requests a card at the moment a task requires payment. The card is created on demand, funded at a locked amount, and used for exactly one transaction. Once the payment settles, the card number is permanently invalidated and any unused balance returns to the funding wallet. FluxA AgentCard implements this model with mandate-governed issuance and a per-agent audit trail, so a leaked credential points to a card that has already closed.

What is the difference between Visa Intelligent Commerce and Mastercard Agent Pay?

Both are network-level programs that give AI agents tokenized card credentials with user-defined controls. Visa Intelligent Commerce launched in April 2025 with the Trusted Agent Protocol for merchant-side trust and added Intelligent Commerce Connect in April 2026 as a multi-protocol entry point. Mastercard Agent Pay, also launched in April 2025, issues Agentic Tokens, has rolled out to all US cardholders, and has completed first authenticated transactions in Australia, New Zealand, and ASEAN. Neither is integrated directly: both reach agents through issuing and platform partners.

Do AI agent virtual cards support stablecoins?

It depends on the platform. Ramp and Robinhood are fiat-only card products. Slash builds stablecoin on and off ramps into its banking platform. Stripe accepts stablecoin payments from agents through the Machine Payments Protocol. FluxA is stablecoin-native: the wallet holds USDC, agents pay services over x402 and AEP2 directly, and the same balance funds single-use cards for merchants that only accept card payments.

Which agent card platforms support MCP?

Most of the 2026 generation. Slash exposes its full banking API through one MCP server URL. Ramp accepts credential requests over MCP alongside API and CLI. Robinhood's Agentic Credit Card is operated entirely through MCP. Stripe ships MCP tooling within its Agent Toolkit, and FluxA's MCP server exposes payment, payout, mandate management, and card issuance to any MCP-compatible agent framework.

Is it safe to give an AI agent a virtual card?

It is safe when the infrastructure enforces limits the agent cannot route around. The controls that matter are amount caps locked into the credential itself, merchant or host restrictions, approval gates for spending outside the mandate, and an audit trail tied to agent identity. What is not safe is sharing a real card number: it exposes the full credit line, persists after the task, and mixes agent spend with human spend. Single-use, amount-locked cards remove all three risks structurally.