Blog · 16 November 2026 · 6 minute read
Stripe test mode to live: the checklist before you take real money
Test and live are separate worlds in Stripe: keys, products and webhooks. What to recreate, what to switch and what to test before the first real payment.
Test and live do not share anything
Stripe keeps test data and live data apart. A product, a price, a customer or a webhook created in test mode does not exist in live mode. Keys are different too. Going live is therefore not one switch. It is making sure the live side has everything the test side had, and that your app points at it.
Before you switch: the business side
- Activate the account with your business details and bank account.
- Set the public business name and the statement descriptor customers will see on their card statement.
- Add your support email and website.
- Decide how you handle tax and whether prices include it.
- Publish terms, a privacy policy and a refund policy on your site. Payment providers expect them and so do customers.
Recreate the catalog in live mode
Create the same products and prices in live mode. Note the new price identifiers, because they differ from the test ones. If your app keeps price identifiers in environment variables, this is a small change. If they are written into the code, move them to variables now.
Create the live webhook
Add a webhook endpoint in live mode that points at your real domain, and select the same events you handled in test. The live endpoint has its own signing secret. A wrong or missing signing secret is the most common reason that payments succeed while accounts stay unpaid.
Switch the keys
- Replace the test secret key with the live secret key in the environment variables of your host.
- Replace the publishable key if your frontend uses one.
- Replace the webhook signing secret with the live one.
- Replace the price identifiers.
- Redeploy, and confirm the app reads the new values.
Make one real payment
Buy your own product with a real card. Use a full discount coupon if you would rather not be charged, which still exercises the whole flow. Then check four things: the payment appears in the live dashboard, the webhook delivery shows success, your database marks the account as paid, and the receipt email arrives.
Then refund or cancel it and check that your app reacts to that too.
Give customers a way to manage billing
Turn on the Stripe customer portal so people can update a card, download invoices and cancel a subscription without writing to you. Link to it from the account page.
Keep the keys safe
- Live secret keys belong in the host environment and nowhere else.
- Never paste a live key into a chat, a screenshot or a repository. If it happens, roll the key at once.
- Use restricted keys with only the permissions a tool needs.
Where Shipyard fits
Shipyard creates the Stripe product, prices and webhook in test mode during a launch and stores the keys as variables on your host, so the app is wired correctly from the first deploy. It works with a restricted key if you prefer one, and says which permissions that key needs. Taking real money stays your decision and your action.
Launch in an hour, not a weekend
Shipyard connects your accounts once, then sets up the domain, hosting, database, email and payments for every new product.
See how it works