#captainrobbo

1 messages · Page 1 of 1 (latest)

astral sleetBOT
vast ravine
outer falcon
#

Yes, req_IUO6lRfNuq9tE1

vast ravine
#

So the Transfer object does have the Description property set based on your incoming parameter. But you want to see that on the destination_payment, correct?

outer falcon
#

That's correct. When we go live, the receiving account will be a charity and they would like some info on who is donating to them, which I could put in the description.

vast ravine
#

We do not propagate the description property of the Transfer to the resulting payment.

#

Are these donations linked with charges you are taking on your account?

outer falcon
#

Yes, but it's quite fiddly, with three accounts involved. We take entries for sporting events, keep a small fee and pass most onto various sports clubs using Connect. The new part is allowing an extra voluntary donation to a third party, a charity. I am trying to do this by upping the app fee, and then doing a manual transfer

vast ravine
#

I realize it is less than ideal but the charity users can also see the Transfer data from the Payment on their Stripe dashboad

#

I just tested this on my own

#

If I click on the Transfer I see the description and other metadata I added to the Transfer object

#

However, I think we should propagate at least the metadata from the Transfer to the Payment

outer falcon
#

OK, thanks. I'll have a go at adding metadata and see if that works. Thanks for your very prompt and detailed reply

vast ravine
#

Oh I'm sorry

#

We don't currently pass the metadata from the Transfer to the Payment ( I tested this on my end first )

#

But I am going to raise that internally to see if we can enable that feature

outer falcon
#

It's not a problem. We plan to log each donation in a database table on our side. Although if you are making a code change, I would suggest propagating descriptions too, as then there would be a nice clear listing visible to the recipient of any transfer in their account