#xqprtzcv-cardelement-appearance
1 messages · Page 1 of 1 (latest)
xqprtzcv-cardelement-appearance
Let me have a look
@graceful igloo what exactly are you trying to do that isn't working?
I am trying to make the text and boxes bigger. I believe that none of the style are showing up in my example though.
what does that mean "the text and boxes"?
Like when somone is entering a card, I want the text of the card number to be larger.
I think you're looking at the wrong doc
You're using CardElement which is quite old but you are using the newer PaymentElements' appearance API which won't work. You need to use the older Style API like documented here: https://stripe.com/docs/js/appendix/style
Example jsfiddle: https://jsfiddle.net/h41wfpvy/
Excellent, thank you!
Is it recommended to use the payment element rather than the card element?
yes PaymentElement is way more powerful, I'd definitely recommend switching to it
Is it possible to hide all the wallet options in the payment method?
*payment element
I saw that, but I am still seeing "Card" and "Cash App Pay" at top
sure, CashApp Pay is not considered "a card wallet".
How are you integrating? There are dozens of ways to do this so I need more context
Okay so you created a SetupIntent with your code, it defaults to all payment methods activated in your account. So you need to turn those off in your account's Dashboard if you don't want them. But really you shouldn't do that and offer those to increase conversions
If you really only want cards then when you create the SetupIntent pass payment_method_types: 'card'
but really I discourage doing this
If someone uses a wallet with the payment element, does that get assigned a payment_method id (just like a credit card does)?
your use of the word wallet confuses me
do you mean ApplePay and GooglePay or something else?
Yes, apple pay, google pay etc.
On our site, we are saving payment methods (payment_method ids) for future use if the user opts in to that, and I was wondering if apple pay and google pay could be saved for future use, or if the user would have to click that button every time.
you say "etc." but what is "etc." about? It's important to align on the right vocabulary here
ApplePay and GooglePay are special types of card PaymentMethods. Link, CashApp Pay and others are their own separate PaymentMethod types
Ok, so let's just say apple pay and google pay
Then yes they will behave like a normal card in your code and in our API. They come with restrictions though for ApplePay specifically on session where you have to re-collect card details again as a separate PaymentMethod
See https://stripe.com/docs/apple-pay?platform=web#recurring-payments for more details
OK, thank you