#bhaal22-pm-on-destination-py
marble sigilBOT
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.
cyan sage
Hmm, I don't believe that's something the API supports today.
Double checking
oblique tundra
hmmm
cyan sage
What charge object are you looking at?
cyan sage
Can you share the ID?
oblique tundra
like the payment method used
sure
give me 1 moment
let take that one for example
the correpsonding pi is : https://dashboard.stripe.com/payments/pi_3Obj0sGn3FuAFiGU1ozMZmZ8
where I have some data from the card (brand, country, apple pay or not, billing info, ...)
unless I miss one thing when I create the on_behalf_of
cyan sage
Is there a reason you're looking for this info on the connected account?
You're creating destination charges. PaymentMethod information is stored on the platform for this flow.
marble sigilBOT
bhaal22-pm-on-destination-py
cyan sage
Yeah that's expected with Destination charges
Charge objects are owned by the platform and can be refunded at the platform level
oblique tundra
so my question 🙂
cyan sage
py_ object created on the connected account is for pay-ins
cyan sage
The only way I can think of is to list the transfers to the connected account as destination
https://stripe.com/docs/api/transfers/list
and then looking at destination_payment parameter to find the exact transfer
https://stripe.com/docs/api/transfers/object#transfer_object-destination_payment
Once you find the transfer object, source_transaction parameter should get you the original payment
oblique tundra
wow
let me investigate
ok might work
py_ -> get the transfert -> get the charge
cyan sage
Yeah and then moving forward you can maybe update the metadata of the py_xxx object to contain the original payment ID as soon as it's created
i.e. when you receive a webhook for transfer creation, you look up destination_payment and update its metadata by calling the Update API + stripe_account header
I haven't tried the above so you'd want to try it out first