メニュー
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.
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コールを案内する。
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.
SOC 職業分類に基づく
| name | stripe-test-clock-constraints |
| description | 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. |
Quick reference for the rules and gotchas of Stripe test clocks as exposed by this MCP. Consult this before designing a time-simulation scenario.
create_stripe_test_customers with a
test_clock set rejects number > 3. To exceed 3 customers in one
scenario, use additional clocks.create_stripe_test_customers with
test_clock). There is no way to attach or move an existing customer to a
clock afterward, so create the clock first.advance_stripe_test_clock can only move
frozen_time to a time after the current frozen time. You cannot rewind
a clock; to test an earlier point, create a new clock.advance_stripe_test_clock, the clock
enters an advancing state and processes billing events in the background.
The tool returns the status once in its response, but this MCP server does
not expose a tool to retrieve or re-poll the clock, so you cannot
programmatically watch it reach ready. If the response shows advancing,
wait a few seconds before follow-up operations, or have the user confirm the
clock has settled in the Stripe Dashboard.frozen_time is a Unix timestamp in seconds (epoch seconds), not
milliseconds and not an ISO string.Date.now() in JS) — divide by 1000 and
floor.date -d '2024-02-01T00:00:00Z' +%s).Date.test_clock_id returned at creation; it is required for every
advance.current_period_end.stripe-billing-cycle-test.stripe-test-data-lifecycle.