#derjanni - Elements
1 messages · Page 1 of 1 (latest)
yes, I would like to render my own payment method list and just change the Payment Element accordingly.
Gotcha. That's not currently possible, the Payment Element renders its own list.
:\
Problem is, I need to render offline payment options as well (cash) and it looks completely off if the blinky blinky stripe tabs are there as well.
Was thinking about using the rest api, but that means I need to keep a list of all banks for eps manually
But I guess there's no way around that then.
I'm just hesitant to keep and track a list of all Austrian banks, that's why I wanted to use Stripe Elements.
Gotcha... yeah, there isn't really a unified way to do this right now, but I can pass this feedback on to the Payment Element team.
Yeah, I guess the Payment Element team has got a lot of homework still to do. The whole thing doesn't look production ready. Sorry, that's just my honest feedback after spending days on it now.
Thanks for the feedback, I'll pass it on!
The themes make no sense whatsoever, some of the documented functionality is not present at all and it is loaded with animations that serve absolutely no purpose.
I spent 3 days on it and am going to abolish it now, it is not production ready in my opinion and I think the documentation should not try to push users into using it.
Sorry it's not working out for your use case!
I would be okay, if it wouldn't have worked for my use-case before 👀
What do you mean?
I interpret the documentation as such that developers should consider migrating to the Stripe Elements and not implement each payment method individually as before. My assumption was that it comes with the same flexibility and let's be honest it wouldn't be that hard to provide either.
Sorry, I'll stop bothering you now and implement each payment method individually again.
We do recommend the Payment Element as the default integration, and it works well for most use cases, but there are always exceptions. We'll be working to improve the Payment Element quite a bit over time, but it sounds like it's just not a good fit for your specific use case quite yet.
I think the Payment Element was built for people with extremely limited customization requirements which is awkward, because the 3rd party payment authorization (like EPS, Giropay) requires such complexity that it's not really suited for people with limited customization requirements. It's a bit of an in-betweener between the hosted payment page and the individual implementation of each method. Really weird, I think I just stepped into some sort of trap there.