Skip to main content
Skip to content
Agentic Finance

AI Agents and KYC/AML in 2027: The Principal, Permission and Payment Record

Connect the customer, beneficial-owner evidence, delegated authority and payment checks without treating an agent wallet as a compliance certificate.

Two illuminated identity cards representing the customer and delegated agent
Reading options: audio, text size & sections

Decentralised News · 2027 planning series · Reviewed 21 November 2026

What Matters

An AI agent’s wallet address or machine identity does not, by itself, answer a financial institution’s customer questions. A usable operating record must connect the customer or principal, the people who own or control it where relevant, the authority delegated to software, and the particular payment being attempted. Automation can collect and reconcile evidence. It cannot turn an unresolved identity, authority or sanctions question into a completed compliance decision simply by producing a confident answer.

The Signal: Evidence reviewed

Reviewed: 21 November 2026. This study uses the FATF Recommendations as amended in June 2026, FATF digital-identity guidance, South Africa’s FIC guidance and crypto Travel Rule, and OFAC virtual-currency guidance. These sources have different legal status and territorial scope. DN’s proposed record checker is a documentation workflow, not a legal determination or a production screening service. No personal identity documents, customer accounts or transactions were processed for this article.

DN Alpha Thesis: the agent needs a traceable principal

The operational advantage of agentic finance is that software can carry work across several services. That same feature can fragment the evidence. One provider knows the customer, another controls the wallet, a third evaluates the destination, and a fourth returns a settlement receipt. Each component can appear to work while nobody can reconstruct the full instruction and responsibility chain.

DN proposes a principal, permission and payment record that connects those components without copying every sensitive document into every system. Its purpose is to make a reviewer able to answer three questions: whose activity is this, why was this software allowed to perform it, and which checks applied to this exact attempted transfer? The record also needs an exception state when one answer is missing.

Four identities that should not be collapsed

For this article, principal is an operational label for the person or organization on whose behalf a workflow is being run. It is not a claim that one legal definition applies in every jurisdiction. Distinguish that principal from an account user, a beneficial owner and a software identifier. They may be connected, but their evidence serves different purposes.

Identity or roleQuestionRecord boundary
Customer or principalWho is entering the relationship or requesting the activity?Customer record and the applicable provider’s verification decision.
Owner or controllerWhich relevant people own or control the customer?Applicable ownership/control evidence and unresolved questions.
Authorized representativeWho was entitled to give the instruction or delegate a bounded task?Authority evidence, account role and approval scope.
Software instanceWhich agent, runtime and credential performed the action?Technical identity, version, permissions and execution logs.

The FATF Recommendations and their interpretive notes address customer and beneficial-owner identification, the authority of people acting for a customer, and ongoing due diligence. They are international standards implemented through national systems. DN’s inference for agent design is straightforward: a technical identifier cannot stand in for every distinct customer and authority question.

Consider a company employee configuring a payment assistant. The employee’s successful login may authenticate access. It does not automatically establish permission to move company funds to any destination. A valid software credential can likewise prove that a particular integration made a request while leaving the business authorization unresolved. A good record connects the layers rather than treating one successful check as universal permission.

Separate the international baseline from local obligations

South Africa supplies a concrete example. FIC Guidance Note 7B explains that accountable institutions must establish and verify the client and, where applicable, a representative or person on whose behalf the client acts. It also addresses legal-person ownership and control, beneficial owners and ongoing due diligence under the institution’s risk management and compliance programme.

That scope matters. The same document should not be presented as a rule imposed directly on every person who uses a personal automation tool anywhere in the world. First identify the relevant institution, activity and relationship. A builder serving several markets needs a documented requirements decision for each applicable operating arrangement, with qualified review where classification is uncertain.

For implementation, keep a requirements register outside the model’s free-form reasoning. Each entry should name the legal or policy source, jurisdiction, activity, responsible owner, effective status and review date. The agent can retrieve that register and flag missing evidence. Changing the underlying rule or waiving a required check should remain a separately authorized action.

Build the principal record before granting execution authority

DN’s proposed record begins with the relationship, not the transaction hash. Assign a stable customer-record reference, identify the service provider maintaining it and retain the review status relevant to the intended activity. If ownership or representative information is required, link the supporting records and identify the person responsible for resolving uncertainty.

A reference is not a substitute for accessible evidence. The responsible institution must be able to obtain the underlying material through its approved process. The design question is where that evidence belongs and which systems genuinely need it. A research agent may only need a status and a record identifier; an authorized reviewer may need access to the underlying documents.

The FATF’s digital-ID guidance emphasizes understanding assurance levels, architecture and governance when deciding whether a digital identity is suitable for customer due diligence. That supports a useful distinction: identity evidence has an assurance context. “Verified” is too vague unless the record explains what was checked, by whom and for which purpose.

Give the delegation a readable business meaning

A permission record should be intelligible to both the execution system and the accountable operator. DN suggests recording the permitted action, account or wallet, asset, network, beneficiary boundary, amount or rate limits, expiry, approval requirements and revocation owner. These are proposed engineering fields; the exact legal and contractual requirements depend on the arrangement.

Bind the instruction to the transaction it permits. If the principal approved a payment to one supplier on one network, a technically valid call to another recipient should not inherit that approval. Preserve the resolved values the executor evaluated, not only the original conversational instruction. This is particularly useful when several tools transform an invoice, quote or destination before execution.

A renewed credential should not silently inherit an expired business mandate. Likewise, an updated agent version should not acquire broader authority because it has a new tool available. Treat permission changes as visible events. Link the old and new versions so that a later reviewer can determine which authority applied when the action was attempted.

Make transaction monitoring independent of the agent’s explanation

The agent’s description of a payment is one input. It should not be the only explanation accepted by the control layer. DN proposes comparing the attempted action with the known relationship, permitted purpose, configured limits and applicable screening results. Resolve discrepancies before execution where the operating policy requires it, and route uncertainty to a responsible reviewer.

For example, “paying the usual supplier” should be reconciled with the actual destination and recipient record. A familiar name paired with a new address is a changed fact. A sequence of individually small transfers may also require review under the applicable monitoring policy. A model should not be allowed to redefine the beneficiary or fragment a transaction simply to obtain a favorable status.

Useful operational metrics include unresolved-case age, repeat exceptions, missing-evidence frequency and the share of decisions that can be reconstructed from retained records. These are proposed management measures, not indicators of legal compliance by themselves. A low alert count can reflect a quiet workflow, an insensitive rule or a failed data feed; interpretation requires context.

Sanctions screening needs a scope, a timestamp and an owner

OFAC’s virtual-currency guidance describes risk-based sanctions programmes and emphasizes that U.S. sanctions obligations also apply in virtual-currency activity. It discusses controls that use relevant customer, counterparty and geographic information. This is a U.S. example, not a claim that one OFAC check satisfies every jurisdiction’s requirements.

DN’s operating record should capture the screening service or process, the information considered, the check time, the rule or list version where available, the returned status and the escalation owner. A missing response should remain missing. An old favorable response should not silently become a fresh clearance for a materially changed recipient or transaction.

The agent can gather information needed for review and communicate an appropriate operational status. A designated process should determine how suspected matches are resolved and what communications are permitted. Do not let a general-purpose customer message expose confidential investigation or reporting details. The system needs a safe outward-facing message and a separate restricted internal case record.

The Travel Rule adds a transfer-information question

South Africa’s FIC Directive 9 specifies obligations for covered ordering, intermediary and recipient crypto asset service providers. It addresses originator and beneficiary information, counterparty-provider diligence and treatment of unhosted-wallet transfers. The FIC/FSCA advisory confirms its 30 April 2025 effective date.

The practical question for an agent-enabled workflow is which participant owns each required information exchange. A blockchain transfer receipt does not tell a reviewer whether the relevant offchain message was complete, sent to the intended provider or accepted. Link the payment attempt to the applicable transfer-information record, while preserving the difference between message delivery and regulatory adequacy.

Do not classify every personal-wallet movement using one generic threshold or label. The responsible provider must determine the applicable treatment from the relationship and transfer facts. Where an unhosted wallet is involved, record the provider’s assessment and any additional evidence required by its policy. The agent’s convenience is not a reason to reroute a payment to avoid an unresolved requirement.

Worked example: a company payment that should pause

Fictional scenario: a Cape Town business uses an assistant to prepare a stablecoin payment for an overseas software supplier. The business has an established provider account. Its customer record and required ownership information have been reviewed. The assistant is authorized to prepare payments, while execution requires a designated operator’s approval.

The invoice names the usual supplier but includes a newly supplied wallet address. The assistant copies the invoice description and proposes a transfer. The original beneficiary record points to a different address, and the available screening response predates the change. The transfer-information workflow also lacks an identified recipient-provider reference.

Nothing in this example proves fraud. It does establish unresolved facts. DN’s checker reports an incomplete record and lists the beneficiary, current screening and transfer-information questions. The appropriate next step is to resolve those records through the provider’s approved process and confirm that the execution approval binds to the resulting values. The assistant should not manufacture missing identity data or convert “not checked” into “no match.”

After review, suppose the supplier confirms a legitimate account change through an independently established contact route. The responsible process updates the beneficiary record, repeats the relevant checks and completes the required transfer-information steps. The operator then approves the exact proposed transaction. The record can now show a consistent path from principal and authority to execution, followed by a settlement receipt.

The example illustrates documentation sequencing, not a claim that this set of steps is sufficient in every legal situation. It also shows why a paid transaction and a complete review record are different outputs. A business needs the financial result and the evidence explaining how the result was authorized.

Use the DN Principal, Permission and Payment Record Checker

The instrument asks for the status of eight documentation areas: customer, required ownership/control information, delegated authority, beneficiary binding, applicable screening, transfer-information requirements, evidence access and retention, and exception ownership. It accepts status choices rather than names, identity numbers or document uploads. Use internal references in the underlying evidence packet, not personal data in the public worksheet.

Any policy block or unresolved material conflict produces an escalation result. Otherwise, missing evidence produces an incomplete-record result. A row marked not applicable requires an applicability decision, not an assumption. When every row is documented, the output says the packet is ready for authorized review; it does not authorize a transaction or certify compliance.

Recheck the packet when a beneficiary changes, a mandate expires, account control changes, a provider requests refreshed evidence or the applicable rules change. The tool deliberately provides no universal identity-expiry period. Your responsible institution’s current requirements and documented policy must supply that decision.

DN Principal, Permission and Payment Record Checker

Change the illustrative assumptions below. This worksheet runs locally in your browser. It records your declarations; it does not verify evidence, connect to accounts, submit instructions or grant approval.

Incomplete record

Documented records0 / 8
Supported not applicable0
Unresolved records8
Blocks or material conflicts0
  • This is documentation completeness only. It does not screen identities, establish beneficial ownership, certify KYC/AML compliance or authorize a payment. Keep personal records in the approved evidence system, not this worksheet.
  • Unresolved: Customer or principal record; Applicable ownership and control evidence; Delegated authority; Beneficiary and transaction binding; Applicable screening record; Applicable transfer-information record; Evidence access and retention; Exception and review owner.
Customer or principal record: unknown Applicable ownership and control evidence: unknown Delegated authority: unknown Beneficiary and transaction binding: unknown Applicable screening record: unknown Applicable transfer-information record: unknown Evidence access and retention: unknown Exception and review owner: unknown

The initial numbers are synthetic. Unknown evidence remains unresolved. Downloads contain the values you enter; use aliases and avoid private or identifying information.

Keep sensitive documents out of the general reasoning stream

DN recommends a two-layer architecture. An approved evidence system holds the sensitive material and its access controls. The agent receives the minimum status and references needed for its task. This is an engineering recommendation for reducing unnecessary exposure, not a claim that one storage arrangement satisfies all privacy or recordkeeping laws.

Log decisions without exposing secrets. An incident reviewer needs to know the applicable policy version, input references, approval, tool call and outcome. They rarely need an API secret copied into the same event. Design access for the people who investigate exceptions, retain evidence under the applicable schedule and distinguish operational audit records from model-training data.

Define the human veto as an operating responsibility

A human-review label is weak if nobody owns the queue or the reviewer cannot understand the transaction. Assign the accountable role, give it the relevant evidence and provide a clear way to pause or reject the action. The agent should preserve the unresolved state when that reviewer is unavailable instead of substituting a self-generated approval.

For cost planning, DN’s compliance-cost model helps estimate the recurring work of oversight. For the separate legal perimeter of trading and investment services, see the AI trading regulation guide. Neither replaces the customer and transaction records examined here.

Methodology, limits and update policy

This article separates documented regulatory materials from DN’s proposed implementation record. FATF standards, South African obligations and U.S. sanctions guidance are not interchangeable. No global KYC rule, institution approval, sanctions clearance, customer identity or legal classification has been determined by this study.

The checker measures the states selected by its user. It cannot verify the truth of a document, detect every false identity, identify every controller or know whether a provider’s process satisfies its obligations. A complete packet can still contain incorrect evidence. The responsible institution and qualified advisers must determine the applicable requirements and evaluate the underlying material.

Editorial scope: this article does not rank or endorse compliance providers. No personal records were used. The local instrument makes no identity-verification, screening or transaction request and offers no certificate or legal assurance.

Sources and evidence register

Primary sources reviewed on 21 November 2026. The article distinguishes documented facts, DN analysis and synthetic examples. Recheck changeable rules and configurations before acting.

  1. FATF Recommendations, June 2026 — FATF Recommendations updated June 2026: customer, beneficial-owner and representative evidence. International standards require national implementation.
  2. FATF Guidance on Digital ID — Digital identity assurance, governance and suitability for customer due diligence.
  3. FIC Guidance Note 7B — South African accountable-institution guidance dated 3 August 2026: clients, representatives, beneficial owners and ongoing due diligence.
  4. FIC Directive 9 — Covered crypto-transfer information and provider obligations, including risk-based unhosted-wallet policies. Paragraph 9.1 states the effective date.
  5. FIC/FSCA Travel Rule joint advisory — Joint advisory confirming that Directive 9 took effect on 30 April 2025.
  6. OFAC virtual-currency sanctions guidance — U.S. sanctions scope and risk-based controls for virtual-currency activity; no global clearance claim.

Frequently asked questions

Can an AI agent complete KYC instead of a person or company?

An agent can help collect, organize and submit information through an authorized process. The relevant institution still needs to determine the customer, applicable ownership or representative information, and required verification. A machine identifier alone does not answer those questions.

Is an agent wallet address proof of the customer’s identity?

It identifies an onchain account or destination. The relationship between that address, the customer and the permitted activity needs separate evidence appropriate to the provider and jurisdiction.

Do all AI agents have to follow South Africa’s FIC requirements?

This article uses South African accountable-institution and crypto-transfer rules as a scoped example. Applicable duties depend on the actor, activity and relationship; they should not be applied globally by analogy.

Does a favorable sanctions-screening result approve a payment?

It is one result from a defined process at a stated time. Identity, authority, beneficiary, transfer-information and other applicable controls remain separate questions.

What does the DN record checker prove?

It reports whether the user has marked the required documentation areas as complete, unresolved or conflicting. It does not validate personal documents, screen a wallet, approve a transaction or certify compliance.

DN research note: This article is original editorial analysis supported by the linked sources. Calculations and example cases are illustrative unless explicitly described otherwise. The worksheet is a planning aid; it does not carry out the actions it describes.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.