#damo-cross-border

1 messages · Page 1 of 1 (latest)

honest crystal
#

the cross border payouts feature is for accounts only receiving payouts

gaunt yew
#

Thanks a lot for your answer

honest crystal
#

which country is your platform set up in / which countries are you paying out with the full agreement?

gaunt yew
#

The documentation threw me off, sorry about that

#

Platform account is in the US

#

some accounts are in Australia / new Zealand, others are based in Europe, Us and Canada

honest crystal
#

and tbc, you're sending a transfer from your platform balance to a connected account in eg: australia, then sending a payout to the AU connected account?

#

not eg: creating direct or destination charges in the AU connected account & paying out from that balance?

gaunt yew
#

yes, not sure if it's worth saying it, but the payout i automatic

#

we are not doing manual pyaout yet

#

we are leveraging the Stripe scheduler

honest crystal
#

manual vs automatic shouldn't matter

gaunt yew
#

yeah that's what I thought

honest crystal
#

it's possible you have some sort of special or legacy arrangement? as a rule, you can't make transfers in the way you're describing

gaunt yew
#

our businwss has two types of users

#

the one that can process payments & receives payouts

#

and the others that are only receiving payouts (commission based)

#

for the second we were using Payoneer for a while, but now we want to replace it with the recipient only agreement

#

it's possible you have some sort of special or legacy arrangement? as a rule, you can't make transfers in the way you're describing

#

So our flow in high overview picture:

#

Our platform is in US

#

we are onboarding account (custom connect)

#

payments are processed on behalf of the connected account id

#

then the connected accounts is getting paid out automatically according to the schedule they are on.

honest crystal
#

when you say payments are processed on behalf of the connected account id, what specifically do you mean by that?

#

are you using destination charges? direct charges?

#

separate charges + transfers?

gaunt yew
#

using the on_behalf_of flag (not sure if it's direct or destination)

#

I guess direct charge based on your description

honest crystal
#

do you have a sample charge I could look at?

gaunt yew
#

yeah sure

honest crystal
#

that's a destination charge

#

the request making it specifies the transfer_data.destination param

gaunt yew
#

well I feel quite stupid, I'm the one that did that integration --"

honest crystal
#

which makes more sense re: why this works with cross-border accounts

gaunt yew
#

oh okay

honest crystal
#

the destination param keeps funds from being co-mingled in your platform balance from multiple countries

gaunt yew
#

so in our case it's a matter of setting up a new onboarding for our second type of users (receiving payouts only)

honest crystal
#

yeah

gaunt yew
#

Thanks a lot for the explanation, and for taking time to check our use case 🙂

honest crystal
#

depending on which countries you're looking to pay out in, stripe may not even have the ability to make charges for merchants in those countries - just payouts

gaunt yew
#

yeah in our case we don't them to be able to process payment, we are just paying them commission

honest crystal
#

eg: argentina

#

so you have to onboard them with the recipient tos in that case

gaunt yew
#

yep

honest crystal
#

stripe doesn't have the ability to onboard them with the payments capability

gaunt yew
#

those type of users will have to be on the recipient only

#

but for the one that have already the capaiblity of processing payment

honest crystal
#

but if you have other users in countries which stripe can support payments, if you want to pay them directly from your platform balance, they still need to be using the recipients tos

gaunt yew
#

but since we are doing transfers I believe the payouts are using the connected account balance.

honest crystal
#

cross-border payouts & normal payments account are two entirely different beasts

gaunt yew
#

the case you are mentionning if we were doing manual payout using the platform balance?

#

or am I misunderstanding it?

honest crystal
#

right

#

in the case where you're not creating a destination charge on the account's behalf

#

you're just sending them a transfer with money that's from your platform balance

#

(regardless of whether the money got there with a topup from your bank account, a charge benefiting your own account, application fees, or anything else)

gaunt yew
#

yeah that's it

#

so that case is Cross Border proof?

honest crystal
#

yeah like

#

that's the recipients tos case

#

which is sorta intertwined with cross border payouts in an annoying way

#

generally speaking, an account in another country can either act like a payment account OR a recipients account, but not both

#

(accounts in the same country as your platform are more flexible)

#

stripe can support payments accounts for some list of countries, and cross-border payouts accounts in a strictly larger (I think?) list

gaunt yew
#

I see

#

Ok it's clearer for me

#

Thanks for your time and your explanations

#

Have a good day

#

Oh sorry for bothering you

#

One more question

#

hopefully less confusing

#

let me put a simple use case

#

we are doing destination charge

#

100 is the full amount

#

we have 30 of application fee

#

the connected account A gets a transfer of 70

#

now a month after, we want to create a transfer of 30 to a connected account B (using the payment as the source of transaction)

#

what's going to happen? will those 30 been taken out of the platform balance?

#

Or will it affect the balance of connected account A in some sort?

#

I tend to think it should use the platform balance

knotty veldt
#

Yes it should come from the platform's balance.

gaunt yew
#

Thanks a lot