#patrick.wierer.r2o
zinc dome
potent mulch
Hi 👋 are these one-size-fits-all links? Or are they customer/transaction specific?
quick hearth
Hey,
those links are transaction specific, meaning we want to generate Payment Links with dynamic amounts (not known ahead of time and not product related).
Example:
- Customer receives invoice for Product A that costs 300€
- Customer only pays 200€
- At some point we want to generate a Payment Link for 100€, to cover the remaining balance.
So even if I would define "Product A" in Stripe's product catalog with a Price of 200€, I could not use a Payment Link, since 100€ is not a valid Price yet.
So I was wondering if I could create a generic Product in Stripe called e.g. "Payment" and every time there is a "new" price not yet known to Stripe, we would create it via API before creating the Payment Link
potent mulch
I would recommend looking at Checkout Sessions, they are better for transaction specific links (Payment Links are meant to be usable by all customers), and they allow you to provide price_data adhoc to create Price objects on the fly rather than requiring you create those first:
https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout
https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-line_items-price_data
quick hearth
Ok thanks, but behind the scenes there would still be tons of Price objects created in Stripe.
So basically there seems to be no way to go around that?
potent mulch
Yeah, all of our hosted payment surfaces are built on top of Products/Prices, if you didn't want those you'd need to build your own page using Payment Intents and likely our Payment Element.
https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
quick hearth
Ok, thanks for clarification.
Last question, do you know are there any limitations on how many prices can be defined per product?
potent mulch
There aren't
quick hearth
Thanks Toby, much appreciate the time you spent helping me.