#stripe_connect_platform-PaymentElement
1 messages · Page 1 of 1 (latest)
For the second question, it's only one price. You can show the price selection on your page before getting to the Payment Element.
Ah......OK, so it is a lot like Stripe Checkout.
On the first one, that is correct. It would occur on the load
Is there an element we can add to Stripe Elements so the end customer can select from a collection of Prices????
That is our challenge now with Stripe Checkout. I thought Elements might solve
Closer to a shopping cart
There is not a way other than building this on your end. The Payment Element lets you accept up to 18+ payment methods with a single integration. It provides an embedded and customized payments experience.
Got it but if I have SaaS plans Starter, Growth, Enterprise and want the customer to choose one and then pay? It would need to be in a form - we can write the code for our customer to embed but we need a radio or checkbox collection or a dropdown or something no?
I started off with Payment Element, but can we do something with Card Element? Or......do you have any type of Price selection Element - that is what I was imaging.
imagining
There is not currently.
What do people do who are using Elements? I am missing the first step. Like we can get the list of three Pricing plans and make some kind of selection (radio buttons or dropdown) and then when chosen we create the payment intent and display the appropriate form - is that the flow? Can you explain how that first step is typically done?
I was hoping you had the CSS for a selection element but we can do that part I imagine.
Is there a working example of Stripe Elements - not just the form but something where you take that first step of choosing some Price/Product first?
Let me see if I can find a sample real quick
Use case we have a hard time with is >3 Products since you can only embed so many Checkout buttons before it looks pretty strange on a web page. 😉
It's OK. I think we are going to just stick to Stripe Checkout and Payment Links since we would need a button for each price anyway with Payment Element. I was imagining passing a collection of price_ids that appeared in a dropdown or something....Let me think on this one.