gershadahlnor_api | Stripe Developers | Page 1

worn scaffoldBOT Sep 6, 2024, 4:18 AM

#

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

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

#

cyan drift Sep 6, 2024, 4:22 AM

#

hello! The destination account should be connected account id

solar trench Sep 6, 2024, 4:25 AM

#

which connected account? the one who has the products and is getting paid?

cyan drift Sep 6, 2024, 4:26 AM

#

yep, that's correct

solar trench Sep 6, 2024, 4:27 AM

#

okay thats what i have it set as

#

in this case it's acct_1PnYDKFSCnOQZh7V

cyan drift Sep 6, 2024, 4:33 AM

#

ah i see, sorry i missed out seeing that you included the StripeAccount header as well : https://docs.stripe.com/connect/authentication

Making API calls for connected accounts

Learn how to add the right information to your API calls so you can make calls for your connected accounts.

#

to clarify, are you trying to create direct charges or destination charges?

solar trench Sep 6, 2024, 4:33 AM

#

destination charges

cyan drift Sep 6, 2024, 4:40 AM

#

then you shouldn't be using a StripeAccount header. You should remove that

solar trench Sep 6, 2024, 4:41 AM

#

okay but when i remove it, then the customer that was created under the connected account isn't found anymore

#

would it be better to use direct charge instead?

cyan drift Sep 6, 2024, 4:47 AM

#

When you use destination charges, all objects (such as Customers) should exist on the platform account, because the payment is made on the platform account

#

you choose the charge type based off what fits your business model best. It shouldn't be based on whether your API call is working.

#

going back to the original problem you're facing - the Customer should be created/exist on your platform

solar trench Sep 6, 2024, 4:51 AM

#

so whats the difference between having a customer on the platform vs have a customer within a connected account?

#

our main use case is that "premium" accounts can create products on our platform. and then customer can buy those products. based on that transaction i was assuming destination chargres would be our use case

cyan drift Sep 6, 2024, 4:52 AM

#

yes, that sounds about right

#

I'm not too sure I understand the question about whats the difference between having a customer on the platform vs have a customer within a connected account - it's where the customer exists. If you make an API call on the platform, then you would only have access to your platform objects. It's like how you are going into a house, and then you can use a cup in that house to drink a cup of water

#

if you're in house A right now, you can't magically access a cup in house B

solar trench Sep 6, 2024, 4:56 AM

#

i meant why would i pick one over the other? if a customer exists on the platform instead, are they still able to buy a connected accounts products?

cyan drift Sep 6, 2024, 4:58 AM

#

this is how direct vs destination charges work

#

direct charges are made on the connected account, and destination charges are made on the platform account

solar trench Sep 6, 2024, 4:59 AM

#

got it, so we should've decided on charges first instead of customers 😅

#gershadahlnor_api