mvnsur

[magic flume]

hi! I don't think that's really a use case PaymentLinks are well suited for.

The better approach would be to generate CheckoutSessions dynamically in your own code, and you can check stock in your code and decide to not generate a session when you don't want to let someone pay. https://stripe.com/docs/payments/accept-a-payment?platform=checkout

[bleak wave]

Is there a limit for CheckoutSessions ? Can I automate these CheckoutSessions so they generate from the date I input ?

Thank you for your quickly reply by the way, I value your time @magic flume

[magic flume]

there's no limit

I'm not sure what you mean by "they generate from the date I input" really

the way it works is a customer visits your website and presses a button or something. On your server, you handle the button being pressed and run code, that code can generate a Stripe CheckoutSession and redirect the customer to that in order to pay. Your code can optionally not do the redirect if you don't want the customer to pay

[bleak wave]

"On your server, you handle the button being pressed and run code, that code can generate a Stripe CheckoutSession and redirect the customer to that in order to pay" Could you please reformulate/rephase this

[magic flume]

not sure how I could.

are you a web developer?

[sand flint]

Hi! I'm taking over from my colleague. Please, let me know if you have any other questions.