#sean-trustap_best-practices
clever mountainBOT
👋 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/1217292161972834304
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
analog sleet
hello! are you trying to do crossborder payouts? https://stripe.com/docs/connect/cross-border-payouts
real imp
Hi Alex, sorry I didn't hear your message come in! We're not trying to do cross-border payouts, but from reading about the recipient agreement it seems much more appropriate for our use cases.
analog sleet
maybe can you elaborate a bit more, is it because you don't want to accept charges and only want to be able to transfer funds to the connected accounts that's why you wish to use the recipient agreement?
real imp
Exactly. Particularly with regards to this part:
A recipient service agreement clarifies that there is no service relationship between Stripe and the recipient, and that the recipient’s relationship is with the platform. Connected accounts under the recipient service agreement can’t process payments or request the card_payments capability.
It's beneficial for us that we're a user's point of contact. We don't have a need for users to have the card_payments capability, which we've seen can also lower our initial KYC requirements for new users, allowing for smoother onboarding processes as well. It looks like recipient service agreements only allow transfer capabilities, which are all we ever really want to allow our connect accounts to do anyway.
In short, from a non-technical standpoint the recipient agreement ticks all our boxes, but there seem to be more technical limitations to this that would be great to understand more.
analog sleet
hrm, what's the error you're seeing when you try this?
real imp
The recipient ToS agreement is not supported for platforms in IE creating accounts in US. See https://stripe.com/docs/connect/cross-border-payouts for more details.
It's similar for other platform/country combinations.
analog sleet
i guess the recipient ToS agreement was really only built for crossborder payouts. If you want to restrict the account to only support transfers only, it's still possible but you wouldn't use the recipient agreement. When you create the connected account, try only creating it with only the transfers capability enabled. By default, the information required depends on certain parameters of the account and the capabilities you're requesting for. You can take a look here : https://docs.stripe.com/connect/required-verification-information#US+US+custom+full+individual+transfers
we may need to enable a "feature" on your platform account to allow you to create transfers-only connected accounts though, but you'll need to try it out to see if your platform account is allowed to do so already
real imp
I see, thanks very much for the information. I don't think it's essential for us but it seemed more appropriate so I wanted to scope it out more. Sometimes we're required to request the card_payments capabality for some platform/country combinations, and we don't use it, so we were wondering if the recipient agreement would also help us with that. Thanks very much for the information about that feature, that would be very useful for us - like I say, we're allowed to request transfers-only for some Connect accounts, but not others. Where would be the best place to request this feature?
analog sleet
to clarify, you're attempting to create a connected account with only capabilities[transfers][requested]=true, and tos_acceptance[service_agreement]=full and receiving a different error than the one first shared?
real imp
Exactly, I can do a quick example and share the result?
analog sleet
yep, can you share the request id [0]? it'd look like req_xxx
real imp
Will do 👍
Request ID: req_ugEqJShubLTZ5o
This is given for multiple countries, not just the US, I can provide a list if it helps
analog sleet
hrm, give me a while to quickly look into this
real imp
Great, thanks!
analog sleet
aha, okay i found another request where you were able to create non-US country with transfers-only
I'm aware of the limitation that "You cannot request the transfers capability without the card_payments capability for accounts in US.", however, I don't know of the reasoning for this.
I think the advice that I can give here to work around this is, for all other countries (except the US), you should be able to do capabilities[transfers][requested]=true, and tos_acceptance[service_agreement]=full, just for the US though, you're going to need to create it with both Transfers and Card capabilities
real imp
Sorry for the delay, I actually lost power for a while. Thanks for the information. You mentioned earlier that there may be a feature to turn off the requirement for card capabilities, is that still an option here?
analog sleet
ah, sorry no, that feature isn't applicable here in this case. If that feature wasn't turned on for your account, you would get an error saying
"Your platform needs approval for accounts to have requested the `transfers` capability without the `card_payments` capability. If you would like to request transfers without card_payments, please contact us via https://support.stripe.com/contact."