#sweets-connect-payouts
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sweets8594, 3 minutes ago, 22 messages
Hi again
Sounds like you are improperly using the Stripe Account header here
Can you show me your code?
What are you trying to do exactly?
Create a Payout on the Connected Account?
Or create a Payout for your own account?
Okay then yeah you don't pass destination at all. You use the Stripe Account Header like we show here: https://stripe.com/docs/connect/authentication#stripe-account-header
So you would have an options object with stripeAccount: 'acct_123'
That is just a screenshot of code
So I have no idea
If you explain what you are trying to do then maybe I can advise
But just screenshots of your code doesn't really tell me anything
i am creating an app which include driver and normal users
users making payment for the trip
and i need to store that tripId in paymentIntent destination
and by stripe.transfer.create i am transferring funds to the connected account where i am also sending trip id
that tripId i am getting in transfer.create webhook and i am storing it in my database
what i am trying to do is getting tripID in payout.paid webhook description
did you get it?
please help me 🥲🥲
Hi please be patient
We help many users in here
Will get to your question in a little
okk I'll wait
Payouts can include multiple payments
So 1 payout.paid event will most likely represent several trips
yes
Right so you won't have just 1 trip id
So do you store a mapping of trip id to payment intent in your database?
There's some api calls you can do to get trip id's from payout as long as you keep track of trip id's relationship to payment intent somewhere, but it's a bit involved
sweets-connect-payouts
Ah cool