Skip to content

Stripe accounts and sandboxes

The wrong Stripe key can put a product, payment or webhook in the wrong account. Keep business facts, key files and deployment settings separate.

You are reading the v0.19.2 documentation. Open the current docs.

More formats
Raw Markdown ↗

DetailWhere it belongs
Legal name, address, public contactReusable business profile
API keys for one chosen setupNamed Godmode environment
Expected acct_…, test/live mode, price IDsProject deployment configuration
Webhook signing secretThat endpoint's runtime secret store

Select the account and sandbox#

Stripe accounts can share a legal entity while keeping their products and payments separate. Independently operating projects or businesses need separate accounts. A consultant's clients keep their own accounts. Stripe account guidance

Stripe Sandboxes have separate data and settings. Legacy test mode shares some settings with live. Both use test-prefixed keys; sk_test_ or rk_test_ alone cannot identify the sandbox. Sandbox guidance, API keys

godmode env create acme-test
godmode --env acme-test setup stripe
godmode --env acme-test --context acme help

Select the intended account and sandbox in Stripe before saving its key. A verified business's sandbox still makes test payments. Real payments require its live keys and enabled payment capabilities.

Check the target before changing it#

A local filename is a label. The provider's response establishes where the key works.

The project script should read the authenticated account, compare its ID with the configured account, check test/live mode on resources, and verify the deployment destination before writes. A denied restricted key stops the operation; it does not justify trying a broader key. Prefer restricted keys with the permissions that the task needs. Restricted keys

Organization keys require explicit account routing and an API version on each request. Account keys are simpler for one project. Organization keys

Keep webhook secrets with their endpoints#

Each webhook endpoint has its own signing secret. Test and live endpoints can share a URL and still have different secrets. Stripe CLI forwarding has another secret. Webhook signatures

Use a separate deployment for each account and sandbox. Store its matching endpoint secret there. Verify the raw request signature, expected mode and project ownership before changing membership or order data.

A created endpoint does not prove delivery. Save the endpoint ID, install its secret, then send a signed event and confirm the receiver's result. If secret installation fails, repair that step before declaring the endpoint ready.

Reuse facts and verified resources#

Reuse the business profile across test and live. Copy a key file when you want a snapshot of shared providers. Keep product, price, customer and webhook IDs separate for each Stripe account and environment.

Provisioning should first retrieve saved IDs, validate their ownership and settings, and search all result pages before creating anything. Multiple matches require resolution. Idempotency keys protect retries; they are not a permanent registry. Stripe idempotency

Godmode v0.19.2 · 2026-11-17 · Inspect the source · Get help