#nukesforbreakfast_docs

1 messages ¡ Page 1 of 1 (latest)

river wrenBOT
#

👋 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/1306082852781424680

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

indigo rampart
#

Could you share what you're trying to achieve, so that I can suggest the solution?

sharp jay
#

sure

#

I want to store the customers on the platform account. However, in order to use direct charges with invoicing + connect, I need a customer on the connected account. The docs indicate there's some token I can use for "shared customers" in order to not have to store the customers on each connected account. However, the doc there links to a feature that says it is "legacy" and no longer supported.

#

how can I store a customer on the platform account, yet use it for direct charges on connected accounts?

#

specifically with invoicing.

indigo rampart
#

Is there any reason why you would like to use Direct Charges in this case? Do you let the connected account holder to manage their own payments? If so, the cloning customer guide (https://docs.stripe.com/connect/cloning-customers-across-accounts) is the only way if you store the customer information on the platform and would like to perform direct charges on the connected account.

If your case only simply wants to have the connected account as the merchant of record on the invoice (not managing the payment), Direct Charges will not be needed. You can simply use Destination Charges (on the platform) with on_behalf_of: https://docs.stripe.com/invoicing/connect#on-behalf-of

Clone customer payment information across connected accounts

Reuse payment information across multiple connected accounts that share customers.

Create an invoice with Connect

Create invoices for connected accounts and optionally take fees in the process.

sharp jay
#

ok got it. It seems like the cloning is not the good way anymore, and I should instead be looking at destination charges.

indigo rampart
#

This will depend on your business requirements.

If the connected account will be the one managing the payment, then Direct Charges is still recommended. You can clone the payment method from the platform to connected account: https://docs.stripe.com/connect/direct-charges-multiple-accounts#clone-and-create-direct-charges

If the connected account will only be the merchant of record, then Destination Charges with on_behalf_of is recommended, so that you don't have to clone the payment method: https://docs.stripe.com/invoicing/connect#on-behalf-of

Create an invoice with Connect

Create invoices for connected accounts and optionally take fees in the process.

Share payment methods across multiple accounts for direct charges

Save payment details on your platform and clone them to connected accounts for making direct charges.

sharp jay
#

ok, this helps. Thank you!