#lexumi_best-practices
gray carbonBOT
👋 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/1346084886741647440
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
untold bay
... pain.
Is there any way to pass a email to an existing payment link? And also like a metadata like "web" or "app". that then will be shown in the customer.subscription.created body?
glass thicket
No you can't
PaymentLink is for multi usage
You probably want to use Checkout Session, which is per customer
untold bay
Hmm you mean the event checkout.session or is there a way to create a checkout session?
glass thicket
No I mean creating a Checkout Session:
https://docs.stripe.com/billing/subscriptions/build-subscriptions?platform=web&ui=stripe-hosted
gray carbonBOT
digital apex
Is there any way to pass a email to an existing payment link?
You can via URL params: https://docs.stripe.com/payment-links/customize#customize-checkout-with-url-parameters
But you can't use an existing cus_xxx object ID without Payment Links. PLs will default to creating a new Customer object every time when required, so you may end up with duplicates if you're creating them prior to the Payment Link too
untold bay
> Is there any way to pass a email to an existing payment link?
You can via URL ...
cool, that seems to work, is it also possible to disable the input for the email via the url param?
digital apex
Not today I'm afraid 😦
untold bay
ahh okay thanks to :) Well have a look at the checkout session and then see what works best :)
digital apex
Yeah the customer_email param on Checkout Session prefills and 'locks' it
No equivilant on PLs today
untold bay
Ye just saw it, were gonna build our flow with checkout sessions then :)
Thank you guys for the help, much appreciated :)