#Serdar
winter sierra
flat fox
Can you explain a bit more of what you are trying to do here?
inner mason
Yes of course
flat fox
Payment Links will generate a new Checkout Session for each person who clicks on them, so you will likely only have to generate it once per type of thing that you are selling
inner mason
For the start we want to offer one product named "Unlimited".
The product has two prices:
- 10€ per month
- 60€ per year
On our application where the customers have their own accounts we want to offer the price table.
But i did not understand, how i know, that it is that one customer.
So i thought, i need to generate for each price an own payment link for each customer. But that seems not right for me.
I saw, that i could send the customer-id as meta data when generation the payment link.
But is this really the solution?
Hope you understood my usecase @flat fox
flat fox
Gotcha. For payment links I think there are URL parameters to do this but I forget exactly what they look like. Looking for our docs on this
And to be clear, is this your pricing table or the stripe pricing table? https://stripe.com/docs/payments/checkout/pricing-table
flat fox
Yes, exactly. That is a way to assosciate customers via your payment links
inner mason
Okay i understand
flat fox
So you can also set that via the pricing table and track users that way https://stripe.com/docs/payments/checkout/pricing-table#track-subscriptions
inner mason
Perfect
Just the solution i was searching
Thank you so much
One more little question
What about returnUrl? 😄
This is it or?
flat fox
Yes, that is the best way to add an ID to your URL that your server can use to look up customer info