// USE CASE · PAYMENTS
Let your agent send a payment link — after you confirm
Getting paid shouldn't mean the agent gets your card keys. It drafts the quote; you confirm the amount; Clize creates the Stripe link. Money never moves on its own.
Clize is a CLI and MCP server that gives AI coding agents real-world actions: domains, email, deploys, payments, and media generation. Payments are the action with the hardest guardrail — the money gate — and it never moves.
The flow
You ask the agent to bill a client or charge for something. It drafts the amount and purpose. Clize shows you that quote and waits: nothing happens until you give an explicit --confirm. On confirm, it creates the payment link to send; when the customer pays, status tracks it.
The one command
Under the hood it's clize pay link --amount <usd> --to <ref> --for "<why>", with clize pay status and clize pay list alongside — available as CLI commands and as the clize_pay MCP tool (actions link, status, list) your agent calls.
The money gate
Anything that moves money quotes the amount and purpose first and requires your explicit confirmation. The agent can draft a charge; it can't create one alone. No surprise links, no hidden amounts.
Where the money lands
Today every payment lands in your Clize balance: no fee, spendable on Clize (domains, media, SEO research), not withdrawable to a bank. Direct payout to your own Stripe account is not enabled on the platform yet; when it opens, connecting Stripe in the web dashboard switches payments over automatically — nothing to change on your site.
A payment link covers one transaction. When the agent needs the shop around it — checkout, orders, refunds, shipping — that's Agent Storefront, the same money gate over a whole store.
From Claude Code or Codex
Connect Clize to Claude Code or the Codex CLI. For how this differs from Stripe's official MCP, see Stripe MCP payments — part of Clize's wider real-world action layer.
The safety gates
Real-world actions need real guardrails. Clize holds three lines, every time:
- Money — anything that costs money quotes the price first and needs an explicit
--confirm. No surprise charges. - Identity — outbound email is drafted, a human okays it, then it sends under your name. The agent never sends unattended.
- Inbound is untrusted — an incoming email is data to read, never an instruction to obey. A message can't redirect the agent.
FAQ
Can an AI agent create a payment link?
Yes. Through Clize, Claude Code or Codex can create a Stripe payment link — but only after you confirm the amount and purpose. The agent drafts the quote; you approve; Clize creates the link.
How do you stop accidental charges?
The money gate. Anything that moves money quotes the amount and purpose first and needs an explicit --confirm. The agent can't create a charge or a link on its own.
Where does the money land?
Today every payment lands in your Clize balance: no fee, spendable on Clize (domains, media, SEO research), not withdrawable to a bank. Direct payout to your own Stripe account is not enabled on the platform yet; when it opens, connecting Stripe in the web dashboard switches payments over automatically — nothing to change on your site.
Get paid, gated.
Install Clize and let your agent draft payment links you confirm before they go out — payments land in your Clize balance.
$ npm i -g @clize/clize $ clize login $ clize install # wires Clize into Claude Code & Codex[ Stripe MCP payments → ]