#godeveloper - connect plugins
exotic summit
hi
acoustic tree
Taking a look at these docs
Okay so in the first doc you are setting yourself up as a platform, creating a Standard Connect Account, and using Direct Charges to allow them to accept payments. So far so good
https://stripe.com/docs/connect/standard-accounts
https://stripe.com/docs/connect/direct-charges
(more details on the account and charge type)
So then you are creating a plugin that your Connect Accounts will be able to use themselves to process payments, is that correct?
exotic summit
Yes
So wanted to ask if this is sthe correct way for the platform to start with stripe?
acoustic tree
You don't necessarily need to develop a plugin. It's just one option. But that is a valid pathway to use Connect.
exotic summit
ok, so wandering why these two docs are not linked together? I had to search for plugins separately and didn't knew what to do after setting up an account
acoustic tree
Because Plugins is a very specific pathway and not the most common
Plugins are used for things like, creating a WordPress plugin that connects an end-user through your platform account to Stripe
Where you manage the API integrations for them
exotic summit
But even after building a plugin I would need to setup a stripe acc and connected accs right to get the transactions flowing?
acoustic tree
Plugins are their own specific use case. In that case your customers would already have Stripe accounts and they would accept you as a platform to provide the service of your plugin.
What is actual business case you are trying to achieve here?
exotic summit
I see. What if my merchants don't have a stripe account?
I want to see how ecommerce platforms have done their integration. What are the actual steps involved.
I saw this in the docs and hence clicked on the shopify eg link since that is my use - similar to shopify, bigcommerce etc
acoustic tree
Okay, I see.
If that is the direction you are going then it makes sense. Taking Shopify as an example, they sign their users up through their application which creates a Stripe account for them. Then Shopify techs manage the actual Stripe API integration and provide a more simplistic set of capabilities to their users.
exotic summit
Got it. So shopify has built the custom stripe plugins ?
And one more question - what's the difference between connectors/plugins and 3rd party plugins for stripe?
clever tiger
Hi 👋 jumping in as my teammate needed to step away. I'm not sure I understand the question, could you try clarifying?
exotic summit
what are the different types of partner integrations does stripe offer?
clever tiger
I wouldn't say we offer them, as they are offerings from our partners, but a list of those can be found here:
https://stripe.com/partners/directory
exotic summit
This is one type of partner integration. What are other types? - direct/custom integration? Direct plugin integration?
clever tiger
I'm sorry, I'm struggling to grasp the question. Could you maybe provide context on why you're asking, that might help me understand what it is you're looking for.
exotic summit
I want to udnerstand what are different ways I as a partner (such as bigcomm, shopify) integrate with stripe - either api integration, plugin, 3rd party?
clever tiger
Gotcha, you can build an API integration, or a Stripe App (which I believe is also API based):
https://stripe.com/docs/stripe-apps
Connectors, plugins, etc, are terms used by partner ecosystems to represent pre-built integrations, from our perspective they're all API integrations.
exotic summit
Ahh ok. So the main type of integration is API integration and then the sub categories under it are 1) custom/direct integration 2) plugin integration 3)3rd part apps integration
Is this the correct understanding? Sorry I am a newbee developer so trying to understand the integration types.
clever tiger
To Stripe, they're all API-integrations, we're not terribly familiar with what other parties decide to call their pre-built integrations.
We have two concepts for these type of integrations:
Stripe Apps (previous version of this was called Extensions):
https://stripe.com/docs/building-extensions
These are usually partners trying to add additional functionality for Stripe users
The other is using Stripe Connect to create Platform accounts that can process payments for their Connected Accounts:
https://stripe.com/connect
This approach is typically used for marketplaces or other platform-like services
exotic summit
ok. Is extensions same as connectors? The link for extensions say deprecated?
Also, if I am platform similar to shopify, bigcommerce what are the high level steps for me to get started? Sorry but the docs are really confusing and not straightforward
clever tiger
Is extensions same as connectors?
From our perspective, they are extensions. The term "connector" is not universal. For example, CRMs like Magento and NetSuite have connectors, but Salesforce has plugins.
The link for extensions say deprecated?
Yes, extensions are being sunset in favor of Stripe Apps
Also, if I am platform similar to shopify, bigcommerce what are the high level steps for me to get started? Sorry but the docs are really confusing and not straightforward
This is pretty broad and hard for us to provide technical guidance on. You first need to figure out what your goals are, and then map what Connect-friendly functionality we have that can do that.
exotic summit
ok here is my use case. I am a developer at a new commerce platform(e.g., bigcomm, shopify) and want to make stripe as a payment available on my platform for my merchants to start using stripe for payment transactions. Want to know how do I get started? Is it clear now
clever tiger
Alright, so that is going to be a Connect scenario. Since it sounds like you'd be building your own frontend for this, I'm assuming you're not interested in low/no-code approaches.
You'll need to start by picking the type of Connected Account and Charges that is right for your scenario:
https://stripe.com/docs/connect/accounts
https://stripe.com/docs/connect/charges
exotic summit
ok and what's next step after picking and creating connected acc?
clever tiger
The overall flow will be:
- Create a Connected Account
- Onboard that connected account (exactly how fluctuates based on type of account used and the approach you want to use if you use Custom accounts)
- Create/process payments for your Connected Accounts (exact process fluctuates based on charge type and integration path, you could embed our Payment Element into your page, or use Checkout if you'd rather have a hosted experience)
- Have the funds from those payments paid out.
This guide does a good job explaining the overall flow:
https://stripe.com/docs/connect/explore-connect-guide
exotic summit
ok and what about plugin? Do i need to build or use a plugin in this process in step 2 that you mentioned?
clever tiger
No, you work directly with the Stripe APIs. The pre-built integration that you're building may be referred to as a plugin in your landscape/ecosystem/platform.
Or leverage our hosted flows to collect the necessary onboarding information.
exotic summit
ok and is this the same way shopify or bigcomm have integrated with stripe? Via stripe connect APIs?