Which of these can take money
Every vendor in this category has an opinion about agentic commerce. Far fewer have shipped anything. Of 264 platforms we track, 2 can do anything with a payment, and 0 can complete a charge inside the agent session.
0
Completes a charge inside the agent session.
2
Sends a link or pushes to a checkout somebody else owns.
262
Books, qualifies or resolves. Money is out of scope.
The tracker
| Tool | Category | Capability | Rails | How we established it |
|---|---|---|---|---|
| Ringly.io | Voice Agent Platforms | Hands off payment | stripe-link | Order-status and returns flows can issue a payment or refund link through the connected store. The store owns the transaction. |
| Sierra | Inbound Qualification | Hands off payment | stripe-link | Agents can trigger order changes and refunds through connected systems where the customer has built that integration. Settlement stays in the customer's own commerce stack. |
Why this column exists
The agentic payments conversation runs about a year ahead of the people who will eventually buy into it. Stripe, Adyen, Visa, Mastercard, Klarna and Coinbase have all shipped protocols. The merchants and the agent vendors have largely not shipped integrations, and the gap between announcement and availability is where most of the confusion lives.
We looked for somebody tracking which agents can actually transact and found nobody doing it. The comparison SERP for agentic payments is dominated by a single vendor publishing its own alternatives pages. So we added a column.
The three states, precisely
- No. The agent books a meeting, qualifies a lead or resolves a call. There is no payment path and the vendor does not claim one.
- Hands off. The agent can trigger a payment link, a checkout redirect or an order change in a connected system. Settlement happens somewhere the vendor does not own. This is where nearly all real capability sits today.
- Native. The charge completes inside the agent session, on a rail the agent holds credentials for.
A vendor saying “we support agentic commerce” is almost always describing the middle state. That is not a criticism — handoff is frequently the better design, because it keeps card data out of your call recordings and off your PCI scope. But it is not what the marketing implies, and the distinction is worth having in a column rather than a paragraph.
What we will not do
We will not mark a tool as capable because a vendor announced a partnership or published a roadmap. This tracker records shipped, documented capability, and where we cannot establish it, the entry stays at “no” with a note. An empty column is more useful than a hopeful one.