#denjaland-PaymentElement

1 messages ยท Page 1 of 1 (latest)

naive maple
#

Hey, thank you for your kind words! I am not familiar with the displayed languages but I will try to clarify

golden merlin
#

yeah - I just realised I should have changed locale to en ๐Ÿ˜‰

naive maple
#

1/ We currently don't have it as I am aware of. I know we have such a feature on iOS/Android SDK, but not in PaymentElement, unfortunately.
2/ Apple Pay button could be displayed within the PaymentElement, but you would need to verify your domain with ApplePay: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#apple-pay-and-google-pay
3/ That's actually great feedback. I am a bit surprise myself to know Card Element had it. Will definitely forward this back to our team

Securely accept payments online.

golden merlin
#

okay - is 1/ going to be updated though? I kinda expected the nex payment element to abstract this away so that we can indeed get rid of some code on our end ;-). It seems we'll need to stick to the old elements if we want to keep our current feature set ๐Ÿ˜‰

naive maple
#

I will confirm with the team. Did the old Card Element has 1/? I haven't seen it myself

golden merlin
#

no, but the old card element didn't support much - we had to implement bancontact / ideal ourselves as that too wasn't part of payment element.

#

imo payment element should abstract all that away, so that we can indeed get rid of some code on our end

#

so ideally I think that payment element should make it as easy as possible on the user and present the saved payment methods to him/her

naive maple
#

Yes correct ๐Ÿ‘ The whole point of PaymentElement is to support many Payment Method at once and automatically

golden merlin
#

exactly

#

fyi: this is how we did it ourselves prior to paypment elements:

#

that first option is the previously saved payment method on the customer account, which we fetch from you before we display the form

naive maple
#

That looks neat

#

Indeed

golden merlin
#

so yes, would LOVE to move towards payment elements, but I don't want to loose the functionality of having customer payment methods presented to the customer when checking out