ere_api

[sleek crystal]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1225781858520793099

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[neon needle]

We have a setup involving platform accounts with its connected accounts. We are mostly using destination charges to handle customers & subscriptions residing on the platform account, charging an application fee and moving the rest of the money to the connected accounts. But for individually created invoices in most cases we would like the connected accounts to be responsible for the Stripe fees and such.

My understanding is that it would be possible using direct charges in these cases instead of destination charges. I spotted the article on cloning a payment method https://docs.stripe.com/payments/payment-methods/connect#cloning-payment-methods that could help us, but seems like the customer has to also be on the connected account. At least we get an error saying "no such customer".

1. Do we also need to somehow clone the customer to the connected account?
2. Are there some downsides to this approach, like keeping the customer information in sync on both accounts or such?
3. Is there some other simpler way to make the connected account responsible for the Stripe fees where we can still have the customers and subscriptions on the platform account?
4. Or should we have the customers & subscriptions on the connected accounts to begin with? We would then need a way to make the platform account responsible for the Stripe fees in this case, if this is the way to go then how would we do that?

[stark nest]

hi! well re: the error, when you clone the PaymentMethod, that is all that's cloned, nothing else. In that failed request you pass the ID of the Customer from the platform account, which is not available/existing on the connected account, so that's an erorr. You can or can not create a new Customer on the connected account and attach the PaymentMethod to that, it depends if you want to keep the cloned PaymentMethod saved on the connected account or not.

1. you can't clone it, you can create a new Customer(/v1/customers + Stripe-Account header) if you want. But in your case, since you're choosing to use Invoices and not just raw PaymentIntents, you will have to create a Customer object ,yes.
2. yes, keeping stuff in sync is really hard. Usually I'd say just have a 'master' customer on the platform and just clone the PM to a connected account when needed. But again, using Invoices requires a Customer so you'll have to create one.
3. No
4. well if you do that the connected account pays the fees. That's just how it works, you have to choose which approach you want for the business(Direct => connect account pays fees, has all the objects; Destination => platform pays fees, has the objects, tranfers just money to the connected account)

[neon needle]

I see thank you, how would just using a payment intent differ from using an invoice? I suppose the customer is just charged and not sent anything?

[stark nest]

a PaymentIntent can just take an amount currency and payment_method and doesn't need an associated Customer object

[neon needle]

This should get us forward, thanks

[neon needle]

I suppose tax cannot be automatically calculated using just payment intents? That might be an issue for us

[opal cypress]

Not automatically