How do I stop an AI agent from signing up for free trials and subscriptions that auto-renew?

What should I check, step by step?

1. Write the rule down: the agent may not accept recurring billing, auto-renewal or a trial that converts to paid without a human approving the specific terms. Put it in the agent's instructions, and enforce it in the checkout step rather than trusting the prompt.

2. Have the agent extract the terms before it clicks: merchant, plan, price after the trial, currency, billing interval, trial end date, cancellation method and the account email the merchant will use. If it can't find them, it stops.
3. Send those terms as the action object to request_human_approval (with a short summary and expires_in_minutes). The approval is bound to the SHA-256 of the canonical action, so approving a 9.00/month plan doesn't approve a 49.00/month one.
4. Call authorize_spend for the first charge (even a small verification charge) with reference set to the subscription or order id, so the sign-up shows up in the signed spend record next to the approval.
5. Pay recurring merchants with a dedicated virtual card per subscription. On Stripe Issuing, set spending_limits to the plan price per_authorization and a monthly (or yearly) interval, and add allowed_categories if you can. A renewal above the plan price, or an unexpected second charge, is declined at the card.
6. Route merchant emails to a mailbox a person reads. Visa requires merchants to send the subscription terms at enrollment and a reminder with a cancellation link at least 7 days before a trial converts or terms change; Mastercard requires a reminder 3 to 7 days before a digital-goods trial ends.
7. Keep a list of approved subscriptions with the trial end date and the card used. When a trial should end or the task is done, cancel with the merchant and set the card to inactive or canceled, so a missed cancellation can't keep billing.
8. Review the card's authorizations monthly against the approved list. A recurring charge with no matching approval means the agent (or someone) signed up outside the process.

Why don't spend caps stop an AI agent from signing up for auto-renewing subscriptions?

A spend check runs when the agent asks to pay. A free trial costs nothing at sign-up, so it passes any cap, and the renewals are merchant-initiated charges on the stored card that the agent never requests. The decision that matters is agreeing to recurring billing, and that happens at sign-up.

• This is the negative option pattern regulators target. ROSCA (15 U.S.C. 8403) requires online sellers to disclose material terms before taking billing information, get express informed consent before charging, and provide simple ways to stop recurring charges. The FTC's 2024 click-to-cancel amendments were vacated by the Eighth Circuit in July 2025, and in February 2026 the FTC restored the older rule text, so ROSCA and state auto-renewal laws are what apply.
• Card networks add merchant duties: Visa's April 2020 rules for free trials and introductory offers require express consent, a copy of the terms at enrollment, a reminder at least 7 days before billing after a trial, and easy online cancellation. Those protect the cardholder only if a person sees the emails, which an agent signing up on your behalf may not forward.

How do I make a human approve the recurring terms before an AI agent starts a subscription?

request_human_approval takes the action as an object and stores its SHA-256 (canonical JSON), a summary and an expiry (default 24 hours, up to 30 days). Only the owner's account key can decide it, and the decision is a signed record. Put the recurring terms in the action so the approval covers the renewal price and interval, not just today's 0.00.

• verify_human_approval lets the checkout step check that the approval exists and that its action hash matches the terms on screen. If the merchant changes the price or the interval, the hash no longer matches, and the agent has to ask again.
• authorize_spend then records the first charge against the agent's spending policy, with the subscription id in reference. Later renewals won't come through Rightshold, which is why the next step is at the card.

How do I cap subscription renewals an AI agent signed up for?

Renewals hit the stored payment method, so the hard limit has to live there. Stripe Issuing spending_limits set an amount per authorization, day, week, month, year or all time, and a cardholder's limits apply across all of their cards. One card per subscription makes a stray charge stand out and lets you stop one subscription without touching others.

• Stripe notes that tips and fees can be posted later and push spend past a limit, and spend aggregation can lag by up to about 30 seconds, so keep the card limit close to the plan price and check statements.
• Rightshold records approvals and signs spend decisions. It doesn't see merchant-initiated renewals, cancel subscriptions or hold cards. Cancelling with the merchant and turning off the card are steps you run, and the Rightshold records show who approved which terms and when.