Stripe Onboarding Guides Public Beta

Stripe implementations can vary depending on the business sector, company size, and other factors. If you're implementing Stripe, this onboarding documentation helps you make informed decisions so that you can build an integration that’s best for your use case. The onboarding content doesn’t replace our product documentation, but it does complement it by helping you choose the right path.

When you or your developers decide to implement a feature, the onboarding content points you to the appropriate product documentation. After you’ve finished your integration, the product documentation is your best source for new content.

To start the onboarding process, click the product you want to integrate. Payments is often best for users that only need to accept online payments. If you need to pay out to third parties, in addition to accepting payments, use Connect. If you need automated or manual invoicing for one-off or recurring payments, use Billing. If you want to learn more about our products before deciding, see our product overviews for Payments, Connect, and Billing.

Onboarding phases

The onboarding process has up to five phases:

  1. Scoping
  2. Integration
  3. Testing
  4. Training
  5. Go-to-market (GTM)

The scoping phase needs to be completed first, but the rest of the phases can be worked on in parallel. The onboarding content is organized so you have a general path to follow, but it also provides flexibility so you can integrate in a way that’s best for you.


Learn about key onboarding components and start to make integration decisions. Topics like funds flows and managing risk are introduced in this phase.


Start implementing based on the decisions you made in the scoping phase. Engineering and UX teams complete a lot of the work in this phase, but product managers and other nondeveloper teams are involved in making integration decisions.


As work is completed in the integration phase, you can start the testing phase. The workload in this phase is often split among several teams. Engineering teams can test charge flows, product managers can test verification flows, finance teams can verify reports and dashboard information, and so on.


The training phase is mostly for nondevelopers. Customer service, finance, business, and product management teams are usually involved. Much of the training focuses on using the Stripe Dashboard, understanding funds flows, and managing refunds and disputes.


Work on strategies for user adoption and transitioning connected accounts to Stripe. This includes communication strategies that explain Stripe to buyers and sellers, how to prioritize connected accounts, and more. Even though this phase is last, there’s a lot you can work on in the beginning of the onboarding process. Having a strong GTM strategy gives you and your customers a smoother transition to Stripe.

Was this page helpful? Yes No


Thank you for helping improve Stripe's documentation. If you need help or have any questions, please consider contacting support.

On this page