#being-metadata-express
velvet solstice
@queen sail that's expected, that's purely for your own platform. We don't show metadata in the Express Dashboard
queen sail
This is the sample payment. We see the metadata section there.
just no values
My current guess metadata is on Session's object. Is there a way to pass on the metadata to paymentIntent or the Charge
if we can do that it should show up on connected account too
what is the way to set the metadata for py_1LKVJ3Qk8J93T3gBXNDOyXQi
velvet solstice
oh boy
Okay so as the platform, you create a Session, it lives in your platform. That Session will create a PaymentIntent, which in turn will create a Charge on success, which itself will create a Transfer
all of those live in the platform
The Transfer will create a Charge in the connected account, that py_123 you mentioned
all those objects are entirely separate and they each have their own metadata
You can't magically set metadata everywhere, you have to write code to do this for you.
But it's important to know that even if you do, the owner of the Express account will never see it. Because the view you see on the page you shared is not the same as the view they would see
velvet solstice
Now if you want to set it for yourself via the API, the idea would be to use the Update Charge API (https://stripe.com/docs/api/charges/update) and passing the py_123 as the id and the Stripe-Account header (https://stripe.com/docs/connect/authentication#authentication-via-the-stripe-account-header) as the id of the connected account.
The py_123 is found in the Charge's Transfer's destination_payment