#dtops_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1259828155779125342
đ Have more to share? Add details, code, screenshots, videos, etc. below.
Cross border transfers like you describe are supported in some scenarios: https://docs.stripe.com/connect/account-capabilities#transfers-cross-border
European Union, United Kingdom, and Gibraltar platforms sending funds to SEPA countries.
Seems to fit that criteria!
Hi @acoustic hill Thanks for you answer. So it seems that in my scenario I can transfer from UK to SEPA countries? That is why this transfer works?
As US is not in that list, it is shown the error message as expected?
Yes a GB platform cannot 'transfer' to a US account
you'd need a native US entity and platform
Okay, thank you for clarifying. I just wanted to check that this will be the case in production.
I was concerned the test API was allowing UK -> Europe through but it would not in production.
@acoustic hill I have another related question. In the connect account setup, there is two options.
Tranfers and Payments.
Transfer section is what we discussed above, but I do not understand how payments works in my scenario.
Does it mean that a connected account In Australia, cannot accept transfers UK -> Australia, but it can accept payments?
No, test mode will model live mode behaviour 1:1 in basically every scenario
It'd allow the account to process payments individually without your (platform) control yes
Okay, so in that case, would it mean I can create a checkout session for the connect account using the API?
I am unsure how this would differ from how I am doing it as the moment with payment intents data
Does it mean the customer must be under the connected account and not a customer of the platform?
Theoretically yes you could create a 'direct charge' payment on the conencted account although that's not really recommended with Express accounts
Yes, in direct charge scenarios all related objects must exist on the connected account
Okay, so as we wont to handle refunds etc on the platform, I can see that it is not recommended to do a direct charge.
It would mean we have to create a new customer under the connected account for that scenario, is my understanding.
Yes to both points
The Express acocunt would be liable for disputes/refunds etc and it's just not recommended for them in most cases as they don't have a full Dashboard access etc etc
Understand, thank you for your help today.
No problem, glad I could help!
@acoustic hill One more, do you know if Stripe plans to add transfer support from a UK platform to non SEPA countries such as the US or Canada in future?
I'm not sure, better question for support: 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.