#lord-elements-load
rich bone
I don't think we have any specific guidance on this - what issues are you running into?
final root
basically I can't input into them for a bit. They feel so slow currently and it is especially bad with the ach linking modal
rich bone
This is with PaymentElement, right?
final root
Yep but I have them separated into card number, card expiry, cvc
rich bone
Do you have a site I can take a look at? Just want to see if I can see the slowness for myself
final root
yes one sec
well it seems to be going faster today
it could have something to do with the fact it is in an iframe when I'm testing it since it's going to be embedded
quick dewBOT
fiery night
So you're not using PaymentElement at all right? You're using the legacy CardElement?
lord-elements-load
I can type in it near instantly after load
final root
I guess so maybe?
<CardCvcElement
options={{
style: {
base: {
fontSize: '15px',
color: colors.secondaryColor,
fontFamily: 'IBM Plex Sans, sans-serif',
},
invalid: {
color: '#fa755a',
},
},
}}
/>
I didn't realize it was legacy
I wanted my inputs on separate rows so I used these
final root
I can type in it near instantly after load
It's definitely a lot quicker idk what changed. I still would rather not need to wait at all though you know?
Is there some type of prop I could check to leave it loading unitl it is ready?
The view I mean
or some way to make the separate elements load concurrently rather than sequentially?
fiery night
https://stripe.com/docs/js/element/events/on_ready there's a ready event you can use and only show the UI after this is ready?
final root
oh sick that is way helpful with helping me show loading or not thank you
Is what I'm using legacy code?
fiery night
Kind of. We do recommend using PaymentElement instead https://stripe.com/docs/payments/elements
final root
am I able to customize that to the same degree though?
The whole reason I went with these separate elements is because it let me organize them how I wanted them
fiery night
Not exactly but our element is drastically better overall, supports many payment method. We spent years designing and building this 🙂
final root
should i just bite the bullet and go with that then? I just really like how simple I'm able to make the credit payment view
this is for nonprofit donations so fraud is going to be a really minor issue and goal is to have as little friction as possible
is there a way to hide the tabs at the top and keep my own custom button the bottom by chnace?
fiery night
Up to you really but yes I would absolutely go with PaymentElement if it were me 🙂
And no you don't want to hide tabs, that's one of the biggest upsides of that element: we handle all existing payment method for you including Google Pay and Apple Pay
final root
alright just not wanting to overcomplicate things :). This is sounding pretty good tbh. Am I able to hide specific payment methods? I like my current bank flow and don't want that on the payment element
fiery night
you control all payment method types in your Dashboard so yes you show the ones you want
final root
sweet thank you. I'm going to give this a whirl and see how it goes!
fiery night
amazing!
final root
can we keep this open for a bit in case I have more questions so I don't need to start a new thread?
fiery night
It's simpler to open a new one since your question(s) will be about PaymentElement. Step 1 would be really to follow https://stripe.com/docs/payments/accept-a-payment-deferred?type=payment since you're doing donation