When a destination charge is created by a platform, using the Charges API or the PaymentIntents API, the metadata set on the charge by the platform will not propagate automatically to other objects that are created, for example, the Transfer that moves funds to the connected account, or the Charge on the connected account that represents the incoming money. The description and metadata are only set on the Charge or PaymentIntent on the platform account, which are private to the platform. Some users may need the metadata or description on the platform to be set on the Charges or PaymentIntents in the connected account. This requires custom development.

To do this, get the id of the payment on the connected account that corresponds to the payment on the platform account. Get the transfer id associated with the charge on the platform from the transfer property on the Charge object, then retrieve the transfer and inspect the destination_payment property, which refers to the payment on the connected account.

This can be done in a single API call by using the expand feature and passing transfer to get the transfer property expanded in the response, which gives you access to the destination_payment id directly in the initial API response. From there, you can call the update Payment Intent and/or Charge API using the Stripe-Account header for the connected account and set the desired description or metadata on that payment.