Visa Pushes Agentic Ready to the Acquiring Side: Acquirers, Merchants and PSPs Begin Verifying 'Who Is Paying'
Visa expands Agentic Ready from 140 issuers to acquirers, merchants and PSPs, growing participants to 175 companies across 45 countries; how the acquiring side identifies agents, verifies authorization and limits becomes the new bottleneck for scaling agentic payments.

Visa announced on November 18, 2026 that it is expanding its Agentic Ready program—launched earlier this year for 140 issuers—to acquirers, merchants and payment service providers (PSPs). According to Visa, Adyen, Antom, Billtrust, Checkout.com, Fiserv, Global Payments, PayPal and Stripe have joined, bringing participants from the initial issuer group to more than 175 companies in 45 countries.
The program's function is not complicated: it provides participants with methods to test and validate transactions initiated by AI agents rather than by humans. What has changed is the direction of coverage—previously it focused mainly on the authorization side, i.e., how issuers identify a request initiated by an agent; now it extends to the acquiring side, where acquirers, merchants and PSPs must also be able to determine "who is behind this transaction."
Rubail Birwadker, Senior Vice President of Growth Products and Partnerships at Visa, said in a statement that merchants need confidence in "who they are doing business with," and payment service providers need to know these transactions can run safely and reliably through existing infrastructure—"no single company can solve this alone." Cindy Turner, Chief Product Officer at Global Payments, put it more directly: for agentic commerce to scale, merchants must be able to trust how agents identify themselves, what the customer has authorized, and how payment is executed.
Breaking these two statements down, the acquiring side actually has to answer three questions. First, identity: is the incoming request an agent, or a script masquerading as one? Second, authorization: how much is this agent allowed to spend on behalf of this user, on what, and to whom? Third, execution and liability: when a transaction goes wrong or is charged back, does responsibility fall on the issuer, the acquirer, the merchant, or the agent operator? In the traditional card network system, these three questions are shared by KYC, tokenization and chargeback rules; agentic payments replace the "operator" from a person to code, so the basis for judgment at every link in the existing chain must be realigned.
This is also why participants repeatedly mentioned things beyond "identity" in their statements. According to the report, some participating processors noted that agentic commerce going global requires capabilities beyond identity recognition; cross-border merchants introduce additional complexity in permissions, payment routing and business coverage. In other words, an agent authorization model that works in the U.S. market may not be directly reusable in scenarios with multiple currencies, multiple acquiring banks and multiple merchant types.
From the perspective of agent payment compliance and security that OceanAlt focuses on, the significance of this expansion lies in moving the point of "pre-settlement interception" forward. Identification on the issuer side occurs after an authorization request enters the network, whereas acquirers and PSPs sit between merchants and the network and can see more complete context: which operator this agent belongs to, which mandate it is bound to, whether the per-transaction limit and daily cumulative amount are within range, and whether the payee is on the whitelist. Completing these judgments before settlement is closer to operational risk control than post-hoc ratification. Correspondingly, if identity verification such as KYA (Know Your Agent) is only done at the issuer, the acquiring side remains a blind spot; by bringing PSPs in, Visa is effectively acknowledging that this verification needs to be present at both ends.
The impact is asymmetric for different types of participants. For acquirers and processors such as Adyen, Checkout.com, Fiserv and Global Payments, Agentic Ready provides a testing standard aligned with the card network; early entry means being able to tell merchants sooner that "we support agentic transactions." For companies like PayPal and Stripe that have both acquiring and wallet capabilities, agent identity and user authorization data are already in their hands, so the marginal cost of integration is relatively low. For merchants, the practical short-term benefit is being able to test in a controlled environment whether agent-initiated transactions are wrongly declined—false decline rates are the most tangible friction point in early agentic commerce.
There was another related development the same day: according to the report, Los Angeles-based Lightspark, founded in 2022, launched Agent Accounts, which it says allows AI agents to hold, spend, send and receive funds on behalf of individuals or businesses, covering more payment methods and currencies than other agent payment solutions; agents can pay with Visa cards, and if the merchant holds an agent account, settlement can be direct. This forms a contrast with Visa's path: the card network adds a layer of identity and verification on top of the existing clearing network, while Lightspark opens accounts for agents outside the network. Both routes ultimately must answer the same question—when funds are controlled by code, who records the authorization boundary, who verifies it, and who bears the liability when something goes wrong. By bringing the acquiring side into the testing scope, Visa at least puts this question in front of both ends of the transaction for the first time.
Original source: Digital Transactions · https://www.digitaltransactions.net/visa-widens-agentic-ready-beyond-issuers-to-include-acquirers/
Provenance & status
- Byline
- OceanAlt Editorial
- First published
- 2026-11-19
- Last updated
- 2026-11-19
- Content type
- Original compilation
- Source material
- View original ↗
Related reading

Fed and HKMA Speak on the Same Day: Two Compliance Tracks for Agent Payments Are Converging

HKMA and Swift Join Forces Again: Ensemble Connects to Swift Ledger, Cross-Border Clearing Layer Begins to Discuss Interoperability

Mastercard Pilots AI-Initiated Flight Booking: How Authorization Checks and Tokenization Form the Pre-Settlement Gate for Agent Payments
Paste a payee address before you pay and see whether it's on a sanctions list, through a mixer, or tagged for fraud.
This judgement can sit inside your own product
One line of code; it touches neither your CSS nor your JS. The same pre-settlement judgement can appear in your articles, on your wallet's confirmation screen, or as an endpoint your agent calls before it pays.

