#kaki87_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/1395835734765600818
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Oh I thought I would have been able to provide a multiline answer on the last one. ๐
Anyways, I was gonna say : long time no see ! I was actually working on something totally different a few years ago, for which I relied on your dev support team a lot, and I still remember how actively helpful you were and I remain grateful. :)
For subscription, invoices will always be used behind the scene. The main considerations will be between Checkout Session and Payment Link.
Checkout Session is for one-time use (one customer makes one payment. link will be automatically expired after the payment is completed) whereas Payment Link is for multiple use (many customer uses the same link to make payment. The link doesn't expire automatically).
After creating a Subscription either through Checkout Session or Payment Link, Stripe will generate invoice for recurring payments in future cycles
Thank you.
Is there a comparison table of the available features between checkout session and payment link ?
many customer uses the same link to make payment
How are they identified then ?
We generally recommend using Checkout Session if you have customer information in hand, since you're able to create a customer and set it during Checkout Session creation. It'll be easier to identify the customer
If you don't have customer information in hand, your system will need to listen to checkout.session.* event for Payment Link integration to find out the customer information
So, if the identification is based on a Discord user ID, I can pass that as custom props to the Checkout Session (I do remember doing that years ago), but if I use Payment Link then I'll only have information that Stripe asks for (e.g. email, name and address), is that it ?
Hello
The Payment Links do support certain URL parameters such as client_reference_id - https://docs.stripe.com/payment-links/url-parameters#streamline-reconciliation-with-a-url-parameter
You can pass the discord user ID as query parameter which you'd then be able to see on the resulting Checkout Session (that gets created via the Payment Link)
Got it.
So, basically, a Payment Link is mostly the same for all customers except for that parameter if I add it, and the main difference between the two options is Checkout Session involves server-side communication beforehand while the Payment Link doesn't.
Is that right ?
Yup, the main difference is that for the former you're (your server is) making an API request to create a Checkout Session versus Payment Links create the Checkout Session automatically when Customer visits that URL
Alright.
What differences in features are there (e.g. abilities to switch/stop plans, etc.) ?
Not sure what you mean? Checkout Sessions OR Payment Links don't allow you to manage your active subscriptions as such.
These surfaces are just to accept a payment (one-time) or starting a subscription (recurring)
I think I remember using an API that generates a link for a customer to manage their plan, so I would like to know if that feature is available for either or both of these payment solutions, and not just that feature specifically, that's just an example, as mentioned I have a customer who doesn't know at all what features they'd want, so they want me to tell them all features that are available or not available depending on those implementation choices.
Thanks
That's a separate surface altogether
https://docs.stripe.com/customer-management
Any subscriptions associated with a customer can be managed though Customer Portal, doesn't matter how it was created (the only limitations are - https://docs.stripe.com/customer-management#customer-portal-limitations)
Got it, thank you.
Then, is there somewhere an overview of all of Stripe's features that are available with subscriptions ?
This page lists everything I think - https://docs.stripe.com/revenue