How do I let my AI agent pay for a subscription that bills every month?

Last reviewed: August 2026

Why the first month works and the second fails

A merchant that sells a subscription keeps the card on file and charges it again on each renewal date. The same is true of ad platforms, cloud hosting, and AI inference providers that bill after use. Two things have to be true on that later date: the card is still open, and it has enough money available for the full charge. A card built for one checkout fails the first test, and a card loaded with one month of spend fails the second.

So the card for a subscription needs three properties: it survives more than one charge, its limit or balance can be raised without replacing the number the merchant has saved, and something outside the agent decides how much it can spend.

The options at a glance

Option 1: a merchant-locked card from Privacy

Per Privacy’s post on its API for agent workflows, an agent creates a card with a POST to /v1/cards, choosing the card type, a spend_limit in cents, and a spend_limit_duration. A merchant-locked card locks to the first merchant that charges it, and Privacy lists recurring subscriptions such as API billing, cloud hosting, and SaaS tools as its use. A MONTHLY duration resets total spend each calendar month, which matches a subscription closely. Its single-use card closes after the first transaction, so it is the wrong type here. Privacy states that API access is available on its Plus ($5 per month), Pro ($10 per month), and Premium ($20 per month) plans.

Option 2: Ramp Agent Cards

Per Ramp’s post on virtual cards for AI agents, Ramp Agent Cards are in early access and use tokenized credentials. An agent card is issued over the API in seconds, with a hard cap per transaction and a lock to a specific vendor. The post notes that multi-use cards with recurring limits are the fit for ongoing charges such as SaaS subscriptions. Ramp describes itself as built for B2B agentic finance workflows, so this route suits a company that already manages its spend there.

Option 3: a virtual card from Meow

Per Meow’s post on corporate cards for AI agents, card issuance runs through the same MCP endpoint and dashboard as the rest of a Meow account, and agent-issued cards are virtual by default. Its example for a SaaS subscription is a virtual card with a monthly cap, the total the card can spend in a calendar month, which is set at issuance and adjustable later through the dashboard or the API. A card can also be limited to merchants in a list of merchant category codes. A card belongs to a Meow account, so this is a route for businesses that bank there.

Option 4: a Laso reloadable card funded in USDC

Laso’s reloadable card is built for merchants that keep a card on file. One card stays open across charges, the money behind it is a balance the account holder owns at the card issuer, and the agent tops that balance up in USDC when a renewal is coming. Creating a card is free and a top-up costs exactly the amount loaded.

Three setup steps belong to the human, once per account: completing identity verification, entering the one-time code that links the card issuer, and accepting the issuer’s terms in the dashboard. The agent can report where each stands and hand over the right link. After that the agent runs the rest.

# 1. Check the one-time setup. status is not_started, code_sent, linked, or kyc_required
curl "https://laso.finance/get-card-issuer-status" \
  -H "Authorization: Bearer $LASO_ID_TOKEN"
# { "status": "linked", ... }  If kyc_required, send kyc_url to your human

# 2. Load $60 onto the card balance from the managed wallet (three months of a $20 plan)
curl https://laso.finance/agentX402Pay \
  -H "Authorization: Bearer $LASO_ID_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":{"userId":"usr_...","route":"fund-card-balance","params":{"amount":60}}}'
# The route answers with a top_up_id, status "paid", and funded_usd

# 3. Create a card that stays open across charges
curl -X POST "https://laso.finance/create-reloadable-card" \
  -H "Authorization: Bearer $LASO_ID_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"usd_amount": 60}'
# { "card": { "card_id": "...", "last4": "...", "expiry": "...", "status": "open",
#   "balance": 60, "spend_limit": 60, "reusable": true } }

# 4. Read the number, expiry, CVV, and billing address to enter at the merchant
curl "https://laso.finance/get-card-data?card_id=$CARD_ID" \
  -H "Authorization: Bearer $LASO_ID_TOKEN"

A 402 from step 3 means the top-up has not reached the balance yet. It usually lands in under a minute, and GET /list-card-transactions shows the top-up moving to credited. Enter the returned billing_address at the merchant exactly as given, because it is checked at checkout.

Before each renewal

# Read the open reloadable cards and their balances
curl "https://laso.finance/get-card-data?card_type=Reloadable" \
  -H "Authorization: Bearer $LASO_ID_TOKEN"
# Each card carries card_id, last4, expiry, balance, spend_limit, reusable, and status

# See what the subscription charged
curl "https://laso.finance/list-card-transactions?card_id=$CARD_ID" \
  -H "Authorization: Bearer $LASO_ID_TOKEN"
# Each row carries merchant, amount, status, and created_at

There are no partial approvals, so a renewal larger than the balance is declined in full. Have the agent read balance a few days before the billing date and top up with GET /fund-card-balance if it is short. The tradeoffs are real: the holder must complete identity verification before the first card, the card has no merchant lock or calendar-month limit, and the control is the balance you choose to load. The exact fields are in the reloadable card guide.

When you do not need a subscription at all

Some APIs sell access per request over x402, so the agent pays a few cents in USDC for each call and nothing renews. If the service you want offers that, it is simpler than any card. See how an AI agent can pay for an API call with USDC.

How to choose

If your company already runs on Ramp or Meow, issue the agent a card there and set the cap to the plan’s price. If you have a Privacy account on a paid plan, a merchant-locked card with a monthly limit is the closest match to a subscription. If the agent’s money is USDC and it should keep the card funded on its own, use a Laso reloadable card. For a one-time purchase of a known total, a fixed-balance prepaid card is simpler than any of these. To be told when a charge lands, see how to get notified when your AI agent spends money.

Sources

• Privacy, Privacy API for agentic workflows
• Ramp, Virtual cards for AI agents
• Meow, Corporate cards for AI agents

Frequently asked questions

Why did my AI agent’s card get declined on the second month of a subscription?

The card was either closed after its first charge or loaded with only one month of spend. Use a reusable card and keep its balance or monthly limit above the renewal amount.

How do I let my AI agent pay for its own API credits or hosting bill?

Providers that keep a card on file and bill after use need a card that stays open. On Laso, POST /create-reloadable-card creates one, and GET /fund-card-balance tops up the balance in USDC as bills arrive.

How can my AI agent pay for ads on an ad platform?

Ad platforms charge the saved card repeatedly as spend accrues, so give the agent a reusable card with a limit you control. A fixed-balance prepaid card is declined once its balance is used.

How do I top up my AI agent’s card when it runs low?

With a Laso reloadable card, the agent calls GET /fund-card-balance with an amount from $5 to $10,000 and pays in USDC from Solana or Base. The same amount lands on the card balance.

How do I stop a subscription from charging my agent more than I expect?

Set the limit on the card and keep it close to the plan’s price. A monthly limit or a small loaded balance declines a charge above it, and a declined renewal is the signal to review the plan.

More guides

• How to give your AI agent a credit card — An AI agent cannot pass credit underwriting, but it can issue itself a virtual prepaid card over an API in about a minute. The working pattern, with real requests: x402 payment in, card number out.
• x402 vs AP2 vs ACP vs MPP vs UCP: which should your agent use? — All five agent payment protocols compared honestly: x402 and MPP for machine-to-machine HTTP payments, ACP for ChatGPT checkout, UCP for Google surfaces, AP2 for authorization. Which layer each one is, when to use each, and a worked x402 example.
• x402 vs Stripe Issuing for AI agents — Two real ways to put a card in an AI agent’s hands: Stripe Issuing behind a business account, or x402 card issuance the agent drives itself. An honest comparison of onboarding, funding, controls, and when each wins.
• Issue a virtual card with one x402 call — A complete, runnable walkthrough: pay one x402 request in USDC and receive a virtual prepaid card with number, expiry, and CVV. Real endpoints, real response shapes, error handling included.
• How can an AI agent pay for an API call with USDC? — An AI agent pays for an API call with USDC by answering the API’s HTTP 402 challenge with a signed payment. Two ways to do it: your own wallet with an x402 client, or a managed wallet with a price cap and no private key.
• How do I give an AI agent a bank account? — Two real ways to give an AI agent bank details: a business checking account it can operate (Meow) or a U.S. bank account that converts incoming dollars to USDC in the agent’s wallet (Laso). What each one is, who approves what, and when to pick which.
• How do I cap how much my AI agent can spend? — Cap an AI agent’s spending with limits it cannot raise: a funded balance, a per-payment spend limit set by the account owner, a per-call price cap, and prepaid cards loaded with exactly the amount to spend.
• How do I send money to someone’s debit card from code? — Send USD, EUR, or GBP to a debit card with one API call paid in USDC. No payment processor account: you get a redemption link, the cardholder enters their own card details, and the funds are pushed to the card.
• What are the best ways to pay someone on Venmo or PayPal from an AI agent? — Four ways an AI agent can pay a person on Venmo or PayPal: the PayPal Payouts API, a USDC-paid payout through Laso, a bank or card payout instead, or a human approving each payment. Tradeoffs for each.
• How do I let my AI agent buy a gift card through an API? — An AI agent buys a gift card with two calls: search the catalog for a laso_server_id, then order it with a USDC payment. The redemption code comes back in the same response. Includes a runnable example and the currency gotcha.
• How do I let my AI agent buy something online? — Two working ways for an AI agent to buy something online: spend the account holder’s saved card with their approval on each order, or pay for a prepaid card in USDC and check out like any cardholder. How Laso and Crossmint each handle it, with runnable calls.
• How do I send dollars to a bank account from an AI agent? — Pay a U.S. bank account by ACH from an AI agent. Register the recipient once, then make one API call paid in USDC. Limits, fees, settlement time, and a runnable example.
• What are the best ways to give an AI agent its own wallet? — Four ways to give an AI agent a wallet it can spend from: a key you hold yourself, Coinbase Agentic Wallet, Crossmint agent wallets, or a Laso managed wallet. Custody, spend limits, and tradeoffs for each.
• How do I get notified when my AI agent spends money? — Get an alert every time your AI agent spends: register one signed webhook for card orders, payouts, withdrawals and deposits, or poll the balance and card transaction endpoints. Working code included.
• How do I convert USDC to fiat in my app without a multi-week integration? — Three ways to turn USDC into dollars, euros, or pounds from code: Laso pay-per-call payouts over x402, a Stripe stablecoin balance, or Circle Mint redemption. Onboarding, outputs, and tradeoffs for each.
• How do I let my AI agent use my own credit card safely? — Let an AI agent pay with your own card without ever handling the number: save the card once behind a passkey, let the agent build the cart over an API, and approve each order on your own device. Working calls included.
• All agent guides, or how Laso compares to the alternatives