#stripe

Interesting but this is unfortunately irrelevant with our business model

lmcq: it will block our tracking requests , but you can ignore that

lmcq: is it affecting the actual ability of Checkout to load/work?

lmcq: cool cool — I know all the errors in the browser console can be a little worrying alright

SerialNumberGuy : step 1 is to figure out what happens when you generate a token since that's where the error lives

SerialNumberGuy : this is not a Stripe issue per se. This is a bug in your code really and that's what you need to reproduce. Just try on your end and look at the code, look at the logs in the JS console (and add some if you don't have any), look at the network tab in chrome developer tools, etc.

no, if there was there would be a clear error on token creation which does not seem to be the case

no worries at all, that's what we're here for! Some rubber duck debugging is always helpful

Mehul : You have to register the domain *on the connected account* first, using you secret key *and* the `Stripe-Account` header: https://stripe.com/docs/connect/authentication#...

"All domains, whether in production or testing, must be registered with your live secret key."

Hello! We are a platform and I'm looking for a way to debit funds from a connected account but can't see to find documentation on how to do that?

the first one does not make sense/would not work. So the Live Secret key of the platform *and* the connected account's id in the `Stripe-Account` header

cpjason : https://stripe.com/docs/connect/account-debits

Ah perfect - thank you! So when a refund is performed for a transaction on a connected account, today we've got the reverse_transfer flag set to true. However, we want to also recover the fees that the platform is charged for the refund. So is it best to leave the reverse_transfer in place and do an additional debit of the connected account or should we just leave out the reverse_transfer and debit the entire amount with a separa

Mehul : no it does not. It means you own account key. The same way it works for any request with connect. It all works the same. You might want to take a step back and read https://stripe.com/docs/connect/authentication#... carefully

cpjason : hmmm that seems weird to me, and you would pay a fee on the debit too. You should take this into account in your own pricing or something instead of debiting the refund fee every time, that's not really scalable IMO. I'd recommend talking to our support team instead: https://support.stripe.com/email

So there are fees when we do a transfer from a connected account?

for what you are trying to do yes. I would really recommend talking to our support team for this since it's about your business model and not about code

Hey again

I just noticed that some webhooks are not sent if I don't setup the webhool urls for the account

I highly recommend that you never ever do that and just ignore that doc and go back to the platform key + https://stripe.com/docs/connect/authentication#...

transfer.reversed and charge.refund are not sent with only the custom applications webhooks, I have to setup the account one. Why ?

Mowee_ : if those live in your platform account that's expected.

Obviously ! Thanks

Niedog : I would recommend asking our support team

xfechx : no that parameter is required

as a platform account, can I hold funds for merchant accounts ?

Mowee_ : depends on your type of integration and the type of accounts you are using. You should discuss your business model with our support team to avoid any confusion: https://support.stripe.com/email

Sure, okay

Guest90616 : it never is. The fee lives on the associated balance transaction https://stripe.com/docs/api#balance_transaction... instead. And you can see this on charge creation by expanding the BT at the same time: https://stripe.com/docs/api#expanding_objects

yes

the latter, today we only support US for the country of Express accounts

joshdchap : hmmm I'd recommend asking our support team for something like this: https://support.stripe.com/email

joshdchap : I know but that's not really a coding question, it's something specific to your account and so only the support team can investigate

sure but what I mean is that this has nothing to do with code or the API. Something changed and would require digging into your accounts to understand what and why

greg_c : sure what's your question?

no since you have no control over Standard accounts. It's only between Stripe and the owner of the account in that case

rotatelic : sure just delete it via the API: https://stripe.com/docs/api/curl#delete_card for example

rotatelic : not at period end no, it will cancel after all retries on the next invoice have been exhausted

another source would become the default

AndiRudi: I'm not sure what you mean by 'the subscriptions cancellation is gone'

AndiRudi: ah, yeah, that sounds odd. Do you have the subscription ID(sub_xxx) so I can take a quick look?

nhill: I believe it should be your business address.

AndiRudi: hmm, it looks in your API requests you pass `at_period_end` , but I think the parameter should be `cancel_at_period_end` Maybe that's a problem with the stripe-dotnet library. But I totally see what you mean, when you update the metadata the returned subscription has `cancel_at_period_end` set back to false.

AndiRudi: for now I'd suggest writing into https://support.stripe.com/email with that subscription ID and a description so we can look into this.

oops, actually ignore my point about stripe-dotnet there, I was misunderstanding something. But yeah, you should still write in about this, the behaviour on that subscription doesn't seem entirely correct.

minodudd_: do you have a request ID?

thank you, taking a look now

Guest13193: it's available when the invoice is finalized, which is about an hour after it's created(assuming any your webhook endpoints also return 200 responses)

Guest13193: yes, I believe so, if the object changes(to add the URL field) that event should be generated

minodudd_: still looking, that does look a little weird. The only thing that jumps out first is that you are passing an empty string for `card` , so you should check your code. But I would expect a different error message than the one you got

minodudd_: yeah, I've been trying myself and can't replicate. It's strange, `card` is totally a valid property for this : https://stripe.com/docs/api/#create_card_token-... If you could extract your code into a Gist or a Pastebin I can take a quick look

minodudd_: it can be an ID as well

minodudd_: aha ok, this is strange

minodudd_: you're passing "card " (notice the space!)

so double check your HashMap params

minodudd_: no problem! Full disclosure, I had to ask some colleagues, I didn't spot that myself either :)

hey does anyone know the endpoint to send a payout for a stripe connect account

you want to payout from the connected account to their bank account or send money to their connect account?

send to bank account

ahh ok thank you