#ucalabrese57

1 messages ยท Page 1 of 1 (latest)

quick plumeBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

viral dagger
#

hi there!

#

you mean you want to prefill some of the inputs on the payment page?

quick plumeBOT
young laurel
#

that's it yes :)

alpine pollen
#

๐Ÿ‘‹ no that's not possible

young laurel
#

Or if we can add some data that will be not visible to the customer

#

for tracking

alpine pollen
#

You can add metadata though

young laurel
alpine pollen
#

This allows you to reconcile the Checkout Session to a certain customer, then you can later update the relevant PaymentIntent's metadata that is related to that Checkout Session if you want to add metadata after the Checkout Session is completed.

young laurel
#

ok ok this is cool

#

but we cannot add metadata with GET or POST though

#

can we ?

alpine pollen
#

Is the metadata unique per-Checkout-Session?

young laurel
#

no it's before we go the checkout

#

and transfer a traking id to the checkout page to trace from where the customer come from

#

So I want to add this traking code in the Stripe payment or Session if it possible

alpine pollen
#

Yeah so the way to do that is what I shared above, you can't do it via a GET or POST request -- that would store the same metadata across all Checkout Sessions/PaymentIntents that are created from that Payment Link.

young laurel
#

oh ok ! it seems cool, I will check that, can we customise the client_reference_id ?

alpine pollen
#

It is a string

#

So yes

young laurel
#

ok ok, cool thank you very much :)

#

have a good day ! :)