#ucalabrese57
1 messages ยท Page 1 of 1 (latest)
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.
- ucalabrese57, 23 hours ago, 23 messages
that's it yes :)
๐ no that's not possible
You can add metadata though
ok ๐๐ฝ
You can add a client_reference_id URL param when you share the Payment Link. See: https://docs.stripe.com/payment-links/url-parameters#streamline-reconciliation-with-a-url-parameter
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.
Is the metadata unique per-Checkout-Session?
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
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.
The client_reference_id is set on the Checkout Session object when passed as a URL Param: https://docs.stripe.com/api/checkout/sessions/object#checkout_session_object-client_reference_id
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
oh ok ! it seems cool, I will check that, can we customise the client_reference_id ?