Federal Reserve speech maps trust questions for AI-agent payments

Sourced news briefing

Federal Reserve Board speech by Governor Christopher Waller published the development on 29 September 2026. The speech described long-standing payment uses of machine learning and newer agentic systems that can plan and execute multistep tasks. It distinguished agent-assisted shopping from agent-delegated transactions. It identified authentication, liability and fraud as central trust questions. The speech said business purchases may suit rule-based agent activity but higher values increase exposure to errors or unauthorized action. It also discussed cross-border screening, routing, foreign-exchange and liquidity optimization.

This briefing reports only the source announcement. The speech raises policy and design questions; it does not authorize autonomous purchasing or prescribe a final liability framework. The remaining sections are independent FixPays analysis for merchants; they are not claims made by Governor Waller.

Independent analysis: prove delegated authority

A familiar customer account is not sufficient evidence that an automated agent had authority for a particular merchant, amount, product and time. Capture the customer’s mandate and constraints. Bind approval evidence to the order and payment. Expire or revoke permissions predictably. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

The transaction record should preserve agent identity, mandate version, item and amount limits, approval events and any human intervention. Review the arrangement by entity, market, currency, payment method and customer journey where those dimensions matter. A provider announcement cannot replace contract review, testing or a documented assessment of the merchant's actual operating model.

Independent analysis: design disputes before launch

Agent errors can blur the line among unauthorized payment, misunderstood instructions, unsuitable fulfillment and ordinary buyer remorse. Define customer support categories. Preserve catalog and price information shown to the agent. Make cancellation and return routes accessible to people. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

A dispute pack should reconstruct intent, authentication, agent actions, merchant confirmation, fulfillment and refund status without exposing unnecessary data. Review the arrangement by entity, market, currency, payment method and customer journey where those dimensions matter. A provider announcement cannot replace contract review, testing or a documented assessment of the merchant's actual operating model.

Independent analysis: recalibrate fraud controls

Models trained on human browsing and checkout behavior may flag legitimate machine-speed activity or miss coordinated agent abuse. Segment agent traffic visibly. Set velocity and value controls by mandate. Monitor merchants, platforms and agents for correlated anomalies. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

Risk review should compare authorization, false-positive, fraud and complaint outcomes for agent and conventional traffic. Review the arrangement by entity, market, currency, payment method and customer journey where those dimensions matter. A provider announcement cannot replace contract review, testing or a documented assessment of the merchant's actual operating model.

Independent analysis: merchant implementation checklist

Inventory where automated agents can discover catalogue data. Connect that control to the agent mandate and retain the result in an authority log. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Specify whether each journey is assisted or delegated. Connect that control to the order record and retain the result in a transaction trace. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Define acceptable proof of buyer authority. Connect that control to the authentication event and retain the result in a dispute file. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Test revoked, expired and over-limit mandates. Connect that control to the fraud decision and retain the result in a model-change register. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Update fraud monitoring without weakening human-channel controls. Connect that control to the agent mandate and retain the result in an authority log. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Assign responsibility for agent-originated complaints and refunds. Connect that control to the order record and retain the result in a transaction trace. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Commercial review should cover service levels, settlement timing, data duties, incident handling, customer support, termination rights and migration assistance. Finance should model both normal volume and stressed conditions rather than relying on a headline feature or a successful demonstration.

After launch, monitor authorization, abandonment, unmatched items, reversals, refunds, complaints, fraud, support effort and settlement differences using stable definitions. Segment results sufficiently to expose a corridor, method or product that performs differently from the portfolio average.

A controlled pilot should define scope, duration, success measures, stop conditions and rollback ownership. Preserve transaction traces and customer communications so reviewers can distinguish a product limitation, integration defect, user error, provider incident and deliberate risk decision.

Finance should reconcile the agent mandate with the order record on a stated timetable. Unmatched items need aging, ownership and escalation thresholds. A manual journal can correct accounting, but it should never erase the original variance, the investigation evidence or the reason a difference occurred.

Customer support needs status language that reflects the underlying system rather than guessing from a single dashboard. Staff should distinguish authorization, acceptance, processing, settlement, reversal and refund, then use an authority log to locate the authoritative reference before promising a time or outcome.

Risk teams should compare new behavior with established baselines while allowing for legitimate changes in channel and geography. Monitoring should reveal concentrated failures and unusual sequences without treating every unfamiliar pattern as fraud. Confirmed weaknesses belong in a transaction trace with an owner and response date.

Data governance matters because a new payment route often adds identifiers, vendors and cross-border transfers. Record which party receives each field, why it is needed, how long it remains available and how an access or correction request reaches the responsible organization.

Provider due diligence should be refreshed when the product, contracting entity, settlement account or subcontractor changes. Review permissions, financial and operational dependencies, security responsibilities, complaint cooperation and termination support. Evidence should describe the current service rather than an earlier sales presentation.

A management review should combine financial, customer, risk and operational measures. Record the decision to expand, constrain, remediate or stop the flow, including dissent and unresolved assumptions. This creates an auditable link between observed performance and the merchant's continuing use of the development.

Review transaction accounting access vendor service performance audit control review follow-up resolution communication records carefully.