The Fintech Log

Visa Pilots AI Payments for Approved Invoices as Mastercard Tests Agents Under Spending Limits

Oct. 25, 2026  •  Article  •  AI in Fintech

Summary

Mastercard and Visa are advancing different approaches to AI-initiated business payments. At Cloudflare Connect, Mastercard demonstrated an agent making nine payments across multiple service providers under one authorized budget. It also opened early developer access to Agent Pay APIs, a sandbox and toolkits. Visa expanded its commercial agentic suite around a BILL and Billtrust pilot, alongside spend analytics and fraud tools.

The distinction is how each approach constrains the agent. Visa’s pilot lets an agent pay invoices that buyers have already approved, using its Trusted Agent Protocol to navigate supplier-portal security without sharing underlying login credentials. Mastercard is testing controls for machine-to-machine transactions, including signed vouchers, agent verification and a score intended to estimate whether an incoming transaction was AI-initiated. Both efforts leave a consequential question for business payments: how responsibility should be assigned when an authorized agent follows its technical instructions but breaches a procurement condition.

Full Article

Mastercard has demonstrated an AI agent making nine payments across multiple service providers under a single authorized budget, while Visa has expanded a commercial agentic-payments suite built around a BILL and Billtrust pilot. The developments show two different ways card networks are trying to establish trust when software, rather than a person at checkout, initiates a business payment.

At Cloudflare Connect, Mastercard presented its “Agent Pay for Machines” demonstration using the x402 HTTP protocol and signed vouchers. It has also opened early developer access to Agent Pay APIs, a sandbox environment and toolkits for automated machine-to-machine checkout. Visa’s expansion pairs its commercial pilot with SESA 2.0, or Supplier Enablement Spend Analytics, and Visa Commercial Fraud Solutions.

The distinction matters for businesses deciding which payment tasks software may perform. Visa’s pilot confines the agent to paying invoices already approved by a buyer. Mastercard’s demonstration instead shows an agent carrying out multiple payments within one authorized budget. Neither model, on the available information, amounts to an unrestricted delegation of purchasing decisions.

Visa keeps invoice approval with the buyer

The Visa, BILL and Billtrust implementation uses Visa’s Trusted Agent Protocol to let the BILL Payment Agent navigate CAPTCHA and anti-bot defenses on Billtrust supplier portals. The protocol allows that access without sharing underlying login credentials or creating separate portal accounts for the agent.

That solves a practical problem for automated accounts payable: a supplier portal must distinguish an authorized payment agent from unwanted automated traffic. In this pilot, the agent’s authority remains narrow. It executes payment for already-approved invoices under buyer-defined payment controls; it does not decide what to procure or approve an invoice on the buyer’s behalf.

Billtrust’s supplier network exceeds 20 million buyers and handles more than $1 trillion in annual trade credit volume, making portal access relevant beyond a single buyer-supplier connection. Those figures describe Billtrust’s network, not transactions processed by the agentic pilot.

BILL has reported that its internal payment risk intelligence flagged approximately $1.5 billion in errors and anomalous commercial invoices in fiscal year 2026. That figure does not measure losses caused by AI agents. It does, however, illustrate why businesses have reason to keep invoice review separate from automated payment execution.

Mastercard tests budgeted machine payments

Mastercard’s demonstration centers on an agent completing a sequence of payments within a preset budget. Signed vouchers provide a way to convey authorization for individual transactions, while the x402 HTTP protocol supports payment requests in the demonstrated workflow. The reported nine payments show execution across multiple service providers; they do not establish that the approach is generally available or suitable for every procurement process.

Mastercard describes its Agent Pay Trust Framework through five modules: identity, intent, controls, execution and intelligence. The framework integrates Skyfire’s Know Your Agent verification and Google’s Verifiable Intent. Together, those components address questions about which agent is acting, what it is authorized to do and how a payment fits within defined controls.

The company is also piloting an AI-initiation probability score with issuers in the United States. Its purpose is to estimate whether an incoming transaction originated from an autonomous agent. A probability score could inform an issuer’s assessment, but the stated pilot does not, by itself, establish who authorized a particular purchase or whether it met a buyer’s internal procurement rules.

Mastercard’s machine-payments pilot also demonstrated settlement across more than one payment rail. It incorporated Coinbase Developer Platform wallets, settlement on the Base network, and BVNK through the Mastercard Global Money Platform for stablecoin and fiat conversion. Those elements show the range of rails included in the pilot, rather than a commitment that all future Agent Pay transactions will use them.

Authorization is not the same as procurement compliance

Existing card-network dispute and chargeback rules address unauthorized credential use. A harder question arises if an agent has valid cryptographic authority to make a payment but acts before a supplier delivers goods, contrary to a buyer’s procurement conditions. The available information does not establish a defined liability structure for that scenario.

That gap helps explain why the two implementations place controls at different points. Visa’s pilot ties portal access and payment execution to invoices a human buyer has approved. Mastercard is testing agent identity, stated intent, budget limits and signals that could help identify AI-initiated transactions. These are distinct approaches to governing a payment, not evidence that either network has resolved every dispute an authorized agent might create.

For businesses, the immediate issue is therefore less whether an agent can technically complete a transaction than which decisions remain with the buyer and which controls travel with the payment. The pilots demonstrate progress in execution and verification. They also leave the allocation of responsibility for procedurally improper, but technically authorized, payments open.


By 'TFL Editorial Team'
Researched with AI tools. Edited and fact-checked by our editors.



You May Also Like

The Linux Foundation appointed payments veteran Michael Hursta executive director of the x402 Foundation on October 1, 2026, as payment systems designed for autonomous AI agents gained attention. Foundation members reported more than 75 million agentic payment transactions in a 30-day period in September, and Coinbase and Amazon Web Services showcased production payment rails at Sibos 2026. Reported transaction counts, however, do not establish the value or commercial character of that activity. The emerging protocols address different obstacles. Coinbase’s x402 enables per-request USDC payments through HTTP, while Google’s Agent Payments Protocol uses signed mandates to connect an agent’s purchases to a user’s authorization. Stripe and Tempo have also proposed session-based billing through the Machine Payments Protocol. These approaches respond to card fees and interactive checkout checks that can impede small, automated transactions. Card networks are developing delegated-identity tools, leaving multiple potential paths for agent payments rather than a single replacement for existing rails.

Oct. 28, 2026 • 3 min read

Mastercard opened developer early access for Agent Pay for Machines (AP4M) on October 20, 2026, releasing buyer- and seller-side APIs, a sandbox and developer toolkits. In a Cloudflare Connect demonstration, marketing agency Hype tested an autonomous agent making nine payments to two merchants within a single budget, without manual billing or account setup. AP4M uses HTTP 402 payment challenges, but differs from crypto-native implementations of the x402 protocol. Its agents issue digitally signed vouchers off-chain; merchants can batch and redeem them later instead of settling every request on-chain. The pilot combined agent wallet infrastructure from Coinbase Developer Platform and BVNK, settlement on Base, and Mastercard’s multi-currency fiat and stablecoin settlement platform. Circle separately expanded its managed payments service to target AI-agent traffic using USDC. Together, the developments show competing approaches to machine-to-machine payments, with different choices about settlement, funding and who manages digital assets.

Oct. 27, 2026 • 3 min read

Visa launched a live pilot with BILL and Billtrust at Money20/20 USA in late October 2026 to test end-to-end B2B invoice payments executed by software agents. The agents act on invoices enterprise buyers have already approved; they do not decide which supplier payments to authorize. Visa’s Trusted Agent Protocol and Agentic Directory are designed to authenticate those agents when they access supplier and merchant portals without shared credentials or manual human login. Separately, Visa has put Commercial Payment Controls into production for eligible issuers in supported regions, allowing businesses to set limits and restrictions on corporate spending. The company plans general availability of Commercial Virtual Authentication and Commercial Supplier Validation in 2027 after pilot completion. Its SESA 2.0 analytics platform has identified more than $600 billion in potentially cardable supplier spend. The pilot tests whether approved invoice payments can be executed through automated workflows while preserving buyer-defined controls.

Oct. 26, 2026 • 3 min read

Mastercard and Visa are advancing different approaches to AI-initiated business payments. At Cloudflare Connect, Mastercard demonstrated an agent making nine payments across multiple service providers under one authorized budget. It also opened early developer access to Agent Pay APIs, a sandbox and toolkits. Visa expanded its commercial agentic suite around a BILL and Billtrust pilot, alongside spend analytics and fraud tools. The distinction is how each approach constrains the agent. Visa’s pilot lets an agent pay invoices that buyers have already approved, using its Trusted Agent Protocol to navigate supplier-portal security without sharing underlying login credentials. Mastercard is testing controls for machine-to-machine transactions, including signed vouchers, agent verification and a score intended to estimate whether an incoming transaction was AI-initiated. Both efforts leave a consequential question for business payments: how responsibility should be assigned when an authorized agent follows its technical instructions but breaches a procurement condition.

Oct. 25, 2026 • 3 min read

Mastercard opened developer APIs, SDKs and a sandbox for Agent Pay for Machines (AP4M) on October 21, 2026. The tools enable autonomous AI agents on Amazon Bedrock to make multi-merchant micropayments over x402 using off-chain signed vouchers. The launch follows Coinbase Developer Platform’s report that cumulative x402 payments across Base and Solana had exceeded 100 million by October. The x402 protocol uses an HTTP 402 response to tell an agent what a service costs and how to pay. Its growing infrastructure includes a Linux Foundation-governed foundation, while alternative approaches use Lightning payments or existing processor rails. Transaction counts, however, do not establish how much genuine agent-led commerce is taking place. TRM Labs found a much smaller pool of plausible commercial trade after screening out other activity. Security questions also remain, including whether a service can receive payment without delivering its output. Developers therefore face choices about settlement, spending controls and proof of service.

Oct. 24, 2026 • 3 min read

CapitalOS completed a $21.9 million Series A financing round on October 21, 2026, led by LGVP. The company plans to expand its engineering team and scale the infrastructure behind its AI-driven money orchestration platform. WEX Venture Capital, Group 11, Great North Ventures, Night Capital and existing early investors also participated. Founded in 2022, CapitalOS helps vertical SaaS and AI platforms offer embedded charge cards, digital wallets and automated bill payments without maintaining in-house licensing or risk operations. Its architecture uses five specialized AI agents across underwriting, capital, compliance, risk and fraud, and support. Property management platform Guesty is an active customer, and CapitalOS reports managing transactions for more than 25,000 active cardholders across dozens of integrated platforms. CapitalOS relies on infrastructure provider Increase and its chartered partner banks rather than replacing depository institutions. The announcement did not disclose a valuation, credit warehouse partner or the identities of its current primary sponsor banks.

Oct. 23, 2026 • 3 min read