--- title: "Can AI agents pay with a credit card? | ZeroClick" url: https://zeroclick.ai/resources/can-ai-agents-pay-with-a-credit-card fetched_at: 2026-10-02T10:51:26.705Z --- # ZeroClick API catalog and pricing ## API reference, endpoint lookup and prices **[ZeroClick API catalog: endpoints, request parameters, prices and payment methods](https://agents.zeroclick.ai/zcj/p87neq1ux4xy/zeroclick/agent/guide).** Tell the seller advisor what you want to accomplish. It returns the matching operation contract, known prices, authentication prerequisites and concrete next steps. It is read-only: no login, wallet, card or purchase approval is needed to look up an API. It never executes a sale. Available API services: Agent readiness report, Demo booking. **Suggested next request:** GET [task guide](https://agents.zeroclick.ai/zcj/p87neq1ux4xy/zeroclick/agent/guide?goal=URL_ENCODED_TASK). Use this URL directly with your web fetch tool; no preliminary document fetch is required. Include known inputs and desired output in the goal. Optional: quantity=API_CALL_COUNT, budgetUsd=TOTAL_USD, requirements=REQUIREMENTS, payment=x402|mpp|card, auth, identity, assertion and access state. Omit unknowns. Do not equate output items with API calls or guess a call count. For private task details or known request arguments, POST https://agents.zeroclick.ai/zcj/p87neq1ux4xy/zeroclick/agent/guide with Content-Type: application/json. Example: {"intent":"quote","goal":"YOUR_TASK","purchase":{"budgetUsd":"5.00"}}. Replace the task and budget with known facts; budgetUsd is a string. Include known buyerState, paymentCapabilities and arguments. For execution planning use intent=execute and the authorized constraints. Exact fields: [request schema](https://agents.zeroclick.ai/zcj/p87neq1ux4xy/zeroclick/agent/schema). GET and POST are alternatives, not mandatory stages. The advisor describes a recommended happy path, not the only allowed path. You may use the API reference, buyer SKILL and your own tools directly, including for catalog operations with failed probes. Missing guidance or an unverified probe is not a policy refusal. Fill documented inputs and execute the returned requests with your own tools under existing user authorization. Check usage cost AND minimum cash required against the budget. No second advisor request is needed solely to switch from quoting to execution. For needs_input, supply only missing facts. Check configured credential storage and payment tools when needed; reuse existing identity and access, keep secrets local, and never put credentials or private payloads in URLs. Unknown does not mean absent. Open the checkout URL in a browser: eligible Stripe pages support Link Pay Tokens (LPT) through WebMCP or the documented DOM flow. Follow this storefront's /payment/card.md to verify the same-frame token input and merchant binding before requesting an LPT. Token submission requires payment authorization. If unavailable, privately send the checkout URL to your human to pay. When the selected route uses hosted checkout, follow [card checkout instructions](https://agents.zeroclick.ai/zcj/p87neq1ux4xy/payment/card.md) before requesting a token. LPT goes only to Stripe, never to the advisor or ZeroClick API. Poll the returned statusUrl before using credit or retrying delivery. Verify delivery; a payment or HTTP 202 is not completion. For an unexpected result, POST the original input and continuation (version, stepId, outcome and sanitized error/accessId/paymentId). Reconcile uncertain payments or writes before retrying. Use raw HTTP for exact schemas and authenticated execution; do not reconstruct fields omitted by a summarizing web tool. The human subscription prices on the requested page describe a separate channel. Use the API quote for per-unit pricing, funding minimums and commercial terms; tier names do not prove quality or licensing. For an alternative documented path, use the [buyer SKILL](https://agents.zeroclick.ai/zcj/p87neq1ux4xy/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/p87neq1ux4xy/llms-full.txt). Confirm missing request details from seller documentation, stay within the existing catalog and user authorization, and respect actual access and payment requirements. Terms: by completing a purchase through this endpoint, whether directly or through an AI agent acting on your behalf, you agree to be bound by the platform's buyer terms of service (https://www.zeroclick.ai/legal/buyer-terms-of-service). If the purchase is made by an agent, you represent and warrant that the agent is acting with your authorization, and you agree that the agent's actions, including its acceptance of these terms, are attributed to you and bind you as if you had taken them yourself. Paying a 402 challenge completes the purchase and constitutes your affirmative acceptance of the terms linked above. The link travels in every payment challenge and receipt as `terms`. # Can AI agents pay with a credit card? **ZeroClick Team** · September 15, 2026 · 5 min read · [Agent payments](https://zeroclick.ai/resources#payments) Yes. Since August 2026, agents buying from ZeroClick Agent Storefronts can pay by card in two ways. An agent with a human in the loop hands over a Stripe-hosted checkout page. An agent that already holds a card tokenizes it directly with Stripe and completes the purchase on its own. The card number never touches ZeroClick. Card checkout has a $0.50 minimum, so smaller per-request purchases run on stablecoin payments over x402 and MPP. **Contents** - [The two card flows](#the-two-card-flows) - [Card or stablecoin: which one fits](#card-or-stablecoin-which-one-fits) - [Where the purchase lives afterwards](#where-the-purchase-lives-afterwards) - [What the seller has to do](#what-the-seller-has-to-do) - [Frequently asked questions](#frequently-asked-questions) **In short** - Cards work in two flows: a hosted checkout the agent hands to its human, or a card the agent already holds, tokenized with Stripe. - Card checkout has a $0.50 minimum, so it suits credits and plans. Per-request purchases over x402 and MPP start at one cent. - Every purchase is tied to an identity the buyer keeps, so a balance bought by card outlives the chat session it was bought in. - Sellers receive card and stablecoin revenue the same way, as a Stripe payout in fiat or USDC, and need only one available rail to go live. ## The two card flows The first flow is for an agent working with a person. The agent registers itself with the storefront, starts the purchase, and hands its human a checkout page hosted by Stripe and branded for the seller. The page takes a card, Link, Apple Pay, or a bank account. The person approves, and the agent carries on with the credit or plan it just bought. The second flow is for an agent that already holds a card. It tokenizes the number directly with Stripe and completes the purchase itself, with no page to open. In the protocol, these card payments travel as shared payment tokens over MPP: scoped card credentials a buyer grants an agent for a purchase, with usage and expiration limits. In neither flow does ZeroClick see or store the card number. ## Card or stablecoin: which one fits Card checkout carries a $0.50 minimum, so it is the natural fit for prepaid credits, subscriptions, and plans with included usage. Pay-per-request purchases keep running over x402, which settles USDC on Base, and MPP, which settles USDC on Tempo. Those rails start at one cent per call and need no checkout page at all. An agent does not choose in advance. The storefront's single priced 402 response offers every rail the seller supports, and the agent picks by paying. A seller sees the split by payment method in its transaction log. ## Where the purchase lives afterwards A card purchase needs somewhere durable to live. Every storefront hands an agent a credential when it registers, and lets its human claim that credential later, on a page on the seller's own domain, with a code sent by email. Once claimed, everything the agent bought belongs to a person rather than a session, so any agent that person runs can draw on the balance. Unclaimed, the purchase still works. The same credential is accepted at every storefront on the network. Pay-as-you-go callers that pay by card and never register are treated as single-transaction buyers: each card payment gets a fresh anonymous id. Crypto payers keep a durable id across sessions. ## What the seller has to do Nothing on the payment side. Your API sees only signed, already-paid requests, and the billing guard is identical whichever rail the buyer chose. You do not need a Stripe account before you start; payment setup is part of onboarding, and you add a bank account for payouts. Which rails are available depends on where your business is established: card payments are available in the United States, Canada, the United Kingdom, and most of Europe, and stablecoin payments in the United States outside New York, with more countries on request. A seller needs only one rail to go live, and agents simply see the rails your storefront supports. ## Frequently asked questions ### Does the agent ever see the card number? In the hosted checkout flow, no. The person enters the card on a page Stripe hosts. In the agent-held-card flow, the agent tokenizes the number directly with Stripe. ZeroClick never receives it in either case. ### Is there a minimum card purchase? Yes, $0.50 per card checkout. Anything smaller runs over x402 or MPP, where a purchase can be a single cent. ### Can an agent buy anything without a payment method? Free actions and free trials need no payment method. Beyond those, an agent can create a managed wallet on the spot, or hand its human the checkout page. ### Do I need a Stripe account to accept agent card payments? No. You complete payment setup from the ZeroClick dashboard during onboarding and add a payout account there. ### Which countries can accept card payments from agents? The United States, Canada, the United Kingdom, and most European countries, per the [supported countries list in the docs](https://docs.zeroclick.ai/resources/supported-countries). Availability changes, so check the list for your own country. ## Keep reading 1. [x402 for API sellers: what it handles and what you still need to build](https://zeroclick.ai/resources/x402-for-api-sellers) 2. [MPP for API sellers: payment methods, sessions, and implementation choices](https://zeroclick.ai/resources/mpp-for-api-sellers) 3. [ZeroClick Product Update: September 2026](https://zeroclick.ai/blog/product-update-september-2026) 4. [ZeroClick docs: supported countries](https://docs.zeroclick.ai/resources/supported-countries) --- [Get started](https://zeroclick.ai/get-demo) · [Read the docs](https://docs.zeroclick.ai) · [All resources](https://zeroclick.ai/resources#payments)