CR

[restive oyster]

When an account is trying to onboard, the country selected is my platform's country, and its not changeable by them so they are unable to onboard.
Can you share a req_xxx ID from where you create those accounts?

I cannot see USA under the list of Transfer Capabilities, even tho the competitors are able to onboard accounts form USA too 🤔
Not sure what you're referring to here.

[valid veldt]

where do i find this "req_xxx " ?

[valid veldt]

ok so im trying to do destination charge with platform in Germany

it requries Transfer capability on the Onboarded account

but i dont see USA

[restive oyster]

https://support.stripe.com/questions/finding-the-id-for-an-api-request

[valid veldt]

means people from US cannot onboard at all?

[restive oyster]

Yeah, cross-border transfers (which is a part of a destination charge - you transfer funds to another account) are pretty restricted: https://stripe.com/docs/connect/account-capabilities#transfers-cross-border

If you're a DE platform, you can only transfer to SEPA countries (as per that list)

You'd need a US entity and Stripe account to do US destination charges

[valid veldt]

req_WghyBNE0ThfMiJ

[valid veldt]

ah shittt :' (

[restive oyster]

Yep, so as you're passing the capabilities hash on creation we limit the account country to the platform country (DE). You should just remove that parameter, and then we'll default to the Connect settings you have configured

[valid veldt]

ok cool.

so

if i wanna connect USA to my DE platform, it will still be possible with Direct Charges right?

but then, the statment descriptor will change to that of the onboarded account, or can I cusomitize the Descriptor to platform's too?

[restive oyster]

Yes, that would work. But there's a lot of other things to consider then as the payment is processed on the connected account (liability, flow of funds, etc all changes)

[valid veldt]

I see. Alright, makes sense.

Thanks for the quick support 🙂