How to Set Up a Stripe Account Test Mode Easily 2026

Head to stripe.com and start the signup form. You'll enter an email, your full name, a password, and your country.

Stripe uses the country to determine which payment methods and payout currencies are available later, so pick the one your business operates in, not wherever you happen to be sitting when you sign up. You can also sign up with a Google account instead of typing a password. Once submitted, Stripe creates your account and drops you straight into the dashboard.

New Stripe accounts open into a sandbox by default. A dark banner across the top of the dashboard confirms it: "You're testing in a sandbox, your place to experiment with Stripe functionality." Creating products, running payments, and making API calls here stays fully separated from your live account, so you can build and break things while your integration is still in progress with zero risk of an accidental real charge.

The sandbox uses the same layout as your live dashboard: Home, Balances, Transactions, Customers, and Product catalog down the left side, with Payments, Billing, and Reporting grouped underneath. Your Overview panel shows zeroed-out gross and net volume until you start running test transactions, which is expected. It's a blank environment built for you to fill with fake activity.

Stripe's own documentation is specific about this: the default sandbox you land in is what it calls your "test mode sandbox", the direct successor to the old single Test Mode toggle. But it's no longer the only option.

From the account picker in the dashboard, a Sandboxes menu lets you create general sandboxes, isolated environments you can spin up separately for local development, CI, or handing to an outside contractor, up to five per account, each with its own data and its own API keys. Stripe's guidance for new integrations is to use a general sandbox rather than the legacy test mode sandbox. Keep using the test mode sandbox mainly if an existing integration already depends on it, or if a feature you need doesn't yet support general sandboxes.

API keys live under Developers in the dashboard menu, scoped to whichever sandbox you currently have open. Test secret keys start with sk_test_ and test publishable keys with pk_test_, so it's obvious at a glance which environment a key belongs to.

A key copied from one sandbox won't authenticate against another, including the legacy test mode sandbox, since each is a separate environment. Use these keys anywhere your checkout or backend code needs to talk to Stripe during development, and never mix a live key into a test integration or the other way round.

Stripe publishes a standard set of test card numbers that only work with test keys, and they're what you use to exercise your checkout flow. 4242 4242 4242 4242 simulates a successful payment with any future expiry date and any three-digit CVC. Other published numbers trigger specific failures, so you can confirm your checkout handles a decline as well as it handles success.

Run several of these through your integration before calling it done. A checkout that only works when everything goes right isn't ready for real customers.

Once your integration behaves correctly against test cards, move to live mode from the same account using the toggle in the dashboard, which swaps you out of sandbox testing and into real payment processing. At that point you need your live API keys instead of the test ones.

Live and sandbox data stay completely separate, so none of your test transactions or fake customers carry over. Before flipping the switch, connect a bank account for payouts; that's required to actually receive money from live payments.