| [ Web Proxy ] |
| Viewing: https://docs.stripe.com/get-started/checklist/go-live | [Back] [Original] |
Become a Stripe Partner to access additional best practices and receive relevant news and updates from Stripe.
As you complete each item and check it off, the state of each checkbox is stored within your browsers cache. You can refer back to this page at any time to see what youve completed so far.
You can log in to see some of your current settings.
Stripe has designed its live and sandbox environments to function as similarly as possible. Switching between them is mostly a matter of swapping your API keys.
If youre a developer (or had a developer perform an integration for you) also consider the following items before going live. If youre using Stripe through a connected website or a plug-in, most wont apply.
All requests use your account API settings, unless you override the API version. The changelog lists every available version. By default, webhook events are structured according to your account API version, unless you set an API version during endpoint creation.
If youre using a strongly typed language (Go, Java, TypeScript, .NET), the server-side library pins the API version based on the library version youre using. If youre not familiar with how Stripe manages versioning, see versioning.
To make sure everything is in sync:
Weve created several test values you can use to replicate various states and responses. Beyond these options, perform your due diligence, testing your integration with:
Dont wait to go live before discovering that you havent properly written your code to handle every possible error type, including those that should never happen. Make sure your code is defensive, handling not just the common errors, but all possibilities.
When testing your error handling, pay close attention to what information you show to your users. A card being declined (that is, a card_error) is a different concern than an error on your back end (for example, an invalid_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 also, despite the apparent redundancy. Your own logs serve as a backup if your server has a problem contacting Stripe or you have an issue with your API keysboth cases would prevent us from logging your request.
Regularly examine your logs to make sure they store 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 a sandbox environmentsuch as plans, coupons, products, and SKUsarent 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 sure to use the same ID values (for example, the same plan ID, not the same name) to guarantee your code continues to work without issue.
Your Stripe account can have both test and live webhook endpoints. If youre using webhooks, make sure youve 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 make sure to check that your production endpoint:
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 rotating your API keys on a regular basis. Before you go live:
| Web Proxy Viewer | New URL | Original Page |