#leguflow
1 messages · Page 1 of 1 (latest)
Hello leguflow, we'll be with you shortly! 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.
• leguflow, 22 hours ago, 19 messages
• leguflow, 1 day ago, 16 messages
hi! I don't think we support that overall.
we do have graduated pricing models for Subscriptions(https://stripe.com/docs/products-prices/pricing-models#tiered-pricing) but those Prices are not compatible with PaymentLinks/BuyButtons.
You could build a custom UI instead.
So value based pricing is not at all available for single payments(not subscription/recurring)?
for single payments, no, not at all
Ah okay. 1 more thing, if I include a button linking to a payment page, how would I send some data from the website so I catch it in checkout.session.complete?
Also what happened to my dashboard? It's not like the default layout
if using a BuyButton/PaymentLink, you can't, they're for simple use cases. Instead, create a CheckoutSession on the backend and pass metadata
https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout
https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-metadata
we released a new Dashboard recently
I have actually succeeded at passing data with the buy button on a different project
Just added client-reference-id
Oh okay
ah ok, didn't know you can do that. But of course remember a user can edit that in their browser if they really want to so the value can only be semi-trusted. Probably not an issue most of the time but mentioning it.