Development checklist
Become a Stripe Partner to access additional best practices and receive relevant news and updates from Stripe.
Stripe has designed its live and test modes to function as similarly as possible. Flipping the switch is mostly a matter of swapping your API keys.
If you are a developer, or had a developer perform an integration for you, you should also consider the following items before going live. If you’re using Stripe through a connected website or a plug-in, most won’t apply.
All requests use your account API settings, unless you override the API version. The changelog lists every available version. Note that by default webhook events are structured according to your account API version, unless you set an API version during endpoint creation.
If you’re using a strongly typed language (Go, Java, TypeScript, .NET), the server-side library pins the API version based on the library version being used. If you’re not familiar with how Stripe manages versioning, please see the versioning docs.
To make sure everything is in sync:
- Upgrade to the latest API version in your Stripe Dashboard
- For dynamic languages (Node.js, PHP, Python, Ruby): set the API version in the server-side library
- For strongly typed languages (Go, Java, TypeScript, .NET): upgrade to the latest version of your chosen library
We’ve created several test values you can use to replicate various states and responses. Beyond these options, perform your due diligence, testing your integration with:
- Incomplete data
- Invalid data
- Duplicate data (for example, retry the same request to see what happens) We also recommend you have someone else test your integration, especially if that other person isn’t a developer themselves.
Once you’ve gone live is an unfortunate time to discover you’ve not properly written your code to handle every possible error type, including those that should “never” happen. Be certain your code is defensive, handling not just the common errors, but all possibilities.
When testing your error handling, pay close attention to what information is shown to your users. A card being declined (that is, a
card_error) is a different concern than an error on your backend (for example, aninvalid_request_error).Stripe logs every request made with your API keys, with these records being viewable in the Dashboard. We recommend that you log all important data on your end, too, despite the apparent redundancy. Your own logs will be a life-saver if your server has a problem contacting Stripe or there’s an issue with your API keys—both cases would prevent us from logging your request.
Regularly examine your logs to ensure they’re storing only the information you need and not anything of a sensitive nature (for example, credit card details or personally identifiable information).
Stripe objects created in test mode—such as plans, coupons, products, and SKUs—are not usable in live mode. This prevents your test data from being inadvertently used in your production code. When recreating necessary objects in live mode, be certain to use the same ID values (for example, the same plan ID, not the same name) to guarantee your code will continue to work without issue.
Your Stripe account can have both test and live webhook endpoints. If you’re using webhooks, make sure you’ve defined live endpoints in your Stripe account. Then confirm that the live endpoint functions exactly the same as your test endpoint.
While examining your webhooks status, also take a moment to check that your production endpoint:
- Gracefully handles delayed webhook notifications
- Gracefully handles duplicate webhook notifications
- Does not require event notifications to occur in a specific order
We recommend all developers subscribe to our API updates mailing list to keep up with new features as we release them.
As a security measure, we recommend rolling your API keys on a regular basis, and also just before going live. This is in case they have been saved somewhere outside of your codebase during development. Make sure your workflow doesn’t result in your API keys being represented or stored in multiple places—this leads to bugs—or even ending up in your version control software.