{"id":122516,"date":"2026-07-29T08:44:11","date_gmt":"2026-07-29T08:44:11","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/122516\/"},"modified":"2026-07-29T08:44:11","modified_gmt":"2026-07-29T08:44:11","slug":"thredds-mccarthy-says-payments-will-govern-agentic-enterprise","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/122516\/","title":{"rendered":"Thredd\u2019s McCarthy Says Payments Will Govern Agentic Enterprise"},"content":{"rendered":"<p style=\"font-weight: 400;\">The interesting question about the agentic enterprise is not whether agents can act. They clearly can. It\u2019s whether enterprises can scale that action safely \u2014 and the evidence so far is that autonomy is harder to scale than the demos suggest. The bottleneck is not intelligence. It\u2019s permission, control and proof.<\/p>\n<p style=\"font-weight: 400;\">Businesses are putting policies and governance in place to safely scale generative AI across their enterprise. At Thredd, green shoots of innovation are sprouting daily, leveraging agentic capabilities for fraud, credit, sales, billing automation and client servicing. But we see the challenge, and equally the opportunity, for agentic experiences more acutely on the payment side, where an agent recommending a purchase, not all that interesting, becomes useful when it\u2019s trusted to initiate and complete a payment. At that moment the question stops being \u201ccan the agent pay?\u201d and becomes \u201cwhat is this agent permitted to do, on whose authority, under what limits, and how is that permission proven, monitored and revoked in the milliseconds an authorization takes?\u201d<\/p>\n<p style=\"font-weight: 400;\">That\u2019s a payments problem before it\u2019s an AI problem, and payments has a head start most people underestimate. At every technology inflection point during my career \u2014 eCommerce, mobile commerce, the launch of Apple Pay, cryptocurrency \u2014 someone predicted the end of cards, and yet each time the trust infrastructure proved far harder to replicate than the rails were to reinvent. Tokenization, scheme rules, dispute and chargeback rights, issuers that underwrite risk and bind consumers to credentials \u2014 these aren\u2019t legacy baggage. They\u2019re the exact controls agentic commerce needs, and they already exist.<\/p>\n<p style=\"font-weight: 400;\">But raw materials aren\u2019t readiness, and this is where the conversation gets too casual. A network token already carries merchant and category restrictions and can be revoked providing a real head start, not an answer on its own. The new work is binding a verifiable mandate to that credential which is essentially a cryptographic proof of what the consumer authorized their agent to do, and then surfacing, at authorization, a signal that an agent rather than a human initiated the transaction, so the issuer can decide in real time rather than discover it after the fact. Visa and Mastercard are standardizing this through Intelligent Commerce and Agent Pay respectively; we monitor and, in some cases, build those frameworks while staying deliberately neutral on the merchant-side protocols, so our clients, issuers and program managers, are insulated from bets that haven\u2019t been resolved.<\/p>\n<p style=\"font-weight: 400;\">It\u2019s also why a connection standard, on its own, doesn\u2019t solve this. Protocols like MCP matter because they standardize how agents plug into systems. They don\u2019t answer who authorized this agent, what the consumer actually intended, whether the behavior is anomalous or who is liable when it\u2019s disputed. Those are issuer-layer questions, and they don\u2019t get easier by stacking another protocol on top of them.<\/p>\n<p style=\"font-weight: 400;\">Liability is the one the industry hasn\u2019t fully answered, and the one I\u2019d tell any enterprise to watch. Fraud detection is being retuned for a new class of automated behavior. The old question was, \u201cis this the genuine customer?\u201d The emerging one is, \u201cis this still what the customer authorized the agent to do?\u201d That\u2019s necessary but not sufficient. The harder case is the agent that behaves exactly as mandated and the cardholder disputes anyway. Today\u2019s chargeback rules were never written for a third party acting on standing instructions. My view is that verifiable intent, proven at authorization, must become the basis for reallocating that liability \u2014 and the issuers who can prove intent will be the ones who can actually underwrite agentic commerce, not merely permit it.<\/p>\n<p style=\"font-weight: 400;\">For a card issuer, the point of sale is the tip of the agentic iceberg. Strip away the consumer experience and the work of card issuing is repetitive, rules-based, operational work. Things like reconciling settlement files, onboarding and screening customers, assembling dispute evidence, servicing cardholders and producing regulatory reports represent high-headcount work that has scaled almost linearly with volume. That\u2019s exactly the shape of tasks agents are good at, and where costs can actually be stripped out of businesses: an agent that reconciles a file and escalates only the genuine inconsistencies, or triages an onboarding case, breaks the link between growth and headcount that has constrained this industry for years. Programmable payments extend the same logic to money movement itself where value that moves on conditions and rules set in line with the transaction rather than preset instructions configured at the program level, with an agent orchestrating inside guardrails set by the customer.<\/p>\n<p style=\"font-weight: 400;\">An agent reconciling a ledger, or releasing a payment on a rule, needs exactly what an agent at checkout needs: defined permission, proof of what it was authorized to do, an audit trail and the ability to revoke it the moment something looks wrong. Solve that governance problem once and you apply it across the operation; that\u2019s the compounding advantage, and why the trust layer is worth owning. It\u2019s also where discipline matters most, because the back office is where autonomy is easiest to justify and hardest to trust. A silent reconciliation error doesn\u2019t announce itself, it compounds. Those who capture these savings will be the ones who put escalation thresholds, manual review thresholds and provable authority in place first \u2014 taking cost out rather than trading labor cost for risk.<\/p>\n<p style=\"font-weight: 400;\">The agentic enterprise won\u2019t be defined by how much autonomy it hands to AI, but by how well it governs that autonomy where liability shifts and value is created. The winners won\u2019t just have smarter agents. They\u2019ll have agent-ready infrastructure beneath them, verifiable intent underwriting it, and partners willing to absorb that complexity so they can move quickly.<\/p>\n<p style=\"font-weight: 400;\"><a href=\"https:\/\/www.pymnts.com\/wp-content\/uploads\/2026\/07\/2026-07-eBook-PYMNTS-Q2.pdf\" target=\"_blank\" rel=\"noopener nofollow\"><img fetchpriority=\"high\" decoding=\"async\" class=\"aligncenter wp-image-3981479 size-full\" src=\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/07\/Download-Building-the-Agent-Ready-Payments-Enterprise-July-2026.jpg\" alt=\"\" width=\"800\" height=\"350\"\/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"The interesting question about the agentic enterprise is not whether agents can act. They clearly can. It\u2019s whether&hellip;\n","protected":false},"author":2,"featured_media":122517,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[179,7493,25,427,462,66,3691,310,3689],"class_list":["post-122516","post","type-post","status-publish","format-standard","has-post-thumbnail","category-agentic-ai","tag-agentic-ai","tag-agentic-artificial-intelligence","tag-artificial-intelligence","tag-ebook","tag-featured-news","tag-news","tag-pymnts-ebook","tag-pymnts-news","tag-thredd"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/122516","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=122516"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/122516\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/122517"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=122516"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=122516"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=122516"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}