#lenny_best-practices
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/1298925914347802725
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi, let me help you with this.
We generally don't recommend showing Stripe Checkout in webview. Why don't you want to use Mobile Payment Element on mobile?
We're looking for the best/simplest solution.
Our back end already prepares everything for checkout and then produces the stripe url.
We are hoping to be able to use this in some way with the react native solution if that's possible
The only recommended way to use Checkout on mobile is redirecting the customer out of your app.
Othewise, it's better to use Mobile Payment Element. You won't be able to fully reuse the backend for that unfortunately.
I see ok thank you.
Is Mobile Payment Element the only thing we'll need to look at/implement? Or do we need some of the other guides or features of stripe for this?
Mobile Payment Element uses a lower-level PaymentIntent API that only allows specifying the total amount, rather than a list of Prices.
There's not a lot of backend work (see the guide that I shared), but you will need to calculate the total yourself.
Are you selling Subscriptions?
No, but we will be implementing a cart system soon. At the moment the user can only pay for one item at a time
Yeah, then using PaymentIntents should not be a lot of work. Please go through the guide, and I will be happy to answer any questions.
Thank you
Happy to help.