Stripe-dotnet: MetaData does not show up on the Destination account( Stripe connect)

Created on 21 Jun 2017 · 4Comments · Source: stripe/stripe-dotnet

While creating a charge(stripe connect destination charges) I noticed that the meta data parameter is not showing up on the destination account dashboard.

Ideally the MetaData(Highlighted below) should show up on the Destination account as well. Currently it is showing up on the platform account dashboard and not on the destination account on which charges are made.

` var newCharge = new StripeChargeCreateOptions()
{

                Amount = amt,
                Currency = "AUD",
                Destination = “xxxxxx", 
                DestinationAmount = shipping + gstshipping,
                Metadata = myDict // Dictionary(key value pairs)

            };

`
Is there any work around for this

Source

varunbabu008

👍2

Most helpful comment

@amos-o a py_XXXX is just a normal Charge. So you would use the Retrieve Charge API and using the Stripe-Account header which in stripe-dotnet is set via RequestOptions

remi-stripe on 13 Jun 2018

👍3

All 4 comments

@varunbabu008 That's expected behaviour, the metadata live on the Charge in the platform not on the corresponding payment created on the connected account.

This is not a bug with the library so github issues is not the best place to discuss this. The idea is that you will Create the Destination charge and get a Charge object back with a transfer property for a Transfer id tr_XXXX that you can expand. This Transfer object will have a destination_payment id py_XXX. You can then use that id to retrieve the payment (like a charge) on the connected id and update it to the right metadata.

If you have follow up questions, it's best to reach out to our support team: https://support.stripe.com/email

remi-stripe on 21 Jun 2017

👍3

@remi-stripe You said:

You can then use that id to retrieve the payment (like a charge)

Which endpoint would I use to do that? Because as of now, the destination payment ID I get is of the format py-xxxx which is not a Charge or a Payout so I am stuck there.

amos-o on 13 Jun 2018

@amos-o a py_XXXX is just a normal Charge. So you would use the Retrieve Charge API and using the Stripe-Account header which in stripe-dotnet is set via RequestOptions

remi-stripe on 13 Jun 2018

👍3

I was missing the Stripe-Account header. Thank you @remi-stripe.

amos-o on 13 Jun 2018

👍1

Was this page helpful?

0 / 5 - 0 ratings