#riptired_api
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1278462566590447667
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- riptired_api, 1 day ago, 5 messages
- riptired_api, 2 days ago, 26 messages
- riptired_api, 2 days ago, 29 messages
- riptired_connect-sct-crossborderpayout, 2 days ago, 27 messages
Hey, clarifying question about onboarding client connected accounts for Stripe Connect. Previously we discussed onboarding a connected account for a cross border payment in which I needed the conencted account to have a recipient service agreement
In the case that i do not need to do a cross border payment but still need to transfer, is there any reason to select that recipient level SA? Or can I just make the connected account onboarding links from the dashboard for connected accounts that are also in the U.S. (the platform is based in the U.S. as well)
If your payment flows are domestic, and you have need of allowing the connect account to create payments, then you wouldn't use a recipient SA.
All the connected account needs is to be able to get transfers of a payment split of a product
the platform handles collecting payment and uses SC&T to pay out the connected accounts for their portion
Then yeah, either SA would work, but it sounds like the recipient SA is better
Do connect account onboarding links created from the dashboard have the same expiry as the ones created via the API?
and I guess in what cases would I need the receipient level SA if its a domestic account that only requires the ability to be transfered to
Yes, as far as I know, but you'd need to test yourself
We don't have a lot of context about dashboard functionality
Got it
As far as the docs go with the SA types it seems like the only thing I am losing is cross border payouts by using the default service agreement
That sounds about right, in a simplified way
I believe the only thing I am omitting is the relationship between the connected account and Stripe correct
where for a recipient there is no relationship but for a full SA, there is a service relationship between Stripe and the SA as well
We don't really have much context on anything but the technical aspects of how the SA affects actions you can perform. I would recommend reaching out to support if you want to know the greater intricacies of service agreements: https://support.stripe.com/contact
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
ok got it