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 to you later, so pick the one your business actually operates in rather than where you happen to be sitting.

You can also sign up with a Google account if you'd rather skip typing a password. Once submitted, Stripe creates your account and drops you straight into the dashboard.

Every new Stripe account opens into a sandbox by default, which is what used to be called Test Mode. A dark banner across the top of the dashboard makes this unmistakable: "You're testing in a sandbox — your place to experiment with Stripe functionality." Everything you do here — creating products, running payments, generating API calls — is fully separated from your live account. This is intentional: it lets you build and break things freely 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, Reporting, and more grouped under Products below that. The banner changes wording slightly once you're working inside it, reminding you that "changes you make here don't affect your live account." Your Overview panel will show zeroed-out figures for gross volume and net volume until you start running test transactions, which is expected — this is a blank environment built specifically for you to fill with fake activity.

Your API keys live under Developers in the dashboard menu, and while you're inside the sandbox, the keys shown there are your test keys — they're prefixed differently from live keys (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. Use these test keys anywhere your checkout or backend code needs to talk to Stripe during development. Never paste a live key into a test integration or vice versa; mixing them up is the single most common way developers accidentally trigger a real charge while still "just testing."

Stripe publishes a standard set of test card numbers that only work inside sandbox mode, and they're what you use to actually exercise your checkout flow. The number 4242 4242 4242 4242 simulates a successful payment with any future expiry date and any three-digit CVC.

Other published numbers trigger specific failure scenarios — a generic decline, insufficient funds, an expired card — so you can confirm your checkout handles errors gracefully, not just the happy path. Run a handful of these through your integration before you consider 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, you move to live mode from the same account — there's a toggle in the dashboard that swaps you out of the sandbox and into real payment processing, at which point you'll 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, make sure your bank account is connected for payouts, since that's required to actually receive the money live payments bring in.