#Jasuno

1 messages · Page 1 of 1 (latest)

opaque muskBOT
shy geode
rocky jacinth
#

So i'm guessing that a no

shy geode
#

Yeah you can't do the reverse

rocky jacinth
#

Can i update a customer in a connect account using a clone token?

shy geode
#

That's all you need to update the customer on the connect account

rocky jacinth
#

So here is some context, im going to have multiple stripe connect accounts and multiple customers. there are going to be instances where the customer needs to be created before there are any payment methods saved which means i cannot clone them. The question is, is it possible for me to create the customer in the connect account, but if the customer adds a payment method, to trigger a webhook that will clone the customer (after they add their payment method) and update the customer that was already created in the connect account so that their payment method are saved across different connect accounts?

shy geode
#

Ok. Is there any reason you're not using Express or Custom accounts with a destination charge flow instead? This way all payment methods and customers will be stored on the platform and you won't have to deal with cloning.

rocky jacinth
#

So all connect accounts are express, but since we are building a rental property management application, each individual landlord will have their own connect account, but the tenants can go from landlord to landlord (from connect account to connect account) we want to make sure that if they added their payment info that they can use it again in the future with a different landlord

shy geode
#

That's exactly what destination charges solves for. And you really shouldn't be storing customers and payment methods on the connect account with Express accounts.

rocky jacinth
#

Ok so you recommend using custom?

shy geode
#

No

#

I recommend you use destination charges

#

That's the recommended flow with custom and express accounts

#

Direct charges (what you're currently doing) are only recommended with standard accounts

rocky jacinth
#

Oooooh here is the thing, would that work on a subscription?

#

because a subscription or scheduled subscription requires a customer

#

There are subscriptions that are being set up in the connect account since we need the change to be billed automatically once a month

shy geode
#

Works with subscriptions fine

#

But again, it's generally discouraged to do direct charges with express accounts. It causes problems

rocky jacinth
#

Im not sure if i quite understand how the destination change works with subscriptions,

shy geode
#

Pretty much the same as with PaymentIntents

rocky jacinth
#

but let me give it a stab, with destination changes, our platform would have all the customers and all the subscriptions and we would just transfer the money to the connect account once its done?

shy geode
#

If you pass transfer_data correctly, there's no need for you to initiate a transfer

#

It all happens behind the scenes

#

Recommend reading the guide I shared in-full to make sure it will be fully compatible with your integration/use-case

rocky jacinth
#

Thanks that may just fix our problem

opaque muskBOT
rocky jacinth
#

In that case will the connect account have access to their invoices?

shy geode
#

Ah no. Since those will exist on the platform account

rocky jacinth
#

Shoot, so close, if there a way to filter an invoice list by subscription Id?

shy geode
rocky jacinth
#

Ok in that case i could probably keep track of the subscription ids from a particulars landlord on my own server, and the fetch invoices by subId, its probably going to be slow, but i cant think of anything else

shy geode
#

Yeah we generally recommend storing as many id's as possible on your end to reduce GET requests to the Stripe API

rocky jacinth
#

Thanks for everything