__rob1986__

[tiny drum]

Not currently no

[solemn pagoda]

is there a way i can pass it as a hidden field? i just

oh wait is that what i can use meta_data for?

[tiny drum]

What specifically do you want to do?

[solemn pagoda]

i want to pass something that links the user to a user record in my database, i am using the email, but if they change it then the association is broken

and then in the checkout session response, save data in the response against the correct user

[tiny drum]

Maybe client_reference_id? The issue with metadata is it'll be the same for every payment completed via the PL

See: https://stripe.com/docs/payment-links/url-parameters#streamline-reconciliation-with-a-url-parameter

[solemn pagoda]

what if i create the metadata via the api using the create payment call?

[tiny drum]

That's fine if you're creating a unique Payment Link for every payment

But if you want to re-use it for a different payment/customer, then the same metdata would be used

[solemn pagoda]

actually your idea of the client_ref_id value seems easy to implement

its just a url param

[tiny drum]

Yup, so customisable per payment without having to create a new Payment Link

[solemn pagoda]

perfect, thanks!