QA Testing and go live checks
The resources below give a high-level overview and best practices when testing Stripe while you’re working on your integration and before you go live.
Make sure your QA team has current information about your Stripe integration, and set clear guidelines on expected behavior for your user stories.
Some merchants use analytics services (for example, Google Analytics) to identify all of the customer behavior for their business. For example, there may be several ways to arrive at your checkout page, each of which requires testing.
After reviewing this material you’ll be able to:
- Verify your OAuth flow handles successes and failures as expected.
- Understand how to respond to charges, refunds, and chargebacks.
- Set up webhooks to manage notifications on important events.
- Apply Stripe’s best-practices to your integration before launching.
To best use the material below, first watch the QA testing video and read the accompanying documentation. Then you can learn more about events and webhooks, and go live checks.
After learning about these topics, you can download a list of associated action items in CSV format below.
QA testing
Review the links below to learn more about the topics covered in this video series. Use the Stripe testing docs and the Stripe Postman collection to achieve specific outcomes in your test payment flows.
Go live checks
After reviewing this guide, you’re ready to activate and configure your account.
Start by going through the general checklists before proceeding with follow action items:
Complete the following tasks prior to launch:
- Validate your profit on each transaction and confirm that you’re satisfied with the margins.
- Add language to your site to help your customers understand what Stripe is, and when to contact your support or Stripe.
- Ensure your support team knows how and when to redirect your customers to Stripe Support.
- Verify that team members have been added to your account with correct roles.
- Confirm the account information is correct, including bank information, company profile, default statement descriptor, and customer service phone number.
- Confirm that your manual or automatic payout schedule is correct.
- Provide any required verification information for the owner and business.
- Set up two-step authentication (recommended for all Dashboard users).
- Ensure all payment methods that you’re supporting have been activated and configured.
- Confirm that you understand the legal contract your business agrees to when you become a platform.
- Confirm that your Radar rules are correct and enabled.
See QA testing use cases and Postman collection for additional resources to test your integration.
Next Steps
Next, take the information you have learned and apply it to your integration design using the Integration Plan guide.