#richard_20727

1 messages · Page 1 of 1 (latest)

steep dockBOT
dusty ibex
#

Hello! Did you have a specific example I could look at?

wary tide
#

yes sorta. sorry it's hard for me to explain. But basically when a paymentIntent is created I have things like description and payment method but when the charge is made on the destination account those things are missing.
I've got my code to a point where I can grab the destination charge via the transfer; I can update that charge's description but I cannot update the billing_details as per documentation.

I believe i need to somehow tie the payment method details to the destination charge

#

ooooof i hope that made sense

dusty ibex
#

Yeah I hear what you're saying - if you have a Payment Intent ID so I can take a quick look it'll be easy for me to confirm what requests you're making

wary tide
#

can i give you a test one? or does it need to be prod?

dusty ibex
#

A test one is fine!

wary tide
#

"pi_3NyHig2u61NOe9050cxtPojp"

#

the pm_1NyHj82u61NOe9053bMsQJXY has the billing_details i want

#

Hey Karbi i've actually gotta run but when i get back i'll hit up dev-help 🙂
is there a better way to rephrase my question to help the next person better understand me?

dusty ibex
#

Ah! Sorry the channel got a bit busy and I didn't get to circle back here

#

I took a quick look and I'm guessing you're referring to the fact that the py_ object on the connected account doesn't copy over the description that you're expecting, right?

#

If you want to tie the payment method details to the py_ object on the connected account you'd have to do it through metadata, or by retrieving the associated ch_ object on the platform account and checking the billing_details there