#TC - metadata
1 messages ยท Page 1 of 1 (latest)
Hi ๐
The screenshots are not really useful here but if you could provide the Request ID (req_XXXXX) that would be helpful
Hii @neat wasp ๐
Also, metafield isn't a parameter. metadata is. I'm wondering if that might be an issue
ohh where do I get the request ID?
I'll try it now!
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
this is my request ID: req_ypZW7r6HFOwNOb
Thanks, looking
also I've tried change the parameter from metadata to metafield, it doesnt work
Okay so here's the issue I am seeing. The way your curl command is structured you are passing in parameters as query params. For POST requests you need to pass it as body data -d
Take a look at the code snippet on the right in this doc:
https://stripe.com/docs/api/metadata?lang=curl
Hi @neat wasp
I've restructured my PHP cURL switching from parameter to body data. The result still the same.
I can pass the
"metadata": {
"invoice_number": "9000"
},
I simply want to make it visible on the transaction metadata. Is this possible?
Yes, absolutely you can. That is the purpose of the metadata parameter. Can you share the latest request ID?
Hmmmm that's the /confirm call on a Checkout payments page.
Could we make it shows up here?
I don't know what you are looking at there.
we want to simply make it more visible in the payment page. at the moment, the only way to see it is in the event data show as a json format. is it possible to configure the payment page to show/highlight specific data?
What do you mean "in the payment page"? I don't know what record you are looking at. Do you mean in the dashboard? If so, what is the object ID for the thing you are looking at?
What are you looking at? Show me the whole screen please. Black out any sensitive data
Okay, Are you looking at the Checkout Session or the Payment Intent?
we believe its the payment intent
it has all the payment details
this appears to be the id for it
pi_3LcYnkBXMg7Moo790wmx6RHh
Yes, thats a Payment Intent. All Payment Intent IDs start with pi_XXX
So, as our docs say, the metadata parameter is copied from the Payment Link to the Checkout Session to help tracking. But that is not automatically copied to the Payment Intent.
i see, is there a way to get it to copy in the payment intent?
You can build that into your integration by listening for the checkout_session.completed webhook and copying the metadata from the Checkout Session to the Payment Intent.