#erikou_docs
1 messages ยท Page 1 of 1 (latest)
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.
- erikou_api, 2 days ago, 10 messages
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260878056432861296
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
Hi, let me help you with this.
Stripe Checkout and Payment Links are 2 different products. I assume you're using the Stripe Checkout.
The main difference is that Payment Links generate multi-use, non-expiring payment URLs. However, they are mostly created as a no-code solution.
For your use case, you probably need to still use Stripe Checkout, which generates individual, short-lived URLs, but use it a little differently.
What you could do instead, share a link with your customers to your own server endpoint, which in turns generates a fresh Checkout Session, and redirects the customer to it. This way, each customer will get an individual customized Session, but you won't need to worry about expiry.
As a rule of thumb I use, deciding between Payment Links and Stripe Checkout: if you generate it automatically - use Stripe Checkout. But you're not supposed to send Checkout Session URLs in emails etc, but use the approach I suggested above.
Oh ok damn i use Stripe Checkout to send checkout Session URLs in emails ...
the issue is we don't have server endpoint since it is a desktop software and how our architecture is made
๐ taking over for my colleague. Let me catch up.
In that case, you could probably adapt Payment Links for your situation.
with Payment Links will i know whenever i send Urls by emails, a status that will told me that customers made the payment ? without using webhooks
you can always see on the dashboard but other than that no not really
PaymentLinks is a no-code version to create Checkout Sessions