AWS Bedrock added a new service section for Amazon Bedrock AgentCore Payments, which enables developers to build payment solutions that route transactions between AI agents, third-party wallet providers, and sellers. The updated terms explicitly state that AWS does not provide regulated financial services, does not hold customer funds, and is not responsible for wallets, private keys, or wallet provider services. Developers using this feature are solely responsible for regulatory compliance, transaction monitoring, security safeguards, and any resulting disputes or payment liabilities.
Developers: If you build payment solutions with this feature, you are responsible for ensuring your product meets all financial and industry regulations in the jurisdictions where you operate.
Developers: You must build security controls into your payment solution and remain responsible for protecting customer wallets and ensuring transaction accuracy.
This change introduces a new optional service feature rather than modifying existing consumer rights or obligations. AWS explicitly disclaims providing regulated financial services, holding custody of funds, or bearing responsibility for wallet providers or transactions. Developers who elect to use AgentCore Payments must comply with applicable financial regulations, implement their own security safeguards, and accept full liability for transactions and disputes. The terms do not impose obligations on end consumers using AI agents; the obligations fall on developers integrating the service.
→ If integrating AgentCore Payments, review your own compliance obligations under applicable financial services regulations in your jurisdiction.
→ Verify the regulatory status and terms of each third-party wallet provider you plan to support.
→ Update your customer-facing terms and privacy notices to disclose that AWS does not provide financial services and that wallet providers are third parties under separate agreements.
AWS explicitly disclaims providing regulated financial services, holding custody of funds or assets, and bearing responsibility for third-party wallet providers or their services.
Developers are solely responsible for regulatory compliance, obtaining required licenses, implementing security safeguards, and bearing all liability for transactions, disputes, and payment failures.
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
AWS introduced a new product service section establishing clear liability boundaries for a payment-routing feature. The updated terms disclaim regulated financial services status, custody responsibilities, and third-party liability. Organizations offering payment solutions through AgentCore Payments …
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-C-001826.
AWS Bedrock's service terms were updated in an update detected on July 30, 2026, with several operational refinements. The terms …
AWS updated its Service Terms on July 18, 2026 with several operational clarifications and restrictions. For On-Demand Capacity Reservations, the …
AWS Bedrock updated its AWS Clean Rooms service terms on July 11, 2026, revising how content deletion and resource removal …
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
Get alerted when this policy changes again, including what changed and why it matters.