#balthius_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1387096908031594777
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
Is this metadata that you are going to set or you are trying to collect from the customer?
You can set metadata via payment_intent_data.metadata: https://docs.stripe.com/api/payment-link/create?api-version=2025-01-27.acacia#create_payment_link-payment_intent_data-metadata but this metadata would be per-payment-link not per-customer that uses the Payment Link.
I am looking to collect a uuid that we are using as our trusted customer value
Too many people have been checking out as guests, or using a different email, and it is making payment tracking a headache.
it sounds like, based on the per-payment-link nature described above, that would not achieve the intended goal.
Do you have any thoughts or suggestions for alternative fields I could use to pass that uuid in?
Anywhere that it would be accessible within a webhook? Is there an alternative request I could fire from the success page, perhaps?
Oh if you just want a UUID then you want to use the URL params and a client_reference_id: https://docs.stripe.com/payment-links/url-parameters#streamline-reconciliation-with-a-url-parameter
That comes through the checkout.session.completed Event
Thank you, diving into that now!