菜单
Set up, verify, and clean up Stripe test data end to end. Use when creating test customers, products, or subscriptions and you want a repeatable setup-then-teardown workflow, or when you need to remove leftover test customers and products with delete_stripe_test_customers, archive_stripe_test_products, and delete_stripe_test_products.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Verify Stripe subscription billing cycles using a test clock. Use when you need to simulate time passing to trigger subscription renewals, recurring invoices, or to confirm that the next billing date generates the expected charge in Stripe test mode.
Stripe CLI の `stripe fixtures` コマンドで実行可能な fixture JSON を、対話的に整理しながら生成・検証する。test_clock を使った時間進行、サブスクのライフサイクル、失敗カードでの payment_intent 失敗、Connect 配下の Destination charge、bulk 件数のテスト顧客作成など、複数ステップの API リクエスト連鎖を扱う。「Stripe の fixture を書いて」「fixtures.json を作って」「このシナリオを fixture 化」「テストデータを大量に作りたい」「サブスクの月次失敗をテストしたい」「stripe trigger と fixture どっち使う」のような依頼で起動する。"fixture" という単語が無くても、複数ステップの Stripe テストデータ準備、 test clock を使った時間進行、 bulk なテスト顧客作成、 失敗パターンの再現といった意図が見えたら起動する。単発 API 呼び出しが目的なら起動せずに `stripe trigger` か API 1コールを案内する。
Reference for Stripe test clock constraints and pitfalls. Use when planning or debugging test-clock workflows, when an advance or customer-attach step fails, or to check rules before building a time-simulation scenario with create_stripe_test_clock, advance_stripe_test_clock, and create_stripe_test_customers.
基于 SOC 职业分类
| name | stripe-test-data-lifecycle |
| description | Set up, verify, and clean up Stripe test data end to end. Use when creating test customers, products, or subscriptions and you want a repeatable setup-then-teardown workflow, or when you need to remove leftover test customers and products with delete_stripe_test_customers, archive_stripe_test_products, and delete_stripe_test_products. |
A round-trip workflow for Stripe test data: set up, verify, then clean up so the test account stays tidy. Test mode only (live keys are rejected).
create_stripe_test_customers
number (default 1), and optional name, email, description,
payment_method_id, test_clock.metadata.generator = stripe-testing-tools-mcp. The MCP server has no tool
to list or search customers by metadata, so record the ids returned at
creation for later cleanup. The tag is still useful for finding leftovers
in the Stripe Dashboard or Stripe CLI.test_clock, keep number at most 3 (see
stripe-test-clock-constraints).create_stripe_test_subscription
customer, items ([{ price, quantity }]), optional
proration_behavior, payment_method_id.stripe-billing-cycle-test).Tear down dependents before their dependencies to avoid leftover references:
delete_stripe_test_customers
customer_ids: array of ids to delete. You must use the ids collected at
creation — the MCP cannot search customers by generator metadata. To
recover lost ids, look them up in the Stripe Dashboard or CLI.archive_stripe_test_products
product_ids and/or urls. Archiving sets active: false and is
non-destructive (recoverable). Prefer this when a product may still be
referenced or you want a soft cleanup.delete_stripe_test_products
product_ids and/or urls. Permanent and irreversible. Stripe only lets
you delete a product with no active prices/usage; if deletion fails,
archive instead. Confirm the exact deletability rules against the Stripe
docs when in doubt.product_ids or urls (the URL
form looks products up by their url field).