Payments
Stripe
Payments and billing infrastructure for cards, checkout, and subscriptions. You are typically the merchant.
Pricing as seen
See site. Card fees vary by country and product, so this entry does not quote a rate.
Checked 16 Oct 2026. Prices change. Confirm on the vendor site before you buy.
Pricing sourceUpdated
16 Oct 2026
Added
16 Oct 2026
Supported builders
Any of these builders can send a user to Stripe Checkout if the secret key stays on a server or a serverless function. A client-only integration that confirms payment in the browser is not enough.
What it is
Stripe’s site describes financial infrastructure for taking payments and running billing models, online and in person, with APIs, a dashboard, and prebuilt Checkout. For a small AI-built app this usually means Checkout or Billing, plus webhooks.
You are generally the merchant of record. Tax, disputes, and the secret API key are yours. The publishable key may be in the browser. The secret key and the webhook signing secret must not be. A success URL is not proof of payment.
Best for: An app that charges cards or subscriptions and has somewhere to put a secret key that is not the frontend.
Watch-outs
- You remain responsible for tax and disputes unless you add a separate merchant-of-record product.
- Test mode and live mode keys are different. Shipping a live secret to the client is a serious incident.
Our take
Opinion from ShipSafeStack. Not a score, not a certification, and not a sponsorship.
The default when you want cards and subscriptions and you can handle being the merchant. The bug in generated apps is almost always the same: the UI says paid because the redirect happened. Verify the webhook signature on the raw body, on the server.