#SirJazz
1 messages · Page 1 of 1 (latest)
client_reference_id is an attribute of Checkout sessions, but more generally no I don't think those columns can be further customized.
I'd suggest asking our support team for future Dashboard UI questions: https://support.stripe.com/contact
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
The "DESCRIPTION" is the same as the name. Is it possible to overwrite the value during the checkout progress? If yes, how? I cant find a "DESCRIPTION" value in the checkout session object -> https://stripe.com/docs/api/checkout/sessions/list
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
or: I can succefully save metadata, BUT can I search every of my customers at one? Like search for a specific metadata in my customers database
okay i just tested it. I can add metadata during checkout session and search for the data in my customer database
thank you
Great, glad you were able to get what you needed working!
sorry for bothering you. but as you can see, I succefully added metadata during the checkout process to the user "Kundennummer":
but in my dashboard, the user has no metdata:
You're likely looking at the customer object
the metadata you've provided there would be on the cehckout session object
Those are just two different things, so its expected that there would be no metadata on the customer
Is there a way, to add metadata to the customer, during a checkout session?
There is not, no. You could create/provide a customer ID though, where you set/update that metadata before creating the session
You mean the stripe customer ID, right?
But what happens if the user decides to cancel the checkout process. Then I have non-used dataset in my database, correct?
Correct
Alternatively, you could have a webhook endpoint that updates the customer metadata based on the session metadata following a successful checkout session, if you wanted to do that