Know Your Human: KYC's Agentic Payment Gap

In April 2026, the International Monetary Fund published an unusual document. IMF Note 2026/004 — How Agentic AI Will Reshape Payments — formally identified autonomous AI agents as a structural threat to the identity verification frameworks underpinning global financial systems.

The IMF's concern is precise. KYC and multifactor authentication, the paper warned, "rely on explicit human action." When AI agents capable of executing payments, initiating transfers, and managing accounts act autonomously on a user's behalf, that foundational assumption collapses. The human who passed the original KYC check may have nothing to do with the transaction that follows.

This is not a theoretical future problem. According to LexisNexis Risk Solutions, agentic traffic — autonomous AI interactions with financial and e-commerce systems — rose 450 percent in 2025. Microsoft Security confirmed in February 2026 that 80 percent of Fortune 500 companies operate active AI agents. FIS, one of the world's largest payment processors, launched its industry-first agentic payment platform in May 2026. The deployment is already in progress. The compliance infrastructure has not caught up.

Why Traditional KYC Was Built for Humans — and Why That Breaks Down

Know Your Customer frameworks were designed around a specific assumption: a human being initiates a financial interaction, presents credentials, and is verified once at the point of entry. Subsequent interactions carry implicit trust because humans behave in recognizable, bounded ways. Anomalies are detectable. Liability is attributable.

AI agents systematically dismantle each of these properties.

When a user delegates financial authority to an AI agent — authorizing it to pay invoices, execute trades, book travel, or manage subscriptions — the agent can initiate dozens or hundreds of transactions without any further human involvement. Each of those transactions may cross regulatory thresholds that would ordinarily trigger re-verification. Each creates a liability question that existing frameworks cannot cleanly resolve.

Consider what happens when an AI agent, acting under a broad authorization, executes a sequence of crypto asset transfers in rapid succession. Under MiCA, every transfer must have a traceable, verified human principal. Under the Transfer of Funds Regulation, travel rule data must accompany every transaction. But the originating human verified their identity at onboarding, months earlier. Their current KYC status, risk profile, and behavioral patterns are not being assessed in real time. The agentic transactions proceed because no mechanism exists to interrupt them.

The Biometric Update identified this as a sector-wide shift in May 2026: financial services are being pushed toward "continuous identity" — a model where identity is not an event that happened at onboarding, but a validated state maintained throughout the customer lifecycle.

Know Your Human: The New Compliance Paradigm

The industry's response to this gap has a name. PYMNTS coined the term Know Your Human (KYH) to describe the compliance standard that places the verified, consenting human back at the center of every agentic transaction chain.

KYH is not a replacement for KYC. It is a layer that extends traditional identity verification to address three specific failure modes created by agentic commerce.

Delegated authority verification. When a user authorizes an AI agent to act on their behalf, KYH requires explicit, documented consent that specifies the scope of delegation. The agent may be authorized to pay utility invoices below €500 per month — not to execute equity purchases or initiate international wire transfers. Bounded, verifiable delegation is the compliance primitive that KYH introduces. Unbounded delegation is a liability gap.

Continuous validation. A one-time KYC check at onboarding is structurally insufficient when an agent will act autonomously for months or years afterward. KYH frameworks require ongoing confirmation that the verified human remains in control of the delegation — and that the agent's transactions remain within the authorized behavioral envelope. When an agent begins transacting in ways that diverge from the human's established pattern, the system must pause and re-verify.

Traceability for dispute resolution. When a transaction executed by an AI agent is disputed, the compliance record must reconstruct a complete chain of accountability: Did the verified human authorize this agent? Did the specific action fall within the authorized scope? Where did the behavioral baseline diverge? Without this audit trail, chargebacks, regulatory inquiries, and fraud investigations become legally unresolvable.

For a detailed look at the machine-facing side of this problem — verifying the agent's own identity and permissions — see our analysis of Know Your Agent (KYA): AI Identity Verification.

The Regulatory Exposure

For payment service providers, this gap generates concrete liability. Addleshaw Goddard's February 2026 analysis concluded that providers face "increased liability risk if they cannot validate whether a transaction has been duly authorized," especially where existing frameworks "were designed around human behavior, not autonomous agents."

EU-regulated entities face layered exposure. Under PSD3 and the Payment Services Regulation, strong customer authentication requirements were designed for human-initiated actions. Whether the initial human authentication satisfies SCA requirements for subsequent agentic transactions is unresolved. The European Banking Authority has not yet issued guidance specific to agentic payment flows.

Under AMLR and MiCA, the obligation is more direct: every transaction must connect to a verified human principal with an up-to-date risk profile. Current KYC architectures — designed for a world of human-initiated transactions — do not satisfy this requirement for autonomous agentic activity.

Beyond regulation, there is the fraud vector. An attacker who compromises an AI agent's session, or who manipulates the agent's instructions through prompt injection, can execute financial transactions that appear technically authorized — because they fall within the original human delegation — while serving entirely fraudulent ends. Traditional fraud detection models built around human behavioral patterns are poorly equipped to distinguish legitimate agentic behavior from agentic fraud.

What Compliant Agentic Identity Looks Like

Closing the Know Your Human gap requires re-architecting the identity stack around delegation, not just verification.

Dimension	Traditional KYC	Know Your Human
Verification moment	Once, at onboarding	Continuously, throughout agent lifecycle
Subject	Human identity	Human identity + authorized agent scope
Authorization record	Account credential	Delegation document with scope constraints
High-risk transactions	Human re-authenticates	Agent pauses, human re-authorizes specific action
Audit trail	Session log	Transaction log linked to delegation record
Anomaly detection	Human behavioral baseline	Agentic behavioral baseline within authorized scope

A compliant agentic identity system must do four things. First, it must capture delegation at authorization — when a user grants an AI agent authority to act, the scope of that authority must be recorded with the same legal precision as a KYC identity document. Second, it must enforce scope on execution — each agentic transaction must be validated against the recorded delegation before it proceeds. Third, it must maintain a live behavioral model — deviations from the human's authorized pattern should trigger re-verification before escalation. Fourth, it must produce a continuous audit trail — every agentic action traceable to the human authorization that permitted it.

This is the architecture that Joinble's AI Agents were built to support — not just verifying who a human is, but maintaining the continuous, traceable accountability of every action taken in their name.

For a closer look at how multi-agent systems handle compliance decisions without human intervention, see Agentic KYC: How Autonomous AI Agents Are Replacing Manual Compliance Reviews.

The Timeline: Acting Before the Guidance Arrives

The IMF published its warning in April 2026. FIS launched its agentic payment platform in May 2026. Visa's agentic commerce infrastructure is enrolling banks across Europe. The deployment cycle is ahead of the regulatory guidance cycle by a margin that is growing, not shrinking.

Organizations that build Know Your Human infrastructure proactively — before the EBA issues SCA guidance for agentic flows, before ESMA clarifies MiCA obligations for AI-initiated transfers, before the first enforcement action establishes liability precedent — will face a significantly lower remediation burden than those that wait.

The historical pattern of KYC compliance offers a consistent lesson: the cost of building identity infrastructure reactively, under regulatory pressure and with evidence preserved for investigation, is an order of magnitude higher than the cost of building it correctly the first time.

---

FAQ

What is Know Your Human (KYH)? Know Your Human is a compliance framework that extends traditional KYC to cover AI agents acting on a human's behalf. It requires documented delegation of authority, continuous validation that the human remains in control, and a full audit trail linking every agentic transaction to the authorizing human.

Why does traditional KYC fail for agentic transactions? Traditional KYC verifies a human identity at a single point in time. Once complete, the human's AI agent can execute transactions autonomously without any additional identity check. There is no mechanism in standard KYC to verify that each agentic action falls within the scope authorized by the verified human.

What did the IMF say about AI agents and KYC? IMF Note 2026/004, published April 22, 2026, warns that AI agents capable of executing payments expose gaps in KYC and multifactor authentication, which "rely on explicit human action." The IMF recommends developing trusted identity frameworks and interoperable standards for agentic delegation verification.

How is Know Your Human different from Know Your Agent (KYA)? KYA focuses on verifying the machine — establishing a digital identity for the agent and certifying what it is technically authorized to do. KYH focuses on maintaining the verified human's accountability throughout every transaction the agent executes on their behalf. Both are necessary; neither alone is sufficient.

What regulatory frameworks currently govern agentic payments in the EU? Agentic payments fall under PSD3, the Payment Services Regulation, AMLR, and MiCA for crypto asset transfers. None were designed with autonomous agents in mind, and regulatory guidance specific to agentic payment flows has not yet been issued by the EBA or ESMA as of May 2026.

How do I know if my KYC system is prepared for agentic transactions? Ask three questions: Does your system capture the scope of any AI agent delegations granted by verified users? Does it validate each agentic transaction against that delegation record before execution? Does it produce an audit trail linking every agentic action to the authorizing human? If the answer to any is no, your KYC architecture has an agentic gap.