#nike-paymentintent-update

1 messages · Page 1 of 1 (latest)

near storm
#

Hello @mighty bison! the description on the PaymentIntent and the Charge are separate. If you update the Charge one it won't be reflected back on the PaymentIntent

mighty bison
#

That makes sense, I'm curious why the PaymentIntent does end up with an updated metadata though. Is that actually separate and part of the charge but just displayed with the PaymentIntent in the ui?

#

Seems like I should just be updating both the PaymentIntent and the Charge. I was just surprised looking at the page that One worked and One didn't. 🤷‍♂️

near storm
#

We also do not sync back metadata either

#

Do you have an example PaymentIntent I can look at?

mighty bison
#

pi_3LcqtAFMvLS54Isy0ehLVoIM

near storm
#

looking, sorry lots of questions

mighty bison
#

Thanks. Yeah, I totally get it.

near storm
#

okay so I got worried for a while but as far as I can tell metadata is only on the Charge and not the PaymentIntent

#

if you retrieve it you would see it's empty

#

So I do think this is overall confusion. A PaymentIntent and a Charge can both have separate metadata and description. When a PaymentIntent is confirmed, we create a Charge and that one inherits the PaymentIntent's description and metadata on creation. After that they are completely separate

#

When you update both, you do it on the Charge today, and not the PaymentIntent so they are out of sync

mighty bison
#

ok. All this is starting to make sense. I think the part that was confusing me was this "payment" page. But this page is really just displaying data from both a payment intent and charge? The UI is a little confusing that is displays the metadata on an updated charge, but not the description, but It is good to see that the API is working as you have said correctly. On these updates, I'll just have to start updating both the Intent and the Charge.

near storm
#

yeah it's because a lot of people still use Charges a lot so we kind of try to "unify" in the Dashboard