AWS Security ChangesHomeSearch

AWS waf: AWS WAF monetization payment settlement options expanded

Service: waf · 2026-11-06 · Documentation low

File: waf/latest/developerguide/waf-ai-traffic-monetization-payment.md

Summary

Rewrites the payment settlement description to cover two settlement options: self-managed crypto wallets configured via CryptoConfig, and connected third-party payment accounts (e.g., Stripe) configured via ConnectedAccountConfigs with AWS-provisioned deposit addresses. Adds a step note about USDC transfers to deposit addresses and a link to the Stripe Connected Account Agreement.

Security assessment

The changed line only describes payment routing/settlement configuration (wallet addresses vs. connected payment provider accounts) and explicitly disclaims AWS involvement in fund flows. No vulnerability, credential handling, or security control is described.

Evidence

+You choose how to receive payments in your MonetizationConfig. You have two settlement options: settle to your own crypto wallet addresses that you configure with `CryptoConfig`, or settle through a connected account with a third-party payment provider (such as Stripe) that you configure with `ConnectedAccountConfigs`. In either case, AWS is not a party to or in the flow of funds for any payment you receive. With self-managed wallets, payments settle directly to the wallet addresses you configure. With a connected account, per-network deposit addresses are provisioned on your behalf and you don't manage wallet addresses yourself.

Diff

diff --git a/waf/latest/developerguide/waf-ai-traffic-monetization-payment.md b/waf/latest/developerguide/waf-ai-traffic-monetization-payment.md
index be74f52..e8a374a 100644
--- a//waf/latest/developerguide/waf-ai-traffic-monetization-payment.md
+++ b//waf/latest/developerguide/waf-ai-traffic-monetization-payment.md
@@ -15 +15 @@ You can now use the updated experience to access AWS WAF functionality anywhere
-You choose how to receive payments by configuring wallet addresses in your MonetizationConfig. Payments settle directly to your wallet. AWS is not a party to or in the flow of funds for any payment you receive.
+You choose how to receive payments in your MonetizationConfig. You have two settlement options: settle to your own crypto wallet addresses that you configure with `CryptoConfig`, or settle through a connected account with a third-party payment provider (such as Stripe) that you configure with `ConnectedAccountConfigs`. In either case, AWS is not a party to or in the flow of funds for any payment you receive. With self-managed wallets, payments settle directly to the wallet addresses you configure. With a connected account, per-network deposit addresses are provisioned on your behalf and you don't manage wallet addresses yourself.
@@ -23 +23 @@ You choose how to receive payments by configuring wallet addresses in your Monet
-  3. USDC is transferred from the client's wallet to your configured wallet address.
+  3. USDC is transferred from the client's wallet to your configured wallet address for self-managed wallets, or to the deposit address provisioned for your connected account.
@@ -31,0 +32,2 @@ Payment settlement is provided to you by Coinbase Developer Platform's x402 faci
+To open a Stripe Connected account, you must agree to the [Stripe Connected Account Agreement on the Stripe website](https://stripe.com/en-ca/legal/connect-account).
+