#waleed.bin.khalid

1 messages · Page 1 of 1 (latest)

safe joltBOT
upper berry
#

Hi I am using CardExpiryElement and I want its type should be hidden, like input should be hidden while entering

untold quest
#

👋 happy to help

upper berry
#

great

untold quest
#

before tackling this subject, would you mind me asking whether your Google Pay integration is working now?

upper berry
#

No tarzan I have 2 quick things to ask from you, first is CardExpiryElement and second is apple pay. I have tried what you said yesterday but I guess it was not working somehow. I am loading stripe sdk suing header

#

but it is not creating everything on connect account

untold quest
#

I received your ticket, as you contacted https://support.stripe.com/?contact=true yesterday and I was about to send you a response to confirm that it was working as expected.

#

first things first, I will close the ticket and we will keep the discussion going here if you don't mind

upper berry
#

sure sure

#

please do it, no problem. We will continue here

untold quest
#

ok that's done

upper berry
#

great so do you have idea about CardExpiryElement ? how we can hide the input

untold quest
#

let's finish yesterday's issue before going to the new one if you don't mind

#

what's still missing?

upper berry
#

amm ok wait lemme do some things on code side and send you the link

#

to test on your side

untold quest
#

I was testing your website, and for a second there I didn't realize it was in livemode

upper berry
#

yeah before I was in the test mode

#

lemme do it quickly

untold quest
#

just a quick thing, if you don't mind me saying, why are you using PRB and CardElements separately? Why don't you use PaymentElement

upper berry
#

card elements for card payments and PRB for apple pay and google pay

untold quest
#

you can use PaymentElement it will offer you this and more

#

have you seen it?

upper berry
#

yes I have read it. Actually I take the project at end stage

untold quest
#

it's really worth it to do the change

#

what if tomorrow you decide to add another payment method

#

this is really the way to go, and it offers more flexibility and better maintainability

upper berry
#

yes I totally aggree with you and thats the correct way though. But for now I got instructions make existing flow to work and then go to implement more payment methods

#

then I am planning to change it in the next sprint

#

a new sprint for it

untold quest
#

I think this is wasted time

upper berry
#

yes exactly

untold quest
#

you should push back

#

and tell them that Stripe support advised you against doing so

upper berry
#

Okay I can advice this to the PM

#

lets see what they can suggest further

#

I will prefer to do payment Element also

#

Okay so I will suggest them to use paymentElement today and see what happen

#

for now can you tell me about CardExpiryElement

untold quest
#

Can we make CardExpiryElement input type hidden to ensure security in Js
to go back to your original question, there's no security issue with displaying CardExpiryElement

#

that doesn't fall under PCI compliance

upper berry
#

Okay good one

#

can we make it anyway ?

#

because client was desperately want this

untold quest
upper berry
#

ohoo ok great, so I will discuss with the PM

#

to go back to paymentElemet

#

element*

untold quest
#

and I advise not to use it in a modal

#

you have lots of popovers, it's not a good UX