#Kaartik-conenct-standard
wintry marsh
Hi yes, definitely. For context, I've never used Stripe before as a user or a developer.
For my app, I'm looking to integrate Stripe so that users can transfer money between one another. I've been reading about Standard Connect (https://stripe.com/docs/connect/standard-accounts) and Creating Direct charges (https://stripe.com/docs/connect/direct-charges) but I'm unsure how exactly to go about this.
Correct me if I'm wrong, but for every user who I intend to allow to receive money, then I would have to get them to create an account with the create-account endpoint right? But who should call this endpoint? Is it the server side or the client side? Additionally, when should I create a checkout session as opposed to a payment intent? And are these API endpoints called by the client side or server side?
I'm just quite confused by the segregation between server-side and client-side in calling the Stripe APIs in the use case of allowing one user to pay another (a pre-defined amount of money) on my platform.
snow forge
To start, you can't transfer funds between your Connected Accounts, you can only transfer funds from your platform (typically as part of a payment) to your Connected Accounts.
wintry marsh
Okay, I'm looking to make a payment between one user to one connected account!
That's the framework by which I'm looking to operate on 😄
snow forge
When you say user, is that someone making a purchase or starting a subscription from your platform (typically referred to as customers in the Stripe ecosystem)?
wintry marsh
It's someone making a purchase, a one-off transaction
snow forge
Okay.
So yes, everyone that you onboard to receive payments, will need to have a Connected Account created and onboarded.
The request to create the account is made from your backend.
https://stripe.com/docs/connect/standard-accounts#create-account
General rule of thumb when looking at code snippets in our documentation, if you see all of our server-side libraries listed (Ruby, Python, PHP, Java, etc) then the request shown in the snippet is made form the backend. If the snippet is in JS, then it is likely a frontend request.
Checkout Sessions vs Payment Intents depends on the type of end-user experience that you're trying to accomplish. If you want to use a hosted page to collect payment information, then Checkout Sessions are a good option.
If you'd rather embed our Payment Element into your own checkout flow, then you would use Payment Intents.
Either of those would be created with requests from your backend servers.
wintry marsh
This is great. Thank you, Toby. Have a good day ahead
wintry marsh
Hey @heady sleet , may I know what's an Account Link and what is its use case?
heady sleet
The Account Link is used to link an existing Standard Connect account to a platform.
wintry marsh
Ah okay thank you
Hey @gritty echo , sorry I still don't get what an Account Link is? Could you please lay it out for me
Does that mean that when an account is created, I have to go on to link that account to my platform using this API?
gritty echo
👋
No
An Account Link is how you get your user into the onboarding flow.
https://stripe.com/docs/api/account_links/create: Creates an AccountLink object that includes a single-use Stripe URL that the platform can redirect their user to in order to take them through the Connect Onboarding flow.