#Masud (usequeue.com)-cross-border

1 messages ยท Page 1 of 1 (latest)

wise tundra
safe tree
#

๐Ÿ‘‹

wise tundra
#

Sorry it's a bit busy in here today! Give me a couple more minutes and I can help

#

For cross border payouts that'd be something you configure on the connect account, not the platform. You'd want to create your connect accounts with the recipient service agreement (you can read a bit more about this at https://stripe.com/docs/connect/cross-border-payouts)

safe tree
#

oh okay got it, so it's not something i do on OUR stripe account, but the connect account api.

#

so this? tos_acceptance: {service_agreement: 'recipient'},

wise tundra
#

Yup, that's the idea

safe tree
#

Question: Do we have to do this for EVERY single connect account or only for specific countries that requires it?

#

lemme rephrase that

#

Can we enable this for every single connect account? or should we only filter for specific countries

wise tundra
#

You'd want to do it for any account that would need cross-border payouts (so any country that isn't the same country as your platform)

safe tree
#

We're in USA, so any country outside USA that we setup a stripe connect account for, needs this enabled?

wise tundra
#

Correct ๐Ÿ‘

safe tree
#

Saw that for accounts with service_agreements 'recipients', they cannot have card_payments: {requested: true},.

What does removing card_payments: {requested: true}, mean? It means they cannot take card payments or cannot DO card payments?

wise tundra
#

Recipient connect account can only accept funds through transfers. You can't create any payment on their behalf (using on_behalf_of or with the Stripe-Account header)

safe tree
#

oh okay, but if someone wants to pay them via stripe charges elements, that's possible right?

wise tundra
#

The platform would collect the payment and then you'd do the transfer separately. The connect account wouldn't be directly accepting payment

safe tree
#

Platform = me the company, right?

#

makes sense thx

wise tundra
#

๐Ÿ‘