#shaneCC
viscid tundra
sage thicket
Hi there
frozen needle
Hey bismarck!
sage thicket
Hmm I don't believe it can. Have you tested it?
I can double check as well.
I assume you are talking about going from full to recipient?
Or vice-versa?
frozen needle
ya full to recipient, because our transfers are being blocked to cross-border countries
I see in the API, it shows that you can update an account, but says "Custom Only"
Didn't know if it's possible to maybe change that on the dashboard or somewhere else
sage thicket
Yeah this would only be possible via the API
I can test it in a min unless you can test first
It does look like it should be possible for Custom Accounts
But I haven't tried this before myself
frozen needle
It would be awesome if you could!
sage thicket
Sure give me a moment
frozen needle
actually I went ahead and did a test. I'm getting this error, so I'm assuming that means it is not possible?
This application does not have the required permissions for the parameter 'tos acceptance' on account 'acct ....'
frozen needle
It's a standard account
sage thicket
Ohhh
Then yeah that't not possible
Standard Accounts only have full recipient agreements. You can only do cross-border transfers with Express/Custom
frozen needle
ahhh
sage thicket
Otherwise you need to use on_behalf_of with destination charges or you use Direct Charges
Sorry, thought you meant earlier that you were using Custom
frozen needle
No worries, I should had mentioned that at first
frozen needle
Real quick last question, I'm curious on why separate charges and transfers are not recommended for standard accounts?
safe gazelle
Hi there. bismarck had to step out. Seperate charges and transfers, similar to destination charges, aren't recommended with Standard accounts because the initial liability for chargebacks will fall on the platform instead of sitting with their connected accounts as funds are first debited from the platform’s balance. Also, Standard accounts are able to log in and view their own dashboard and control their payout schedule as per usual. This may lead to inconsistent behavior and customer support queries across connected accounts depending on how they set up their account. They will not be able to respond to chargebacks or control or set Radar rules since all the activity is in the platform. Essentially, weird issues/things start to crop up when you do destination charges or separate charges and transfers on Standard accounts due to the fact that Standard accounts are fully-fledged Stripe accounts, and with destination charges or separate charges and transfers, the payment objects, etc. all live on the platform account.
frozen needle
That makes perfect sense! Thank you so much! Sorry I have just a couple more questions that popped up. May I ask you?
safe gazelle
Go for it
frozen needle
Awesome. So for separate charges and transfers, I see this statement: "Separate charges and transfers are supported only if both your platform and the connected account are in the same region." I'm assuming the exception here is if the connected account has the recipient service agreement?
safe gazelle
The exceptions to this is covered in this section: https://stripe.com/docs/connect/account-capabilities#transfers-cross-border
frozen needle
Here is a quick scenario we are dealing with:
Connect account in the US has a product for sale. Another connect account in Australia is an affiliate for that product on our platform. So when customer buys that product through the affiliate, we charge with separate charges and transfers, keep our fee, transfer austrilia their affiliate commission and transfer the US seller the remaining money, all at once
Ahh I see this line: "US platforms sending funds to cross-border payouts destinations using a recipient service agreement." So with my scenario above, I should be good to go right?
safe gazelle
Yeah if the australian account has the recipient service agreement you should be good
safe gazelle
No worries. Go for it
frozen needle
I see here: "Stripe supports separate charges and transfers in the following regions: Australia, Brazil, Canada, Europe, Japan, Malaysia, New Zealand, Singapore, and the U.S." So if a connect account is apart of any of the other supported countries for connect accounts, we need to be using Destination Charges for them? and in the case of my scenario above, they would not be supported to be an affiliate of a US product?
For example, a Mexico connect account?
safe gazelle
Is your platform in the U.S.?
frozen needle
yes
safe gazelle
Then you can do separate charges and transfers and send to any of these countries: https://stripe.com/docs/connect/cross-border-payouts#supported-countries
US platforms sending funds to cross-border payouts destinations using a recipient service agreement.
frozen needle
Oh weird. I didn't see that page. This page shows that statement I pasted above which show less countries: https://stripe.com/docs/connect/charges-transfers
safe gazelle
That list of countries is the list of platform countries where sc&t are supported
If you are a US platform, you can send to more countries (the links I sent)
frozen needle
This list is WAY more countries than the supported connect countries! Does this mean all of these countries can have an express account but only with recipient service??
safe gazelle
What list are you referring to that's shorter?
safe gazelle
Oh hm to be honest I'm not sure about that. I would reach out to support about availability per country. They know much more about those kinds of things. https://support.stripe.com
safe gazelle
Yep I'm not sure. I'd reach out to support about that. We do clearly say express & custom accounts available in these countries: https://stripe.com/docs/connect/cross-border-payouts#supported-countries
Maybe the global list is just for platform and standard accounts
frozen needle
ahh ya that would make sense. Ok, I will reach out. Thank you for your time!!