AWS Bedrock added a new service called AgentCore Payments (Preview) that enables developers to build payment solutions using AI agents. The service transmits API calls between AI agents, third-party wallet providers, and sellers, but AWS explicitly states it does not provide regulated financial services, does not hold funds, and is not responsible for wallets, digital assets, or wallet provider services. Developers using AgentCore Payments must comply with applicable laws, obtain necessary licenses, implement safeguards like human-in-the-loop controls, and bear sole responsibility for transactions, disputes, and payment liability.
Developers: If you build a payment solution using AgentCore Payments, you must follow all applicable laws and get any required government licenses.
Developers: You must build safety checks into your payment solution, such as requiring human approval before transactions.
Developers: You alone are responsible for protecting wallet credentials and verifying that transactions are correct.
Developers: You are fully liable for any payment problems, customer disputes, or losses that occur through your use of this service.
Developers: AWS can stop supporting a wallet provider you rely on, though it will try to give you notice first.
This change introduces a new optional service for developers building AI-powered payment solutions. The updated terms establish that AWS does not provide regulated financial services, does not hold or control funds, and is not responsible for wallet providers or their services. Developers using AgentCore Payments must comply with applicable laws, obtain necessary government licenses or registrations, implement safeguards such as human-in-the-loop controls, and accept sole responsibility for all transactions, disputes, and payment liability.
→ Review applicable financial services laws and licensing requirements in your jurisdiction before using AgentCore Payments.
→ Evaluate third-party wallet provider terms to ensure compatibility with your compliance and risk management framework.
→ Implement and document safeguards such as human-in-the-loop transaction approval controls appropriate for your use case.
AWS explicitly states it does not provide regulated financial services, does not hold funds, and is not responsible for wallets or wallet provider services.
Developers accept sole responsibility for compliance with applicable laws, obtaining licenses, implementing safeguards, and all transactions, disputes, and payment liability.
AWS may change or discontinue support for third-party wallet providers at any time, with prior notice if practicable.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Wording edits to this record that do not change what it claims. Changes to a claim are published as corrections.
AWS added AgentCore Payments as a preview service, explicitly disclaiming regulated financial services provision and fund custody. The terms establish that developers bear sole responsibility for compliance with applicable laws, obtaining licenses, implementing safeguards, and …
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
Unlock the full institutional analysis — InsightConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-X-001826.
AWS Bedrock updated its Service Terms to add AWS Elemental Inference to the list of Indemnified Generative AI Services and …
AWS Bedrock updated its Service Terms document date from September 1, 2026 to September 11, 2026. The only substantive change …
AWS Bedrock updated its AWS Service Terms to expand the list of services covered under its Indemnified Generative AI Services …
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
Get alerted when this policy changes again, including what changed and why it matters.