#sawyer_api
turbid talonBOT
👋 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/1313127972793745408
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fresh quest
hi! that's how it works yes, the recipient has a Stripe account of their own.
what you want is a Destination Charge integration, based on your description. If you have some specific errors/request IDs req_xxx like what happens when " it keeps saying that i m using the application account and not a random stripe account" I can have a look at those
tribal tulip
yea probably, i want to send the charge to my application account, that way, i would invoice them myself. Here is the request in error : req_ENIgN1XkHFsa64
thanks for helping me 🙂
fresh quest
in that case you passed a Customer object that you created on the connected account(using "stripe_account"), which is how a Direct Charge integration(where the objects are created on the connected account and the connected account pays the fees and handles refunds/disputes etc) would work. If you want to use Destination Charges you would not be creating the Customer there, you'd use a Customer on your own platform account.
tribal tulip
ah okay, but i would like to keep it that way, if possible, that my connected account have their own customers. Is it possible, in another way, to do what i want? paying the stripe fee with my application ?
fresh quest
I would say no, that's one of the configurations that's not supported (https://docs.stripe.com/connect/migrate-to-controller-properties#unsupported-configurations) (you want the connected account to have a full Dashboard and access to customers but for your platform(application) to pay the fees, which is not something we support today)
tribal tulip
okay so what i should do is : create the customer directly linked to the connected account of my platform. And then, when i create a subscription or invoice, create on each customer account the different subscriptions, linked to the different customers that are on my okatform's connected account. Then i can parameter the transfer_data to the different connected accounts. That will work? And using the solution on not using the express type, it might be more complicated for us with KYC, transfers and so on. Am i right?
fresh quest
create the customer directly linked to the connected account of my platform
that's hard to understand.
what you'd be doing, for a normal Destination Charge integration , is create a Customer object cus_xxx on your main, platform account(use your API key and do not pass "stripe_account").
The same applies for all other objects you might create like Price/Product/Subscription/Invoice
Then yes, in those APIs there a ways to set transfer_data so the funds from those payments get transferred to a connected account.
And using the solution on not using the express type, it might be more complicated for us with KYC, transfers and so on.
I'm not really sure what you mean by this. But in general for a typical Destination Charge integration, Express accounts the recommendation yes.
tribal tulip
okay sorry for not being so clear, yuo understood correctly 🙂 but the, when i will want, for example, to get subscriptions of an account, like this for example, it wont work, right? $this->client->subscriptions->all($parameters, ['stripe_account' => $accountId]);
fresh quest
no, that won't work
That lists subscription objects on the account, and in this setup there are no such objects on the connected account(the only objects it has is the recieved payment from the transfer). if you want to do something like that you need to implement your own logic for it such as adding metadata so you can know "oh sub_123 is related to account acct_456" and checking that in your own logic after calling $this->client->subscriptions->all($parameters);
turbid talonBOT
tribal tulip
mmh, okay, and if i want to do both : stripe fee for my application AND keeping the objects like subscriptions or invoices linked to the different stripe connected accounts, i can't really do it? or there is another way?
fervent turret
Hey! Taking over for my colleague. Let me catch up.
tribal tulip
hi! of course, thanks 🙂
fervent turret
mmh, okay, and if i want to do both : stripe fee for my application AND keeping ...
The workaround that my colleague suggested seems a good option.
I don't think you can achieve that using Stripe API natively. You'll need metadata and extra logics in your integration to keep track of that.
tribal tulip
okay, so that's what your customers do in general in their apps in that case? Because you see what i want, invoice my clients (that are the ones with stripe connected accounts) of the stripe fee + our fee, but not realated to the invoicing they are using.
fervent turret
Yeah this should be tracked in your integration unfortunately, I can't find another option honestly...
tribal tulip
okay, thank you very much for helping me anyway