Skip to content

docs: document Stripe account sandbox distinction #569

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mjaskolski wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: document Stripe account sandbox distinction #569

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions agent-workspace/domain-skills/stripe/account-sandboxes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Stripe account Test mode and sandboxes

Stripe's new-account onboarding can expose two distinct test environments:

- The account's classic Test mode keeps the main account ID and uses URLs shaped
like `https://dashboard.stripe.com/{account_id}/test/...`.
- Choosing **Go to sandbox** during onboarding can create an additional sandbox
with its own account ID and API keys.

Do not assume that the environment opened by the onboarding flow is the main
account's Test mode. Before creating products, prices, or webhooks:

1. Read the account ID from the URL.
2. Open `/{main_account_id}/test/apikeys`.
3. Verify the API key by retrieving `/v1/account` and comparing its `id` with
the intended main account ID.

@cubic-dev-ai cubic-dev-ai Bot Jul 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: Step 3's /v1/account path is ambiguous about how to retrieve it — the document doesn't specify whether the agent should navigate to it in the Stripe dashboard (https://dashboard.stripe.com/v1/account) or make an HTTP request to the REST API (https://api.stripe.com/v1/account with an Authorization header). In a browser-automation harness context, these are distinct operations with different syntax, and the agent has no way to infer which is intended. Specify the full URL and retrieval method so the verification step is actionable.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At agent-workspace/domain-skills/stripe/account-sandboxes.md, line 16:

<comment>Step 3's `/v1/account` path is ambiguous about how to retrieve it — the document doesn't specify whether the agent should navigate to it in the Stripe dashboard (`https://dashboard.stripe.com/v1/account`) or make an HTTP request to the REST API (`https://api.stripe.com/v1/account` with an `Authorization` header). In a browser-automation harness context, these are distinct operations with different syntax, and the agent has no way to infer which is intended. Specify the full URL and retrieval method so the verification step is actionable.</comment>

<file context>
@@ -0,0 +1,28 @@
+1. Read the account ID from the URL.
+2. Open `/{main_account_id}/test/apikeys`.
+3. Verify the API key by retrieving `/v1/account` and comparing its `id` with
+   the intended main account ID.
+
+Useful stable routes:
</file context>
Fix with cubic


Useful stable routes:

- `/{account_id}/test/apikeys` — Test mode API keys
- `/{account_id}/test/settings/account` — account display name
- `/{account_id}/test/settings/payment_methods` — payment method configuration
- `/{account_id}/test/settings/tax` — Stripe Tax settings

The initial **Business name** onboarding field can replace the display name
shown in the account switcher. Restore a product-specific display name under
**Settings → Business → Account details** if the legal name makes sibling
product accounts indistinguishable.