#krustyflakes-stpCardFormView
1 messages · Page 1 of 1 (latest)
Hey, meant to message before that I am looking in to this. I am still looking in to this. Will get back soon
Thank you for your patience, you should use the STPPaymentCardTextField instead which is not a multiline card input field but a single line one, but you can disable postal code field on that with postalCodeEntryEnabled
https://stripe.dev/stripe-ios/docs/Classes/STPPaymentCardTextField.html#/c:@M@Stripe@objc(cs)STPPaymentCardTextField(py)postalCodeEntryEnabled
Oh wait there may be something more
On a separate note, I was looking into the sample code and saw a credit card form instantiating the stpFormView, it gave flexibility for customization and allowed to hide country field, do you know if following this approach retains PCI compliance
I was looking into the sample code and saw a credit card form instantiating the stpFormView
can you share a link?
modifying the pre built UI does compromise PCI compliance technically
also can you try something for me, in your STPCardFormView constructor, do you get the chance to pass an argument for postalCodeRequirement ??
We do want to allow postal code
Product was looking into hiding
It but the stpCardFormView minus the country is exactly what we need
So we might either keep it with the country or look into creating our own instance of stpFormView with the specifics we need
Is the PCI compliance is not an issue
If the*
Ohh thanks you
not recommended to modify STPCardFormView or roll your own UI
so really you want to use STPPaymentCardTextField instead as an alternative
Can you tell me about my earlier question in
also can you try something for me, in your STPCardFormView constructor, do you get the chance to pass an argument for postalCodeRequirement ??
Let me find the code
i believe the Code i reviewed was quite old, i just downloaded the UI Examples from your git and all i see over here is CardFormViewController as the final implementation that does not allow field customizations, the code i saw before had field arrays and had the same class name so i assume it was the code pre component release
STPCardFormView*
we have released the form for iOS, Android and web, the product team noticed that the looks were inconsistent, seems like android does not show country, i assume the 3 are very separate implementations
the contructor only allows me to pass style:
they are separate implementations yes though my understanding was iOS and Android should be ~close
give me a bit to spin up my iOS samples and try it out and compare the STPFormView.
but yes I agree that constructor only allows you to pass style and not disable billing collection
oh
those are the out of the box forms
is the second one CardForm on Android? Or CardMultilineWidget?
they are both card form
I don't recall which one is which but they're fairly similar
the android one i believe we added the name fields outside of the form
yes name is outside of CardForm
the difference being the country field
ok firing up my Android Studio and Xcode, which will take a billion years lol
hehe appreciate it
and slow down my machine to a crawl
that is CardForm on Android
and I think what you linked is CardMultilineWidget
which is the "older" version of the card input "split fields" component, before CardForm came around
and it does have Country field
and postal is a separate line
^this is CardMultilineWidget (just added it in my code)
so yes both iOS and Android have a country field in them for CardFormView
and the reason for that is, they change postal code validation based on what country is selected
or hide postal code entirely for countries that don't use postal code
so there's value in keeping them
so for US/CA/UK they show postal and update the validation accordingly
does that help?