AI Agents Are Moving Money: Can You Govern Them?

Michael Johnson · 2026-11-10

AI agents are no longer just suggesting financial actions—they're executing them. They reconcile invoices, trigger procurement workflows, interact with APIs, and increasingly initiate payments under predefined conditions. That means the instruction to move money might not come from a person at a screen anymore. It could come from software acting under delegated authority. For the payments industry, this isn't just an efficiency gain. It changes how we think about accountability. ### Why Identity Alone Isn't Enough Historically, compliance has focused heavily on identity: who's the customer, who's the business, and who ultimately owns or controls it. Those questions remain essential. But in the world of agentic payments, identity alone is no longer enough. An agent can be perfectly identified and still initiate the wrong transaction, in the wrong context, at the wrong time. That's why I believe the industry now needs to move beyond simply asking "Know Your Agent" and start asking a more important question: Can you govern your agent? Knowing who an agent belongs to solves an identity problem. What determines risk is authority: what the agent is allowed to do, under what conditions, for how long, when that authority must stop, and who remains accountable for its actions. The next evolution of KYA should therefore not be a machine version of KYC, but a control framework built around delegated authority, continuously binding business intent, agent authority, and financial execution. ### Bind the Agent to an Accountable Principal The first step is still identity, but the goal isn't to create an independent financial identity for AI. Quite the opposite. Any agent capable of initiating financial actions should be bound to a real business principal that has already completed the appropriate KYB, risk assessment, and due diligence. The infrastructure should be able to establish which business account the agent represents, who created and authorized it, which credentials it's using, and whether that authorization remains valid. This relationship must be both technically verifiable and auditable. Financial institutions don't need to determine whether an AI is inherently trustworthy. What they need is a clear chain of accountability: Verified Business → Authorized Agent → Permitted Action → Transaction. Only when each link can be traced back to a real business principal and a valid authorization can machine behavior be governed within a regulated financial environment. > "The real question isn't whether the agent is trustworthy, but whether its actions can be traced back to a responsible party." ### Define the Mandate, Not Just the Limit Real risk control begins with authority. Traditional payment systems rely heavily on per-transaction limits, daily limits, account limits, and API permissions. But those static controls aren't sufficient for agentic payments. An agent shouldn't simply receive a spending ceiling. It should operate within a clearly defined business mandate. For example, a procurement agent may be authorized to pay suppliers, but only to verified counterparties, against valid purchase orders or invoices, from designated accounts, using approved settlement assets and payment routes, and within defined amount and time thresholds. A treasury agent may rebalance liquidity across predefined accounts but shouldn't automatically create new beneficiaries. A payroll agent may pay registered employee accounts but shouldn't be able to redirect funds to unrelated third-party addresses. The key question is therefore not only, "How much can this agent move?" but also, "Under what business context is this agent allowed to act?" Static limits restrict amounts. Context-bound authorization restricts behavior. For agentic payments, the second is the more important control layer. ### Every Transaction Must Prove Why It Was Allowed The third control layer is provability. Traditional payment logs can usually tell us who paid, who received the funds, how much moved, when the transaction occurred, and what its final status was. In agentic payments, that's not enough. You need to know why the transaction was allowed. What was the business justification? Which mandate permitted it? Which conditions were met? Without that proof, you can't govern the agent. You can only hope it behaves. And hope isn't a control. ### The Bottom Line AI agents are here to stay. They'll handle more financial actions, not fewer. But if we want to trust them with money, we need to move from knowing them to governing them. That means binding them to accountable principals, defining clear mandates, and proving every transaction's legitimacy. It's not about slowing innovation—it's about building the guardrails that let it scale safely. So ask yourself: Can you govern your agent? Because if you can't, you're not ready for agentic payments.