Manage sandboxesBeta
Manage and organize your sandboxes in the Dashboard.
Beta
Sandboxes is currently in private beta. Join Stripe Insiders, our new early access program, to register your interest in joining the Sandboxes private beta.
Use the Stripe Dashboard or the Stripe CLI to manage your sandbox.
Create a sandbox![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Any team member with the Sandbox Administrator role, Administrator role, or Developer role can create a new sandbox. Each account can have a maximum of six sandboxes.
To create a sandbox:
- Click Sandboxes > Create New in the Dashboard.
- Enter a unique name that reflects the purpose of the sandbox (for example, “Staging”) in the Name field.
- Decide if you want to adjust the toggle that copies selected settings you already have configured in your live account. Stripe enables this by default.
- Click Create.
Stripe automatically assigns the Super Administrator role to any user that creates a sandbox. This role allows them to carry out all operations within that particular sandbox.
View a sandbox![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Any team member with the Sandbox Administrator role can view all sandboxes. Developers can only view sandboxes they’ve created. All members of your team can continue to access your prior test mode setup in Legacy Test mode.
- Click Sandboxes in the Dashboard, then select one of your most recent sandboxes.
- Click Manage Sandboxes to view the full list of your sandboxes.
- Click Open to enter the sandbox.
The banner at the top of the Dashboard indicates that you’re in a sandbox. You can navigate to any other part of the Dashboard.
View your current sandbox in the CLI![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
To display the sandbox you’re currently using, run the following command:
stripe preview whoami
Default Sandbox {{SANDBOX_ID}}
Update a sandbox![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Any member of your team with the Sandbox Administrator role can update the name and details of any sandbox. Developers can only update the name and details of a sandbox that they’ve created.
- Click Sandboxes in the Dashboard, then select a sandbox.
- Click Settings in the top right corner.
- Update the name or additional details about your sandbox’s business account (for example, the branding).
Delete a sandbox![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Any team member with the Sandbox Administrator role can delete a sandbox. Developers can only delete sandboxes that they’ve created. You can’t delete the Legacy Test mode sandbox, and you must have one other sandbox. Create a new sandbox before attempting to delete the last, non-legacy sandbox.
- Click Sandboxes > Manage Sandboxes in the Dashboard.
- Click the overflow menu (), then Delete Sandbox.
- Confirm that you want to delete this sandbox as this action can’t be undone. After deletion, we remove all data associated with the sandbox and revoke access.
Note
Deleting a sandbox deletes all the data associated with the sandbox and removes access for any other team members who had access to the sandbox.
Switch to a sandbox in the CLI![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
You can switch the sandbox you’re operating on in your CLI. To switch to a different sandbox, run the following command:
stripe preview use
You are currently operating on Default Sandbox ({{SANDBOX_ID}}) * indicates your active workspace. Use the arrow keys to navigate: ↓ ↑ → ← ? Select the sandbox you'd like to use: ▸ * Default Sandbox {{SANDBOX_ID}} QA Team Sandbox {{SANDBOX_ID}} Developer Sandbox {{SANDBOX_ID}}
Next, select the sandbox you want to switch to.
Organize your sandboxes![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Each account can have a maximum of six sandboxes. You can organize your sandboxes to completely isolate changes in one area from changes in another area. Teams and developers can use this isolation to observe changes. Here are a few potential ways to organize your sandboxes:
- Per team member
- Per development team
- For a specific feature
- For a staging environment