setup-saas-payments

A reusable Codex skill for integrating, completing, auditing, testing, and promoting Stripe or Creem payments in TypeScript SaaS applications.

It is designed for Next.js, TanStack Start, Node.js, and Cloudflare projects. The workflow starts in sandbox, preserves existing payment abstractions, automates safe steps, pauses at actions that require account-owner input, and resumes from a non-secret progress file.

What it covers

• Stripe and Creem support with one active checkout provider per environment
• Subscriptions and one-time payments
• Hosted checkout and customer portals
• Provider-specific webhook verification and normalized lifecycle handling
• Provider-scoped customers, subscriptions, orders, refunds, and disputes
• Server-owned catalog validation and duplicate-subscription protection
• Idempotent and out-of-order webhook processing
• Sandbox verification and guarded live promotion
• Next.js, TanStack Start, Node.js, and Cloudflare implementation guidance

Self-service plan switching is disabled by default until a project explicitly defines upgrade, downgrade, proration, and effective-date semantics.

Install with Codex

Ask Codex:

Install the setup-saas-payments skill from
https://github.com/zhengguge06-code/setup-saas-payments-skill/tree/main/setup-saas-payments

Or run the bundled installer directly.

macOS/Linux:

python ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
  --repo zhengguge06-code/setup-saas-payments-skill \
  --path setup-saas-payments

Windows PowerShell:

python "$env:USERPROFILE\.codex\skills\.system\skill-installer\scripts\install-skill-from-github.py" `
  --repo zhengguge06-code/setup-saas-payments-skill `
  --path setup-saas-payments

The skill is available to Codex on the next turn after installation.

Use

Use $setup-saas-payments to integrate Stripe for this project. Start in sandbox
and continue automatically until the next action that I must complete.

Resume after a manual step:

Continue $setup-saas-payments. Verify the manual action I completed and resume
from the saved integration state.

中文示例：

使用 $setup-saas-payments 为当前项目接入 Stripe，先使用沙盒模式，自动执行到
下一项必须由我完成的操作。

Security model

• Sandbox is the default.
• Live resource creation, live secret synchronization, and deployment require separate explicit confirmations.
• Secrets are read only from process environment, ignored local env files, or deployment-platform secret stores.
• Secret values are never written to the integration progress file or printed by the bundled scripts.
• Stripe and Creem webhook routes remain provider-specific even when checkout traffic switches providers.
• The repository contains examples and variable names only. It contains no API keys, webhook secrets, customer information, or project-specific payment data.

Review generated application changes and provider resources before promoting an integration to production. A hosted checkout page opening is not proof of a complete payment lifecycle.

Repository layout

setup-saas-payments/
  SKILL.md
  agents/
  assets/
  references/
  scripts/

The skill includes deterministic project inspection, state management, Stripe and Creem provisioning, remote verification, reusable TypeScript contracts, database guidance, and self-tests.

License

MIT