IMF outlines policy questions for AI-intensive payments

Sourced news briefing

International Monetary Fund speech by First Deputy Managing Director Dan Katz published the development on 28 September 2026. The speech said efficient and secure payments are important to economic growth and stability. It considered how agents could compare fees, services, exchange rates and execution quality. It described potential automation of complex transactions, reporting and compliance. It also questioned how financial infrastructure and policy should adapt to autonomous agents operating continuously and at scale. The remarks presented policy analysis rather than a product launch.

This briefing reports only the source announcement. The speech describes possibilities and risks, not a finding that particular AI payment systems are safe, compliant or ready for merchant deployment. The remaining sections are independent FixPays analysis for merchants; they are not claims made by the IMF speaker.

Independent analysis: competition and routing transparency

Continuous route comparison could improve execution, yet a merchant still needs to know why a route was selected and whether commercial incentives distorted the outcome. Define routing objectives and prohibited trade-offs. Log provider and rate options considered. Set human review for material exceptions. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

The routing record should show data inputs, chosen path, price, expected timing, actual result and any override. 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: automated compliance with accountability

Automation can assemble evidence and prioritize alerts, but legal responsibility and difficult contextual judgments remain with accountable organizations and people. Validate data lineage. Measure false positives and false negatives. Require review for defined high-impact decisions. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

Governance should include model purpose, testing, version history, access controls, escalation and retained reviewer rationale. 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: machine-speed resilience

Continuous autonomous activity can concentrate volume and propagate mistakes faster than manual processes permit. Apply value and velocity limits. Use circuit breakers and rollback plans. Test dependencies under degraded service. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

Exercises should include bad data, duplicate instructions, unavailable providers and inconsistent responses across connected systems. 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

Document each automated payment decision and accountable owner. Connect that control to the routing engine and retain the result in a model inventory. 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.

Measure routing outcomes against declared objectives. Connect that control to the compliance model and retain the result in a decision 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.

Test limits and circuit breakers under realistic load. Connect that control to the payment instruction and retain the result in a resilience test. 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.

Review vendor concentration and exit options. Connect that control to the customer remedy and retain the result in a vendor assessment. 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.

Preserve customer-accessible support and correction routes. Connect that control to the routing engine and retain the result in a model inventory. 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.

Keep policy speculation separate from implemented controls. Connect that control to the compliance model and retain the result in a decision 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.

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 routing engine with the compliance model 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 a model inventory 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 decision log 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 control review follow-up resolution communication status beneficiary identity pricing data retention complaint fulfilment relevant merchant payment customer provider settlement records carefully.