#richard_20727
severe shoal
bold robin
Can you be specific about where you're looking and expecting to see certain data but not finding it?
rugged fog
Yeah so when we create the PaymentIntent we pass these params along with it amount, currency, description, receipt_email on_behalf_of application_fee_amount, transfer_data { destination }
this works as expected. I log into our dashboard and see.... do you mind if i upload a screeen shot?
bold robin
That's fine, best to use test mode and redact and private info though, this channel is public
rugged fog
this is in test mode
this looks awesome what we expect to see
but our customer isn't seeing this data when they log in, they see
bold robin
Ah gotcha
So that info is not propagated with destination payments, and accounts should generally not be seeing those transfer payments
But if you need to you can manually update those objects after the payment succeeds
(ie, manually replicate the PI info you set to the py_123 charge created on the connected account)
rugged fog
hmm i'm not followin'
or do you mean like click edit on the description and manually put it in?
bold robin
No i mean via the API
when the payment succeeds and the transfer is created, you can manually update the charge objects on the connected account
rugged fog
oh yes! ok this is what i was trying to do earlier today. I see the the transfer object inside the payment details of pi_3NxhaR2u61NOe90519h6l7Cf. I need to grab that from the Payment Intent. Alrighty time for CLI work
sweet ok and just for my sanity. Once i get the transfer object i want to update the metadata?
bold robin
You can get this on the payment intent by expanding latest_charge.transfer then looking at the destination_payment
Then you'd update the py_123 on the connected account using the stripe-account header
(charge update API)
rugged fog
where did latest_charge come from? is this a method i can use?
rugged fog
thanks so much. i'm gonna let you go and try to figure this out now. thanks for your help!
bold robin
NP - good luck with it!