#joelpatrizio_docs
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/1357033049342345348
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐
Currently we don't have a "down-sell" functionality. So the only way to pre-select the yearly option would be if you created the Subscription with the Yearly price.
Which would not allow the Customer to select the Monthly price
I see... Thanks! Would it be better then to have my own UI for the user to select between monthly/yearly, and only then show the Stripe embedded checkout?
What's the best practice here?
It really depends on your business model. We don't have a "best practice" for this situation. But it occurs to me that you might be able to leverage Pricing Tables
That way. you can flag a "Recommended" or "Most Popular" option directly in the UI before the user goes to the Checkout page.
Understood. Thank you, @exotic urchin , that helps.
Great ๐ Happy to shed what ๐ก I can ๐
One last question, not sure if here's the right place though:
How can achieve something like this? https://gyazo.com/524a442b34de4583a200ce26260e8d06
Is this using Stripe Embedded Checkout, Checkout Tables or something else?
That is a custom UI (for the select menu) along wit the Payment Element. It looks like that one is configured only for credit cards but you can use the Payment Element to collect many different types of payment methods.
Fantastic! I wasn't aware of this feature. Thanks again ๐
Sure thing! Happy to help ๐
The Payment Element is our canonical element for custom web integrations. It does require you to build a lot of the logic behind it but it offers a lot of flexibility.
We have a version of our Accept a Payment integration guide specifically for it. If you haven't used the Payment Element before, I recommend starting there.
Got it! So just to make sure Iโm on the same page... this means I can use the same approach to set up a monthly or yearly subscription, right?
You would need to create the Subscription in your integration logic and then use the Payment Element to confirm the latest_invoice.payment_intent
We actually have a very similar integration guide that uses Subscriptions and the Payment Element here