#vparthay_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1364697579744661554
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
That payment refund was the result of a transfer reversal, which was done on your platform in this request: https://dashboard.stripe.com/logs/req_2b6ARH8dtaZ7hu
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
What's the refund id?
What do you mean?
I am trying to tie with TRR with the actual refund and unable to find it.. Which API should I be using for it?
Ah
You can see the Transfer ID in that request and if you retrieved it then you could look at its source_transaction: https://docs.stripe.com/api/transfers/object#transfer_object-source_transaction
sure thanks ..
"source_transaction": null,
I get a null, does that mean this came out of nowwhere?
What happens if you expand source_transaction when you retrieve the Transfer?
it is still null
trr_id = "tr_1QbDshDMNOMDEQIUW5cZCU6N"
transfer = stripe.Transfer.retrieve(
trr_id,
expand=[
"source_transaction",
]
)
print(transfer)
Hmm okay sorry I must be misremembering. I thought we set source_transaction for destination charges... let me double check on that...
Just to be clear, there is no refund tied here
Like the Transfer Reversal was a separate API request
But I am assuming you want to know the originating PaymentIntent for the Transfer, correct?
But I am assuming you want to know the originating PaymentIntent for the Transfer, correct?
Yes yes yes..
๐ Taking over this thread, catching up now
Thanks for waiting! source_transaction is generally used to retrieve the original Payment Intent. However, this original Payment Intent pi_3QaUhuDMNOMDEQIU0nwcsfH0 was created with multiple capture, which the source_transaction isn't populated when multiple capture is used.