#erangalp-elements
1 messages · Page 1 of 1 (latest)
hello @hollow relic! It looks like you're going to need to change your flow slightly and only display the Payment Element on a page where the user is no longer adding items / changing quantities
@bold spoke I'm afraid that's not possible, this is a one-page interaction. For many years it was possible to render the Stripe payment form without needing the amount ahead of time - is this option being deprecated? seems like a massive change
Just for context, I'm representing a connect platform with over 300 connected Stripe merchants which all rely on this functionality
it's not being deprecated so you can continue to use your current implementation
Most of the documentation is being hidden away (I can't find full documentation any more for the individual payment elements)
Also, this means we can't use the payment Elements capabilities for multiple payment methods
Is there no work around for this? why was it decided to require the payment amount up front?
Also, in our interaction, it's quite possible for the merchant to make changes still to their cart after getting to the payment step
there isn't any workaround right now, but i'll pass on the feedback. Is there a particular payment method element which you're looking for? we should still have it somewhere but may take a little bit of digging
Our connect platform serves a world-wide audience - we were looking forward to using elements to simplify integration of local payment methods in many of the countries we support
We integrate with BECS, iDEAL, Bancontact, BACS in addition to card payments and ACH
A few others are in the pipeline
Also PAD
if you need to refer specifically to the previous elements (per payment method), you can take a look at :
https://stripe.com/docs/js/element/other_element
https://stripe.com/docs/js/payment_intents/payment_method
I would really appreciate it if you could take the feedback back to the team regarding this. We've been using Stripe with significant volume for years and this hurts one of our main user flows
yep definitely, there are a few other users who have mentioned this as feedback as well
Thank you
If there was a way to provide the amount / payment intent to the Elements widget just in time for payment, that would work as a work around
Would probably still end creating unncessary payment intents (currently we only create the payment intent after all payment information has been entered)