#jakel-crossborder-obo
ebon sky
Hello! I assume you're using destination charges?
echo granite
Correct!
ebon sky
Gotcha - since you're a US based platform, you need to use on_behalf_of with the accounts in different countries/regions because otherwise it'll be classified as a cross-border transfer. Using OBO allows us to settle in the connected account's country
With that in mind, what you're asking for (being able to accept charges before onboarding is complete) isn't possible
echo granite
Would it be possible (being able to accept charges before onboarding is complete) if the connected account was also based in the US?
In that scenario, we would be using separate charges & transfers
My current understanding:
We are a US Platform:
For US Connected Accounts:
- We are using Separate Charges & Transfers
--> If we do NOT use OBO, we can process charges before onboarding is complete
-->If we DO use OBO, we cannot process charges before onboarding is complete
For Non US Connected Accounts:
- We are using Destination Charges
--> We must use OBO
--> The account must finish onboarding to process payments
Does this look accurate ?
echo granite
Is it also accurate that we cannot use separate charges and transfers for the NON US accounts ? We must use destination charges ?
ebon sky
You could use separate charges and transfers if you changed your integration and used the recipient service agreement for non-US accounts (see https://stripe.com/docs/connect/cross-border-payouts#restrictions-and-requirements)
I believe you'd have to talk to support (https://support.stripe.com/contact) to get that enabled for your platform
knotty shoreBOT
jakel-crossborder-obo
echo granite
Very interesting, thank you. Presumably (if this was enabled for us) this would allow us to split a charge between 2 non US connected accounts.
For example, a customer pays $100 for a service.
- We could then send $40 to Mexico Connected Account #1
- And then $50 to Mexico Connected Account #2.
ebon sky
Yes, that should work with recipient connected accounts