#sindev_error
dark summitBOT
👋 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/1476930224892411904
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- sindev_error, 13 hours ago, 54 messages
polar viper
note: this works for the web (stripe.js) for the same BE setup
I can attach some code snippet how they do it
cobalt haven
👋 Amazon Pay, Satispay, and Link are redirect-based or webview-based payment methods, so these probably don't work with this approach. Your best option would probably be to use the EmbeddedPaymentElement which provides a component-based approach and should support these payment methods. You can find details on using this here: https://docs.stripe.com/payments/mobile/accept-payment-embedded
polar viper
interesting, I haven't come accross this element
I will try it, but theoretically, after initializing one of them, will it redirect to webview to complete the steps?
And also, I have these payment methods "hardcoded", meaning that I don't know whether my stripe account actually supports them, is there a way to verify through some API if they are eligible?
cobalt haven
Yes, this is a relatively new element. It does technically still use a webview, but it handles the entire redirect flow automatically
With regard to checking if your account supports the payment methods, if you create a Payment Intent with automatic_payment_methods, the payment_method_types array in the response will list the eligible methods. Although if you use the Embedded Payment Element with dynamic payment methods, it will automatically show only eligible payment methods.
polar viper
yes, but there could be a lot of supported payment methods, I want to show and restrict usage of only these three
cobalt haven
You can pass paymentMethodTypes in your IntentConfiguration to restrict to specific methods
polar viper
when creating the payment intent, right?
cobalt haven
This would be on the client-side on the IntentConfiguration object that you pass to useEmbeddedPaymentElement