UCP and Subscription Commerce: How AI Agents Handle Recurring Billing
How AI agents use the Universal Commerce Protocol to interact with subscription billing platforms, manage recurring payments, and enable autonomous commerce.
The Subscription Problem for AI Agents
One-time purchases are straightforward for AI agents. The agent discovers a product, reads the UCP manifest, initiates checkout, exchanges a payment token, and the transaction is done.
Subscriptions are different. A subscription is not a single transaction. It is an ongoing relationship between the consumer and a merchant that involves recurring charges, plan changes, cancellations, and sometimes failed payment recovery. The agent needs to interact with the subscription record, not just the checkout event.
This creates challenges that the base UCP spec does not fully address. The spec defines checkout, identity linking, order management, and payment token exchange. Subscription management sits on top of these primitives but requires additional capabilities: querying current plan state, initiating plan changes, handling proration on mid-cycle changes, and processing cancellations.
How the UCP Subscription Layer Works
Platforms like Chargebee, Recurly, Paddle, and Zuora are building UCP extensions for subscription commerce. The pattern is consistent across them.
Subscription state query. The agent uses an identity token to look up the consumer's active subscriptions. The response includes the current plan, billing interval, renewal date, payment method status, and any pending changes. This is a read operation that does not initiate a transaction.
Plan change. The agent submits a plan-change request through the UCP checkout flow. The checkout response includes the proration amount (credit for unused time on the current plan, charge for the new plan), the new recurring charge, and the effective date. The agent confirms or abandons the change based on the consumer's preferences.
Cancellation. The agent submits a cancellation request specifying whether to cancel immediately or at the end of the current billing period. The platform returns confirmation and, in some cases, a retention offer the consumer can accept before the cancellation is finalized.
Dunning events. When a payment fails, the platform emits an event that the agent can receive via webhook. The agent can prompt the consumer to update their payment method before the subscription lapses.
The Consent Problem
Subscription commerce requires more explicit agent authorization than one-time purchases. When an agent buys a book, the transaction is complete and the consumer can review it. When an agent modifies a subscription, the change has ongoing financial implications.
The UCP spec handles this through the identity-linking capability, which defines how consumers grant agents scoped permissions. For subscriptions, the permission scope needs to specify what the agent is allowed to do: read subscription state, initiate plan changes up to a dollar threshold, cancel at the consumer's request, or some combination.
Platforms implementing UCP subscription support need to design their permission scopes carefully. An agent that can cancel subscriptions without explicit per-action authorization is a liability. An agent that requires confirmation for every renewal is not useful. The right model is somewhere between these extremes, and the platforms building UCP subscription support are still working out the details.
Recurring Payment Mechanics
The payment token model in UCP works for one-time purchases and subscription initiation. For ongoing recurring charges, the platform holds a stored payment method reference on behalf of the consumer.
The agent's role in recurring billing is mostly supervisory. The platform charges the stored payment method on the renewal date. The agent does not need to re-authorize each renewal. But the agent can be notified of renewal events, failed charges, and payment method expiration so it can take action on the consumer's behalf.
GoCardless introduces a different model. Direct debit mandates authorize the merchant to pull payments from the consumer's bank account. The mandate is set up once, and subsequent charges do not require per-transaction authorization. For subscriptions, this is lower friction and has higher payment success rates than card-on-file billing. UCP's payment token model can represent a direct debit mandate as well as a card token, though platform support for this is not yet standardized.
Which Platforms Are Agent-Ready
Chargebee is building UCP support with a focus on subscription lifecycle management for B2B SaaS. Its API is well-documented and covers the full subscription lifecycle.
Recurly is building UCP checkout support with consumer media and streaming in mind. Its dunning management and promotion engine are relevant for agent-assisted retention.
Paddle handles tax compliance automatically, which simplifies agent-initiated B2B SaaS purchases in markets with VAT and GST.
Zuora targets enterprise subscription management. Its OrderLineItem model provides a detailed audit trail that is valuable for procurement agents managing complex contracts.
GoCardless is the best option for UK and European subscription payments that prefer bank-to-bank over card. Its direct debit mandate model has better payment success rates than card-on-file recurring billing.
Maxio handles complex B2B SaaS billing, including usage-based and hybrid pricing, that is difficult to represent in simpler billing platforms.
What to Build Now
If you are building an agent that manages consumer subscriptions, the practical path today is using the billing platform's REST API directly. Most platforms have good developer documentation, webhook support for lifecycle events, and programmatic access to subscription state.
The UCP subscription management layer will standardize this interface once platforms complete their implementations. Until then, treat the platform API as your integration target and design your agent's subscription management logic to be portable, using abstractions that can be swapped for UCP endpoints when they become available.
The core capabilities your agent needs: read subscription state, request plan changes with proration calculation, handle cancellation with retention offer logic, and receive dunning events. Build these four workflows and you have the foundation for agent-managed recurring commerce.
Read next
A developer guide to subscription billing platforms with UCP support or agent-friendly APIs, covering Recurly, Chargebee, Paddle, Maxio, and more.
A developer-focused primer on UCP. What it is, what problems it solves, and how the protocol works under the hood.
Everything you need to know about UCP, the open protocol enabling AI agents to shop, compare, and checkout on behalf of consumers across the internet.