#TC - metadata

1 messages ยท Page 1 of 1 (latest)

neat wasp
#

Hi ๐Ÿ‘‹

#

The screenshots are not really useful here but if you could provide the Request ID (req_XXXXX) that would be helpful

shy yew
#

Hii @neat wasp ๐Ÿ™Œ

neat wasp
#

Also, metafield isn't a parameter. metadata is. I'm wondering if that might be an issue

shy yew
#

ohh where do I get the request ID?

neat wasp
shy yew
#

this is my request ID: req_ypZW7r6HFOwNOb

neat wasp
#

Thanks, looking

shy yew
#

also I've tried change the parameter from metadata to metafield, it doesnt work

neat wasp
#

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

shy yew
#

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?

neat wasp
#

Yes, absolutely you can. That is the purpose of the metadata parameter. Can you share the latest request ID?

shy yew
#

sure.
req_CHHXtEew7TE949

#

thanks

neat wasp
#

Hmmmm that's the /confirm call on a Checkout payments page.

shy yew
#

ohh sorry

#

req_whcXFexegKV5OY

neat wasp
#

Looks good to me

#

In both the request and the returned body

shy yew
#

Could we make it shows up here?

neat wasp
#

I don't know what you are looking at there.

shy yew
#

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?

neat wasp
#

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?

shy yew
#

sorry, yes we were referring to the dashboard.

#

how do we locate the object id?

neat wasp
#

What are you looking at? Show me the whole screen please. Black out any sensitive data

shy yew
neat wasp
#

Okay, Are you looking at the Checkout Session or the Payment Intent?

shy yew
#

we believe its the payment intent

#

it has all the payment details

#

this appears to be the id for it

#

pi_3LcYnkBXMg7Moo790wmx6RHh

neat wasp
#

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.

shy yew
#

i see, is there a way to get it to copy in the payment intent?

neat wasp
#

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.