Concepts
Agentic commerce: how AI agents actually get paid
Agentic commerce means an AI agent handles the transaction instead of a checkout page. The term covers two very different worlds: autonomous agents paying each other with wallets and issued cards, and conversational agents collecting payment from a real person on a call or in a chat.
The autonomous world is being built now. The conversational world is generating revenue today, and it has a harder constraint at its center: a human saying their card number out loud to a machine, safely.
Two kinds of agentic payments
Agent-to-agent payments give AI agents their own wallets, accounts, and spending rules so software can transact with software. It is real infrastructure, and it is mostly still ahead of the market.
Human-present agentic payments are the ones happening at scale right now: a voice agent taking a takeout order, a support bot upselling a plan, a collections agent settling a balance. The agent closed the sale in conversation, and the payment has to happen in that same conversation or the sale decays.
The constraint nobody can prompt away
The agent must never see the card. PCI DSS puts any system that touches cardholder data in scope: the ASR pipeline, the LLM context, the recordings, the logs. An agent that hears a card number drags its whole stack into an audit.
So the defining primitive of human-present agentic commerce is the handoff: the agent steps aside for the moment card data exists, a compliant layer collects and charges it, and the agent gets the conversation back with a result. Done right, the customer never notices the seam.
What the payment layer has to do
A payment layer for conversational agents needs a few things that classic checkout infrastructure was never built for.
- Collect cards inside a live conversation, by voice, keypad, or inline widget, with real-time validation.
- Stay gateway-agnostic, charging the merchant's own processor instead of forcing a new one.
- Fire signed webhooks fast enough for the agent to react mid-conversation.
- Support tokenization, so an agent can save a card on file without charging it.
- Hand the conversation back the moment the payment resolves.
Where Maven fits
Maven is the payment layer for human-present agentic commerce. Voice agents on platforms like Vapi and Retell transfer the caller to Maven at payment time; chatbots mount an inline widget. Maven collects the card, charges the merchant's own gateway, and returns the conversation with a signed webhook. The agent stays smart, the stack stays out of PCI scope, and the sale closes in the moment it was won.
How a human-present agentic payment runs
- 01
The agent closes
Voice or chat, the customer agrees to an amount. This is the moment of highest intent in the entire funnel.
- 02
The handoff
The agent triggers a transfer or mounts a widget. From this moment, card data exists only inside the compliant payment layer.
- 03
Collection and charge
The card is collected conversationally, validated in real time, and charged through the merchant's own gateway.
- 04
The return
A signed webhook reports the result and the customer lands back with the agent, which continues knowing the payment cleared.
Common questions
What is agentic commerce?
Commerce where an AI agent handles the transaction flow instead of a traditional checkout: autonomous agents transacting with wallets and issued cards, and conversational agents collecting payment from real people on calls and in chat.
Can an AI agent legally take credit card payments?
Yes, as long as the card data is handled by PCI DSS compliant infrastructure. The agent itself must never store, process, or transmit the card, which is why a compliant handoff layer sits between the agent and the payment.
How is Maven different from agent wallet platforms?
Wallet platforms let AI agents hold and move their own funds. Maven handles the other side of agentic commerce: a real person paying an AI agent by card, in a live voice call or a chat thread, through the merchant's own gateway.
Add payments to your agent in minutes, not months
Connect your gateway, wire the handoff, and start collecting. Card data never touches your stack.