Visa, BILL and Billtrust have launched a live pilot in which AI agents complete supplier invoice payments that buyers have already approved. Announced on October 20, 2026, the initiative targets the manual work that can remain after an invoice clears a company’s approval process: opening a supplier portal and submitting the payment.
According to Visa’s announcement, the agent executes eligible, authorised payments. It does not decide which invoices a business should pay. That boundary is central to understanding what the pilot demonstrates.
How the payment moves between platforms
BILL provides the agent acting for the buyer. Visa supplies capabilities for agent identification and payment controls. Billtrust authenticates the agent at the supplier’s portal so the payment can proceed.
The announced workflow combines Visa’s Trusted Agent Protocol and Agentic Directory with tokenised payment credentials. Controls connect the transaction to the buyer’s approved instructions, while the payment path relates to a particular invoice. Visa says the design removes the need to share supplier-portal logins and provides visibility into payment authorisation and completion.
The pilot is processing transactions for participating BILL buyers and Billtrust suppliers. It is not a general release for every business using either platform.
What the companies expect it to change
FinTech Magazine’s reporting includes comments from BILL executive Mike Cieri and Billtrust executive Kunal Patel. Cieri describes security and finance-team controls as priorities for the payment agent. Patel describes supplier-portal authentication that allows an approved payment to finish without someone manually logging in to submit it.
The proposed benefit is less administrative work for buyers and quicker receipt of payments for suppliers, while suppliers retain their acceptance policies and reconciliation information. Those are the companies’ expectations. The coverage does not establish a measured reduction in processing time or payment errors.
Why approval and execution need separate controls
For finance teams, the useful distinction is between deciding to pay an invoice and carrying out that decision across another company’s system.
Consider a hypothetical invoice that has passed review for a specified supplier and amount. An agent could save time by completing the portal submission. But if the portal presents a different amount, an unexpected fee or an invoice that appears to have been paid already, the original approval does not automatically answer what should happen next.
This makes the scope of delegated authority important. A payment tool needs a clear response when the requested transaction no longer matches what the buyer approved. The relevant evaluation question is whether the workflow stops, explains the discrepancy and routes it for review.
Authentication addresses a different question: who is making the request? Recognising an authorised agent is useful, but a finance team also needs to know what that agent is permitted to do in this specific transaction. Both questions matter when software can move money.
A permitted route through the supplier portal
The pilot also illustrates a practical issue for the agent industry: completing a task depends on the receiving website accepting automated activity.
AgentsCalling’s coverage of Blackwall and AI-agent traffic examines how websites distinguish useful automation from unwanted requests. The payment pilot approaches that access problem through cooperation between the buyer’s platform and the supplier’s platform.
The implication for developers is that better navigation alone may not solve a blocked workflow. A receiving service may need a supported way to recognise the agent, associate it with a customer and restrict the actions available to it. The supplier remains a participant in that decision.
What would show that the pilot is ready to expand
The announcement does not specify participant numbers, transaction volume, success rates or a date for general availability. Those details will matter when judging whether the approach can work across a wider range of suppliers.
A useful evaluation would include interrupted payments and retries. For example, if a portal accepts a payment but the agent loses its connection before receiving confirmation, the workflow should establish the transaction’s status before submitting again. A completion message alone would provide too little evidence.
Finance teams should also be able to trace the approved instruction to the attempted payment and its eventual outcome. An operational record should help a reviewer answer which invoice was involved, what happened when an exception arose and whether a person changed the approval.
For this pilot, the next meaningful evidence would be completed transactions accompanied by reliable exception handling and measurable reductions in manual work. That would help businesses assess where payment agents can take responsibility within their existing approval processes.
Prepared with AI-assisted research and drafting. AgentsCalling has not independently tested the pilot.
About Puneet Sharma
Puneet Sharma · Freelance Writer
Puneet Sharma is a freelance writer covering AI agents, automation and the software changing how we work. His coverage at AgentsCalling starts with the questions a reader might ask over a conversation: What does this tool actually do? Where does it fall short? And is it useful beyond the demo? His articles explore new launches, practical workflows and the trade-offs behind giving software more responsibility, with explanations that make room for readers who are still getting familiar with AI.
