#itchtherightspot_paymentlink-vs-checkout
stark graniteBOT
👋 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/1314297962003693701
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fair flume
Hi 👋
We don't focus much on the no-code solutions since this server is for developers coding integrations with Stripe APIs. That being said, what do you mean in terms of
Dynamically creating payment sessions via my backend for each transaction.
Do you mean a static Payment Link vs a Checkout Session?
tawny gazelle
Oh my fault and correct Payment link vs Checkout session
Mind you my application is a monthly subscription
fair flume
Okay so the Payment Link is a static UI that is not very customizable for individual customers. This can be great to get up and running with a set of sensible defaults but, if you find yourself wanting to perform per customer customizations, then Checkout Sessions are what is needed.
tawny gazelle
Ohh got you. One last question
If I decide to go with static UI with a generic payment link from my dashboard. I wanted to confirm: Can I pass metadata into this static UI setup? Specifically, I’d like to associate custom data (like user IDs) with each transaction.
fair flume
You can add the URL parameters we document here: https://docs.stripe.com/payment-links/url-parameters
tawny gazelle
bet thank you for the help
fair flume
Happy to do it 🙂
stark graniteBOT