#Joe
1 messages · Page 1 of 1 (latest)
hello! can you provide more detail on what you've tried? or the request id of what you've tried?
PaymentIntentId: pi_3M5heDRd7mJcj3RJ0HEgCozm
I would take the payment intent and get the charge. Then from the charge I would get the balance transaction. I would use the available_on from the charge's balance transaction with a type of payout calling /v1/balance_transactions?source=payout&available_on=1668828219
alright, can you share the request id too?
What do you mean by request Id?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I can give you a request id for one of them but the issue isn't the request. It's what am I supposed to use that is the question.
req_clR89Ssuz9Bnf6
You'll see that the request doesn't return anything which is true, but I was just following what I was instructed before. You can see in my original screenshot I can pull the balance transactions that are associated with a payout, but if I use the available_on field, they were not the same.
and I won't have the payoutId if I start with the paymentintentid
The request that is showing a charge and a payout that have available_on stamps that do not line up is this one: req_w3SHzI83Agdvxw
hmmm, gimme a while to think about this
so the problem here is that the charge might become available earlier than when the payout actually happens. Like what was mentioned to you previously, it's not directly possible. The way I would go about this would actually be different, everytime a Payout is created, i would pull and save the corresponding transactions and map them to the corresponding payout id in my own DB. Then when i need to, i can retrieve the relevant data from my own DB