denjaland-elements | Stripe Developers | Page 1

rose cosmos Mar 25, 2022, 10:06 AM

#

why do you require it a second time when calling confirmPayment()
we need the cardholder/payment method name, which might not be the same as the customer-level name

#

So it seems I really need to provide the redundant data in the confirmPayment() on the js SDK?
I would say yes

winged sage Mar 25, 2022, 10:11 AM

#

okay, but it might not be the same. Not sure why you don't fall back to what you have on the customer - if the payment fails because of a validation by the acquirer, you can still ask for it then, no?

#

payment elements don't even prefill the data from the customer for the created intent 😦

rose cosmos Mar 25, 2022, 10:12 AM

#

the name is not validated by the issuer

winged sage Mar 25, 2022, 10:12 AM

#

exactly - so why do you need it?

rose cosmos Mar 25, 2022, 10:12 AM

#

collecting the name is just so there's more context and information to help in the case of a dispute or detect fraud

#

it's an opinionated default that it's a useful thing to collect

winged sage Mar 25, 2022, 10:13 AM

#

I feel like I'm getting more overhead from the payment elements like this to be honest

#

at least the elements should prefill data from the account, no?

#

now the user has to enter the data

#

or I as a developer need to do something additional to prefill what you already have 🙂

rose cosmos Mar 25, 2022, 10:14 AM

#

there are a lot of things that "should" work that we might not have implemented yet!

#

but yeah as far as I know you can't prefill anything into the PaymentElement

winged sage Mar 25, 2022, 10:14 AM

#

😦

rose cosmos Mar 25, 2022, 10:14 AM

#

you can disable fields instead and pass the information directly, that's about it

winged sage Mar 25, 2022, 10:16 AM

#

For me, even though the intent is definitely good, the payment elemens seem to be a step back functionality wise - it feels as if it was released too early. But again: like the direction you're potentially moving to

rose cosmos Mar 25, 2022, 10:16 AM

#

winged sage I feel like I'm getting more overhead from the payment elements like this to be ...

to be clear, it's our default because it's a drop in solution to quickly take payments across a variety of methods but there are many use cases where it might not suit, and you can switch to using the lower level split elements in a more custom form instead, you don't have to use it

winged sage Mar 25, 2022, 10:16 AM

#

I know that...

rose cosmos Mar 25, 2022, 10:16 AM

#

well it's not a step back, since nothing was really removed

winged sage Mar 25, 2022, 10:16 AM

#

I agree with that, but you just have quite some missed opportunities...

rose cosmos Mar 25, 2022, 10:17 AM

#

you have exactly the same functionality you always had, but now there's additionally this options

#

I mean I completely agree with you

winged sage Mar 25, 2022, 10:17 AM

#

saved payment methods on the customer account are not presented to the user checking out for instance

rose cosmos Mar 25, 2022, 10:17 AM

#

look at the other thread Valentin-element for instance

winged sage Mar 25, 2022, 10:17 AM

#

aha - will have al ook into that one as well

rose cosmos Mar 25, 2022, 10:17 AM

#

everything is under development so will get better over time!

#denjaland-elements