Visa, BILL and Billtrust say an AI payment agent is now completing approved supplier-invoice card payments in a live pilot. The companies announced the pilot on October 20, 2026. It is a business-to-business workflow for participating BILL buyers and Billtrust suppliers, not a card feature that any business can switch on today.
The important boundary is who makes the decision. According to Visa, the agent does not decide which invoice to pay. It executes a payment instruction the buyer has already approved.
What the pilot changes
Supplier portals often require a person to sign in, pass anti-bot checks and type payment details even after an invoice has cleared the buyer’s approval process. The pilot tests a way for an authorized software agent to complete that last step.
Visa’s October 20 announcement describes this sequence:
- A buyer approves an eligible invoice in BILL.
- BILL’s Payment Agent uses controls tied to that approved instruction and a tokenized payment credential.
- Billtrust recognizes the agent through Visa’s Trusted Agent Protocol and Agentic Directory.
- The agent submits the card payment through the supplier portal.
- The buyer and supplier keep visibility into authorization and completion.
Visa says this avoids sharing a supplier-portal login with the agent. Agent authentication can also satisfy protections that previously depended on CAPTCHA or another bot block. That is a pilot design claim from the three companies, not evidence that the method works on every supplier portal.
It is execution, not autonomous invoice approval
The companies’ FAQ is explicit: the AI agent is not making payment decisions. It handles payments that the buyer has already approved.
That distinction matters for finance teams. Invoice validation, approval authority and the final act of entering a payment are separate controls. The pilot automates the last one. It does not establish that the agent checked whether the supplier was genuine, whether goods arrived or whether the invoice amount matched a contract.
If a business evaluates this kind of workflow, it should keep the approval record separate from the execution record. The useful audit trail should show the invoice, approver, authorized amount, payment credential, agent identity, submission time and result.
Why tokenized credentials matter
Visa says the agent uses tokenized payment credentials rather than a shared portal password. A token can represent the payment credential without exposing the underlying card number to every system in the path.
The pilot also ties the payment path to a specific invoice and to buyer-defined controls. Those are narrower permissions than giving an automation a general company card and a reusable supplier login.
Tokenization does not prove that an invoice is legitimate, and it does not remove the need to reconcile the payment. It changes how the credential is presented and can reduce the amount of reusable card data exposed in the workflow.
Who can use it now
Visa says the pilot is live and processing end-to-end transactions with participating buyers that use BILL and suppliers that use Billtrust. The announcement does not publish general enrollment, pricing, supported card types or a rollout date for businesses outside the pilot.
That makes availability narrower than the phrase “AI invoice payments” may suggest. A BILL customer should ask whether its account, supplier and payment method are included. A Billtrust supplier should ask how the agent is authenticated and how the payment appears in its existing acceptance and reconciliation process.
What to check before relying on an agent payment
For a live payment, verify five records:
- the approved invoice number and amount;
- the person or policy that authorized it;
- the supplier account and portal that received it;
- the credential and limits assigned to the agent; and
- the authorization, settlement and reconciliation result.
Do not infer settlement from a successful portal submission. Card authorization, final settlement and the supplier’s application of the money to the correct invoice are different events.
Radlof’s Visa Intelligent Commerce guide explains the wider card-network framework. This pilot is a narrower implementation for commercial invoice payments.
