#devivo-checkout-connectflow
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- devivo, 56 minutes ago, 14 messages
- devivo-checkout-email, 22 hours ago, 70 messages
@mental forum no but I'm happy to answer any clear follow up questions you have!
it was in re: to nd really you should only be using Direct Charges (creating the Charge directly on the Connected Account) when working with Standard Connected Accounts
what did he mean?
rob — Today at 4:18 PM
I'm working on a b2b platform that converses with a user via SMS using GPT4 API, then once it ascertains the user's order, it generates a custom checkout link for tha price.. so i want to offer it to other businesses, Id LOVE to be able to apply some radar rules for them so they dont have any issues like that
rob — Today at 4:18 PM
Awesome, so express is the way to go for me ..
bismarck — Today at 4:19 PM
Yep
As long as the Charge takes place on your platform then your platform Radar rules will apply
And really you should only be using Direct Charges (creating the Charge directly on the Connected Account) when working with Standard Connected Accounts
You are a platform, you use Standard accounts, so you basically should only ever use the Direct Charges flow: https://stripe.com/docs/connect/destination-charges
Anything else is mostly a big mistake
devivo-checkout-connectflow
But if iu se express accounts
what should i do ?
if im using stripe hosted checkout essions orp ayment intent
If you use Express accounts then use Destination Charges: https://stripe.com/docs/connect/destination-charges
wait im confused sorry
whats the difference in flow
AH i see
so u pass their account ID in there
can u use a destination charge for a checkout session creation call?
Or only for payentIntent
It's a completely different flow of funds, with completely different responsibilities for fees and liability and such.
Make sure to carefully read https://stripe.com/docs/connect/charges
no i understand that
i just meant programattically
If iw anted to use create checkout session call
if i could do it for destimnation, on behalf of their connect account ID
Direct charges
Customers directly transact with your connected account, often unaware of your platform’s existence.
The transaction involves a single user.
An e-commerce platform like Shopify or Squarespace
An accounting platform that enables invoice payments like Freshbooks
But this is what we wanna do, we're more like a shopify platform
We're an ecom based platform
Customers transact with your platform for products or services provided by your connected account.
The transaction involves a single user.
A ride-hailing service like Lyft
A services platform like Thumbtack
Buti guess we're like this too.. damn its tough kinda both
Can you do direct with express?
Really that doc covers it in details and helps you choose! If you have follow up questions the best option is to chat with our support team: https://support.stripe.com/contact
i see the docs but its rather ambiguous about if you can use direct on express
Using direct charges is recommended for Standard accounts. The connected account is responsible for Stripe fees, refunds, and chargebacks. For more information about the different types of Connect charges, see Charge types.
it says recommended but doesn't say if you can use it with express