#gaidinx_api
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/1502113057164230807
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hey! do give me some time to take a look at this!
Could you take a screenshot of your emulator/device?
Also, could you send a code snippet of how you implemented the Embedded Payment Element?
Hey! Apologies, i took some time to test this out
This is from our Android SDK docs: https://stripe.dev/stripe-android/paymentsheet/com.stripe.android.paymentelement/-embedded-payment-element/-configuration/-builder/payment-method-order.html
- By default, Stripe will use a dynamic ordering that optimizes payment method display for the
* customer. You can override the default order in which payment methods are displayed with
* a list of payment method types.
*
* See https://stripe.com/docs/api/payment_methods/object#payment_method_object-type for the list of valid
* types.
* - Example: listOf("card", "klarna")
* - Note: If you omit payment methods from this list, they’ll be automatically ordered by Stripe after the
* ones you provide. Invalid payment methods are ignored.
*/
If you take a look at the list of valid types that can ordered, google pay is not one of them
So wallet buttons (e.g. Google Pay) are essentially not driven by paymentMethodOrder. The layout prepends wallets (and related wallets) ahead of the vertical PM list, so you wont be able to achieve orderings such as card first, then Google Pay EmbeddedPaymentElement/PaymentSheet
Hey Teddy, thanks for clarifying. I was hoping there is a way but it sounds not possible to override this behaviour