#.bustafa
tame cave
chilly quail
👋 happy to help
strange venture
hi, @chilly quail. So, what can you tell about according to the demo, description and error?
chilly quail
will be with you shortly
digital veldt
What should we do? just accept service agreement or what?
strange venture
@digital veldt is also from our team
chilly quail
where is your platform account based in?
basically it seems like a cross border issue
https://stripe.com/docs/connect/account-capabilities#transfers-cross-border
strange venture
our platform is based in US and Stripe acc is US
chilly quail
in that case you need to follow this doc https://stripe.com/docs/connect/cross-border-payouts
strange venture
we already looked this doc. Could you please give us particular steps to fix it. Now we use 2 Stripe enpoints create user and create link what should be done in addition to fix this "cross border issue"
I mean expected result for Austria and all EU is the same like we have on demo video
chilly quail
Platform must be in the US.
Connected accounts must be Express or Custom accounts.
Platform must be the business of record. Consequently, destination charges with on_behalf_of (OBO) aren’t supported.
Connected accounts have to onboard under the recipient service agreement.
so the recipient service agreement is a must
strange venture
Ok, I read the doc
looks like the fix is
https://stripe.com/docs/connect/service-agreement-types#recipient
linked page to that one
chilly quail
exactly
strange venture
exactly what?
there are Supported agreement types
Full service agreement
Recipient service agreement
what to choose
chilly quail
you need to use the recipient service agreement
strange venture
which is the difference?
chilly quail
A full service agreement creates a service relationship between Stripe and the connected account holder. Connected accounts under the full service agreement can process card payments and request the card_payments capability.