#François-connect
1 messages · Page 1 of 1 (latest)
Hey, you're describing Connect which facilitates multi-party payments like this: https://stripe.com/docs/connect
what kind of Connected Account are they in those cases ?
Which cases?
actually, for now, we only have Custom
looks like they have to be standard acccounts
Why must they be standard accounts? For a business requirement?
Do you have a specific question I can help with?
We are working like shopify for now. We use Custom Connect accounts for this.
Some of our users want to handle their own Stripe Account, so we are looking at this. Looking at what you say, we have to use Connect, but Connect have 3 differents accounts type
what type should we use, and is it possible to use it with "destination charge" ?
Some of our users want to handle their own Stripe Account
They'll need to be a standard account then.
and is it possible to use it with "destination charge" ?
You shouldn't use destination charges with standard accounts.
This doc breaks down the type of connected account payments and their appropriate usage: https://stripe.com/docs/connect/charges
If you're using standard accounts, you'll want direct charges: https://stripe.com/docs/connect/direct-charges
I thought you wanted to shutdown direct charge integration
Nope. What gave you that impression?
multiple emails with Europe CEO
Thank you, I have all what I need to start working !
Are you confusing working directly with the Charges API?
That's different to using direct charges with Connect (which uses Payment Intents, not Charges)
I'm talking about direct charge. we've been using it since the beta
we've switched to destination charge a few years ago
We're definitely not deprecating direct charges
ok cool
mmmh sorry, but Standard account, can be an already registred account right ?
because I don't see anything in the documentation to have the workflow to use a button "connect my stripe account"
Yep, you should use the OAuth flow: https://stripe.com/docs/connect/oauth-standard-accounts
we can add customized data the the button to get it back after redirect ?
What specifically?
internal data to get our site id to connect with
depends what you mean but you could store information in cookies and check them when the user returns to your site from the onboarding, or use the state URL query parameter in the OAuth link(https://stripe.com/docs/connect/oauth-reference#get-authorize-request)
to add to what was mentioned above though, we're generally moving away from connecting to existing Stripe accounts. In most cases where you want to facilitate payments for a merchant, you'd use the Standard approach that creates a new account under that merchant's Stripe user, but isolated to your platform. Use cases where you want to connect to an existing Stripe account to do things like analyse their data are more what we call "Extensions" and today use OAuth but will transition to the new Stripe Apps platform.
mmmh ok so I'd better start working on Stripe Apps ? is there any documentation about this ?
well it depends on the use case
the distinction is if you're a platform that facilitates payments for a Stripe account, or an extension that adds features to the account's experience. Extensions have a migration guide here https://stripe.com/docs/stripe-apps/migrate-extension but it's very early days
if you're the former(a platform facilitating payments)(you say you are "like Shopify) then you're not an extension I'd imagine so that doesn't apply
We are an ecommerce application. We just want to be able to drive an external stripe account, so our users can use their own stripe account, instead of our Custom Account integration
but you wouldn't generally use OAuth, the preferred approach is the default one where you create an account for them
We just want to be able to drive an external stripe account, so our users can use their own stripe account
yeah we don't suggest that any more, you should create new accounts for them instead so they have an account specific to your platform.
https://stripe.com/docs/connect/platform-controls-for-standard-accounts
https://stripe.com/docs/connect/oauth-changes-for-standard-platforms
mmmh so just to be sure, in our case, we don't need a Stripe Apps, and the best thing to do is to use 0Auth to connect external Stripe account, right ?
no in your case the best thing to do is https://stripe.com/docs/connect/standard-accounts
with this options, a merchant can leave our platform and use it's Stripe account the way he want ?
yes, though that wouldn't be a common thing to happen
we have a special price with our platform for card payments. do they will benefit from it ?