How to Create Stripe Sandbox Account & Test Account Easily 2026

Go to stripe.com and click through to sign in. If you've never used Stripe before, don't hunt for a separate registration page — the sign-in screen itself offers passkey and SSO options up top, and beneath them a plain link reading "New to Stripe? Create account." That link is your entry point into the whole setup.

The signup form asks for your country before anything else, since Stripe's available features and payout rules vary by region. Get this right the first time: once the account is activated — meaning it's processed a live charge, shares a legal entity with another account, or has an Atlas application submitted — Stripe locks the country permanently, and its own support documentation says the only fix at that point is opening a new account.

From there you can either fill in an email and password directly or use the "Sign up with Google" shortcut. Either path creates a free account with no payment details required up front.

Stripe sends a verification email immediately after signup, and clicking it activates the account. You'll also be prompted for business details like a legal entity name and bank account — none of that is required to start testing, so it's fine to dismiss or defer those prompts until you're actually ready to accept real payments. Everything covered in the rest of this guide works on an account that hasn't finished business verification.

Once you're in, the dashboard makes it obvious you're not touching real money: a banner across the top reads "You're testing in a sandbox. Changes you make here don't affect your live account." The left-hand menu is the same one you'll use in production — Payments, Billing, Reporting, and a More section holding Connect, Identity, Atlas, Issuing, and other add-on products — so anything you learn to navigate here transfers directly once you go live.

A Setup guide panel sits in the corner, walking through Set up payments, Verify your business, and Go live as sequential checklist sections. One limit worth knowing early: an account can hold up to five sandboxes total, so if you're setting one up per teammate rather than sharing a single sandbox, that cap will eventually matter.

Under Developers in the dashboard, Stripe issues a separate pair of publishable and secret keys specifically for the sandbox environment — these are the keys your code should use while building. They start with pk_test_ and sk_test_ prefixes, which makes it hard to accidentally wire a test key into a production deploy. Keep them out of version control the same way you would live keys, even though no real charges can happen with them.

Add a product under Product catalog exactly as you would for a real item, then charge it with one of Stripe's published test card numbers. 4242 4242 4242 4242 simulates a clean successful charge with any future expiry date and any 3-digit CVC; other numbers simulate a decline, insufficient funds, or a card that forces 3D Secure authentication, so you can confirm your checkout handles each case before a real customer hits it. A handful of common ones are in the table below — Stripe's testing documentation has the full set, including brand-specific and dispute scenarios. Any transaction here shows up in the sandbox's own Gross volume chart, separate from live figures.

The same Setup guide panel that tracked your sandbox progress has a Go live section — that's where you complete business verification and switch your main account over to accepting real payments. Nothing you built in the sandbox needs to be redone; the same product catalog structure and integration code carry over, you're just pointing your app at live keys instead of test ones once this final section is checked off. The sandbox itself doesn't merge into the live account or disappear — it stays available afterward as your ongoing test environment.