#ashwin_03833
1 messages · Page 1 of 1 (latest)
the request wouldn't be able to find the card token on the other account
So I will have to implement the appropriate routing. i.e. store the account that the card was tokenized against and always route the charge to the correct account. And for currency conversion, I would have to set CA as the currency?
can you share more about your business model? how does your business work for example? That'll allow me to better be able to advise you
I work for swimply. We have a marketplace for spaces like pools, backyards etc. A US guest might book a facility with a canadian host. We use custom connect. So we as the platform charge the guest and then transfer the host's share to the host's connected account.
We operate in US, CA & AU. We have a separate account for AU, but share the US account for CA. But are investigating opening a CA account to avoid the international fees.
sounds like you're using Separate Charges and Transfers (SCT) right now?
yes.
pretty much yes, you're going to have to keep track of where the card was tokenized and then charge it on the right account. Is your end goal though to allow a guest to sign up once on your platform, and to be able to charge the save card on any of your US, CA, AU accounts?
Yes. We want to keep things transparent to the user. We dont expect a lot of crossover but expect a few bookings over the border. So basically the flow would be:
- US user books CA facility for CA$100
- We charge the US user's card CA$100. Stripe handles the currency conversion to USD
- We topup the CA account if necessary so that transfer to the CA host succeeds.
Does this sound right?