#Wyrran - Confirm Card Payment
twilit plover
Hey! Sure. I think pi_3LQCioFnaZsSkALk0kQQYxch should have the metadata in question. I did not yet confirm that one though...
plush sky
Yes I do see two donation_ metadata keys
twilit plover
Here is the one I confirmed: pi_3LQCioFnaZsSkALk0kQQYxch
plush sky
And you are saying these are not returned in the Payment Intent that the Promise from .confirmCardPayment resolves to? I can do some digging but I'm pretty sure we restrict the amount of data returned due to security concerns with the front-end
twilit plover
OK to post a screenshot of the response from JS here?
plush sky
As long as your server-side keys are not shared it should be fine
twilit plover
There is the paymentIntent's clientSecret but I assume thats specific to that PI
that's what the promise resolved with for result.paymentIntent
i wonder if its because we're on a pretty old API version...
plush sky
But the Payment Intent object itself does have metadata
twilit plover
right, just not included in the response from confirmCardPayment
plush sky
Yes I'm double checking that but my hunch is that users are storing data in the metadata they don't want exposed on the client side
twilit plover
I see. I know the docs say not to store sensitive data in there.. but it also says its not shown to the client, so I could see that explaining why its not returned
plush sky
Yes, there we go. If your front-end needs this information you could always return it yourself from your server.