Stablecoins | Techlist.io

cloudflareAug 4, 20263 min readCurated summary

Announcing Cloudflare Wallets: The programmable wallet for the agentic Internet

Cloudflare is introducing Wallets to help AI agents discover, test, and pay for APIs without relying on humans to handle registration, billing, and API keys. Account Wallets will fund agent-controlled Virtual Wallets with configurable spending limits, while stablecoin micropayments through the x402 protocol enable machine-native transactions. Cloudflare also proposes human-readable wallet identities so merchants can recognize agents and their sponsoring organizations. ## The Challenge of Agent Onboarding - APIs are typically designed for humans, requiring login pages, payment methods, and manual API-key generation. - Agents lack: - Stable identities for signing up. - Native payment mechanisms. - As a result, agents often abandon API evaluation and delegate onboarding back to humans, limiting agentic commerce. ## Cloudflare Wallets and x402 Payments - Users can claim a Cloudflare Wallet handle that provides a persistent username for interactions with merchants. - Wallets will support: - Storing stablecoins. - Purchasing APIs, content, and other services. - Receiving funds. - Cloudflare’s Monetization Gateway will let eligible customers sell APIs and content through the x402 protocol. - x402 attaches micropayments directly to HTTP requests, supporting uses such as AI inference, data access, and content consumption. ## Account Wallets and Virtual Wallets - **Account Wallets** - Belong to human Cloudflare account owners. - Can be funded and drained by the owner. - Delegate spending authority to agents through Virtual Wallets. - **Virtual Wallets** - Are designed for agents and accessed through API keys. - Let agents spend independently within owner-defined limits. - Can enforce allowances, merchant allow lists, and maximum transaction sizes. - This structure gives agents autonomy while preventing uncontrolled spending. ## Enabling Low-Risk Exploration - Agents can try dozens or hundreds of APIs with inexpensive x402 micropayments. - Spending caps make autonomous experimentation safer: a small budget can support many low-cost trials. - Organizations could assign policies such as a $100 weekly AI-inference budget to each employee or agent. - Agents exceeding their limits can request a human override. - Administrators can review unusual spending, raise limits, or provide one-time funding when appropriate. - Cloudflare plans to support traditional funding and withdrawals in selected regions, with stablecoin self-funding available to eligible users. ## Building a Two-Sided Agentic Market - Monetization Gateway gives merchants tools to sell resources directly to agents. - Wallets add the buyer-side infrastructure needed for agents to purchase APIs, MCP tools, and content. - Together, these systems aim to create a machine-native marketplace where agents can transact without constant human intervention. ## Persistent Agent Identity - Merchants often cannot tell which person or organization an agent represents. - This makes it difficult to provide trials, credits, or other benefits without enabling abuse through large numbers of agents. - Wallets linked to Cloudflare accounts through `cloudflare.pay` will let agents optionally identify themselves. - An identity such as `research.example.cloudflare.pay` could indicate both the agent and its associated organization. - Agents may remain unidentified, while merchants can choose whether to prioritize known identities. ## Human-Readable Identifiers - Cloudflare compares agent identity to VPN use: an unidentified agent is not necessarily malicious but may need to establish greater trust. - Existing systems such as Web Bot Auth can associate agents with cryptographic keypairs. - Cloudflare Wallet handles would make those otherwise opaque identifiers easier for humans to recognize. - The proposal intentionally avoids defining a complete identity or verification standard, focusing instead on a simple, memorable naming layer. Cloudflare’s Wallets are intended to give agents both the ability to transact and the freedom to explore services safely. Account-level controls, Virtual Wallet spending policies, and optional persistent identities could provide the foundation for a more autonomous but accountable agentic economy.

Read original

Stablecoins AI Agents Agentic Commerce X402+4

cloudflareJul 1, 20263 min readCurated summary

Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402

Cloudflare is introducing the Monetization Gateway, which will let customers charge for web pages, datasets, APIs, and MCP tools protected by Cloudflare. It combines payment rules, access control, metering, and payment verification at the edge, initially using stablecoins through the x402 protocol. The goal is to make low-cost, usage-based payments practical for AI agents without requiring sellers to build billing infrastructure or onboard every buyer. ## The Web’s Shift Toward Usage-Based Payments - The traditional web monetized human attention through advertising, subscriptions, and e-commerce. - AI agents consume resources without viewing ads or maintaining subscriptions, creating a need for pricing based on actual usage. - Potential models include: - Charging a few cents per search. - Combining a base fee with usage charges, such as per megabyte uploaded. - Charging only when an outcome succeeds, such as a resolved support escalation. - Agents may generate thousands of requests and micropayments, making per-request, per-token, or outcome-based pricing more appropriate than monthly or per-seat plans. - Existing usage billing has generally required API keys, known customers, extensive accounting systems, and costly payment infrastructure. - Stablecoins such as USDC and Open USD can support sub-cent payments with low fees and settlement times under a second. ## Cloudflare’s Role in Usage-Based Billing - Cloudflare can use its position as a proxy between buyers and sellers to combine payment verification with the request path. - Metering, payment exchange, and settlement can occur away from the customer’s origin. - Customers retain control over: - Pricing. - Access rules. - Revenue. - Sellers will not need to onboard each buyer or build a complete billing system; they can define rules that determine when agents must pay. ## How x402 Payments Work - x402 uses HTTP’s `402 Payment Required` status code to add payments directly to ordinary web requests. - The flow is: - A client requests a protected resource. - The server returns a 402 response containing the price, accepted asset, and payment destination. - The client pays and retries the request with proof of payment. - A facilitator verifies the payment. - The server returns the requested resource. - There are no checkout redirects or separate payment APIs. - Payments settle peer-to-peer directly into the seller’s wallet. - x402 is well suited to machine payments because: - It supports very small transactions. - Buyers do not need an account with the seller. - The payment itself acts as the access credential. - Stablecoins offer fast settlement, low fees, and no chargebacks. ## Monetization Gateway Capabilities - Customers will define payment policies through a dedicated rules API using expressions similar to other Cloudflare rules. - The system will apply to traffic such as tokens, APIs, MCP tool calls, and datasets. - Enforcement will run across Cloudflare’s network in more than 330 cities, allowing payment handshakes to occur near buyers while reducing latency and protecting origins. - Planned functionality includes charging for specific REST methods and routes, such as requiring $0.01 for each `GET` or `POST` request to `/api/premium/*`. - The gateway is also intended to support variable pricing for tasks with different costs. Cloudflare’s approach is to make micropayments a native part of HTTP access, enabling businesses to charge agents directly for the resources they consume without constructing their own payment and accounting systems.

Read original

Stablecoins AI Agents Model Context Protocol Cloudflare+4

awsJun 15, 20264 min readCurated summary

AWS WAF adds AI traffic monetization capability to help content owners charge AI bots for content access | Amazon Web Services

AWS WAF introduces AI traffic monetization, allowing publishers to charge AI bots for content access at the network edge. Owners can set prices and access rules by content path and agent verification tier without changing origin infrastructure or building payment systems. The capability uses stablecoin payments and the x402 protocol, helping publishers recover costs from AI traffic that generates little referral value. ## Why AI Traffic Monetization Matters - AI crawlers now represent more than half of web traffic for many content providers. - AI-specific crawler activity has reportedly grown over 300% year over year. - Unlike search crawlers, AI agents often consume content without sending users back to the publisher. - Publishers still pay for bandwidth and infrastructure while losing potential page views, advertising impressions, and subscriptions. - AWS WAF Bot Control previously supported visibility, blocking, and rate limiting, but not payment collection. ## Setting Up a Protection Pack - AWS WAF Bot Control must be enabled at the Common or Targeted level on the web ACL associated with a CloudFront distribution. - A protection pack defines: - Monetized content paths - Pricing by agent verification tier - Accepted payment methods - License terms - Protection packs can be created in the AWS WAF and Shield console. - Users can associate CloudFront distributions, select managed security protections, and customize monetization settings. - Multiple protection packs can apply different pricing policies to separate content zones. ## Analyzing AI Bot Traffic - The AI traffic analysis dashboard divides requests into: - All bot requests - AI bot requests - Verified AI bot traffic - Unverified AI bot traffic - It reports bandwidth usage, estimated monthly cost, and peak request rates. - A per-path heatmap shows when and where AI agents access content. - AWS WAF Bot Control classifies more than 650 AI bot and agent types, including GPTBot, Claude-Web, and Perplexity-Bot. ## Agent Verification Tiers - **Verified:** Identity is confirmed through Web Bot Auth Ed25519 signatures or documented IP ranges with known user-agent and domain information. - **Unverified:** The agent is identified using user-agent matching, behavioral fingerprints, and IP reputation, but lacks cryptographic confirmation. ## Access and Pricing Actions For each verification tier, publishers can choose one of six actions: - **Monetize:** Charge for access and return an HTTP 402 response. - **Allow:** Provide free access. - **Block:** Deny the request. - **Count:** Log the request without charging. - **CAPTCHA:** Require human verification. - **Challenge:** Silently verify that the client is a browser rather than a bot. ## Stablecoin Payments and x402 - Publishers select supported blockchain networks and provide a wallet address. - Pricing is set as a base page price in USDC, with support for multiple networks. - AWS does not process payments or take a share of content revenue; settlement is handled by the publisher or wallet provider. - Monetized requests return an HTTP 402 response containing an x402 JSON price manifest. - The manifest specifies: - USDC price - Accepted networks, such as Base and Solana - Destination wallet - Payment timeout - Payment scheme - Compatible AI agents can submit signed payment authorizations autonomously. - AWS WAF verifies the payment, uses third-party facilitators such as Coinbase’s x402 Facilitator for on-chain settlement, retrieves the content, and returns it to the agent. ## Deployment Limits and Testing - Monetization rules are supported only on web ACLs associated with Amazon CloudFront distributions. - Regional web ACLs cannot use the Monetize action. - Real and Test currency modes can be switched from the monetization configuration page. - Test mode is intended for validating pricing, wallet settings, and x402 payment flows before production deployment. - Stripe account payments and Machine Payments Protocol support are planned for future releases. Publishers should first enable Bot Control and study AI traffic patterns before setting prices. Protection packs and test mode provide a way to apply differentiated policies while validating that automated payment and content delivery work correctly.

Read original

Stablecoins X402 Blockchain Cloudfront+3

stripeJun 4, 20263 min readCurated summary

New ways to turn global demand into revenue

Stripe argues that global expansion is increasingly accessible, but turning international reach into revenue requires solving localization, payment performance, money movement, and compliance challenges. Its Sessions announcements present an integrated set of tools for improving conversion, reducing fraud and costs, managing cross-border funds, and handling tax responsibilities. The overall conclusion is that businesses can scale internationally faster by relying on Stripe’s infrastructure rather than building country-specific systems themselves. ## Localize checkout to improve conversion - Checkout Studio helps businesses tailor checkout experiences to local markets using location data, industry recommendations, and performance tracking. - Stripe supports more than 125 payment methods, including Bizum, BLIK, TWINT, Sunbit, and Pay by Bank. - Stripe reports that showing even one geographically irrelevant payment method can reduce conversion by up to 15%. - Supporting locally preferred methods can significantly improve results: - Pix increases Brazilian conversion by up to 38.3%. - UPI increases Indian conversion by up to 19.8%. - Adaptive Pricing displays prices in customers’ local currencies and manages the associated conversion work. - Businesses see an average 5% increase in authorization rates and a 17.8% increase in cross-border revenue. - Subscription businesses see conversion improve by 4.7% and lifetime value per session increase by 5.4%. - Subscription pricing includes safeguards to keep renewal amounts consistent across billing cycles. ## Increase payment acceptance and reduce fraud - Authorization rates differ by region because of issuer behavior, payment networks, and local card preferences. - Stripe Authorization Boost uses real-time retries, issuer-specific messaging, Data Only authentication, and A/B testing to improve acceptance. - Businesses see an average authorization increase of 3.8%, while some customers reduce processing costs by up to 3.3%. - Stripe Radar detects and blocks risky transactions across cards, bank debits, wallets, buy-now-pay-later services, and stablecoin payments. - In a private preview, Radar reduced fraud by an average of 71% across Klarna, PayPal, Affirm, and Cash App Pay. ## Simplify cross-border money movement - Stripe Treasury lets businesses store, convert, and send funds in multiple currencies and stablecoins from a single account. - Businesses can hold different currencies without maintaining multiple bank accounts, local entities, or converting funds unnecessarily. - Currency conversion is available instantly, around the clock, with transparent rates. - Treasury supports payouts to more than 160 countries and enables employee cards funded directly from Treasury balances. - Stablecoin capabilities allow marketplaces and sellers to accept, hold, spend, and convert stablecoins into currencies such as ARS, COP, EUR, MXN, PHP, and USD. - Treasury operates in more than 120 countries, with stablecoin-backed balances available in 100 countries and planned expansion to 41 more by the end of 2026. ## Handle tax and regulatory compliance - International expansion requires navigating different tax systems, registration thresholds, invoicing rules, filing obligations, and dispute timelines. - Stripe Tax supports businesses that remain the merchant of record by automating: - Tax calculation and collection - Threshold monitoring - Registrations - Filing - It covers more than 100 countries and over 600 product categories, and is used by more than 67,000 companies. - Stripe Managed Payments acts as the merchant of record, handling tax registration, collection, and remittance in more than 80 countries. - Managed Payments also provides fraud protection, dispute management, customer support, and localized checkout. - The service is now available for digital goods and has supported companies including Unity, RevenueCat, and Lovable. Stripe’s broader recommendation is to treat international growth as an integrated operational problem rather than a series of separate country launches. Businesses can use localized checkout, automated payment optimization, Treasury, Stripe Tax, or Managed Payments to reduce infrastructure and compliance work while expanding into new markets.

Read original

Stablecoins Stripe Fraud Detection Adaptive Pricing+4

stripeApr 29, 20262 min readCurated summary

Giving agents the ability to pay

Agents are increasingly capable, but making purchases still requires access to today’s payment systems. Stripe is addressing this with Link’s wallet for agents, which lets users authorize purchases without exposing raw payment credentials. The system uses one-time cards or Shared Payment Tokens (SPTs), with users reviewing each request before approval. ## Link’s Wallet for Agents - Consumers connect an agent to their Link wallet through OAuth. - Agents can request: - One-time-use virtual cards - Shared Payment Tokens backed by cards or bank accounts in Link - Credentials can be restricted by amount, currency, and merchant. - Users approve requests on the web or through Link’s iOS and Android apps. - Users can track spending and manage connected agents in Link. - Stablecoins, agentic tokens, and additional payment methods are planned. ## Approval and Spending Controls - Each spend request currently requires explicit user review. - Link provides transaction context so users can understand what they are approving. - Future controls will support spending limits and allow agents to act without approval in predefined situations. - Agents never receive users’ underlying payment credentials. ## Stripe Issuing for Agents - Link’s wallet is built on Stripe Issuing infrastructure. - Businesses can use Issuing APIs to create customized agent wallets and card experiences. - Developers can control: - Onboarding and fund flows - Card-level permissions - Transaction authorization and fraud checks - Real-time and historical spending visibility - The infrastructure includes virtual cards, fund storage, spending controls, transaction monitoring, and fraud prevention tools. ## Potential Use Cases - Developers can automate business purchases and recurring spend. - Fintech companies can issue cards for real-time expense management and reconciliation. - Vertical SaaS platforms can let SMB agents make purchases under the platform’s brand. - Marketplaces can enable supplier payments, logistics, and fulfillment purchases through agent-issued cards. Stripe’s offering gives agents a practical way to transact through existing payment networks while preserving user oversight and credential security. Developers can use Link for a ready-made wallet or Stripe Issuing to build customized agentic payment workflows.

Read original

Stablecoins Database Design Oauth Link Wallet+3