#Gaildess-Connect

1 messages · Page 1 of 1 (latest)

fossil kite
#

It suppose to use on_behalf_of Is there any reason you don't want to use that parameter?

obtuse path
#

Our platform advertises pseudo-chargeback protection for sellers. My understanding of on_behalf_of, is that if a chargeback occurs, because the connected account is listed as the merchant, the sellers account would be debited back the chargeback, and not the platform's account, while the chargeback resolves.

#

In addition, from the documentation here: If the account is in a different country than the platform, the connected account’s address and phone number shows up on the customer’s credit card statement (as opposed to the platform’s)
We would prefer if our seller's personal information was not sent to the clients on a credit card statement: https://stripe.com/docs/payments/connected-accounts

fossil kite
#

Chargeback shouldn't be an issue, as regardless of using on_behalf_of or not, Destination Charges also take Platform responsible for Chargeback. on_behalf_of is just to decide whose information is used for displaying in statement descriptor, and yes its your 2nd concern

obtuse path
#

I see. So there is no way around revealing seller's information for cross-border payouts?

fossil kite
#

I think it's possible with Separate Charge and Transfer. You charge the end customer with your currency, displaying your information, then separately transfer to your Connected account

#

But you need to be an US Platform

obtuse path
#

Is there no way to charge in the native currency of the seller? For example, an Australian seller selling to an Australian customer, could they pay in AUD using separate charge and transfer?

#

We may have to use on_behalf_of

obtuse path
fossil kite
#

Is there no way to charge in the native currency of the seller?

#

This comes down to : can you charge an Australian customer by AUD? I think it should be possible