> Nothing beats tapping/swiping your card at a physical terminal. Zero typing required. What does tapping mean? And in what countries do you swipe nowadays? I also need to type in my pin so wouldn't say zero typing.
The anatomy of a credit card form
41–50 of 129 posts
Re: The anatomy of a credit card form
#42> Nothing beats tapping/swiping your card at a physical terminal. Zero typing required. What does tapping mean? And in what countries do you swipe nowadays? I also need to type in my pin so wouldn't say zero typing.
Re: The anatomy of a credit card form
#43> Nothing beats tapping/swiping your card at a physical terminal. Zero typing required. What does tapping mean? And in what countries do you swipe nowadays? I also need to type in my pin so wouldn't say zero typing.
Re: The anatomy of a credit card form
#44> Nothing beats tapping/swiping your card at a physical terminal. Zero typing required. What does tapping mean? And in what countries do you swipe nowadays? I also need to type in my pin so wouldn't say zero typing.
Re: The anatomy of a credit card form
#45> Nothing beats tapping/swiping your card at a physical terminal. Zero typing required. What does tapping mean? And in what countries do you swipe nowadays? I also need to type in my pin so wouldn't say zero typing.
Paywave / Paypass / Tap & pay / whatever your country or bank calls it. With NFC payments you don't have to type a PIN when using a card. Although you can use extra PIN when paying using your phone.
Re: The anatomy of a credit card form
#46UK banks sometime sends payments to a separate verification page which either returns automatically or asks further security questions. I don't think this form is going to work with those banks. A couple of takeaways: 1. This has been a standard problem for twenty years now. Why are designers and developers still having to reinvent the wheel? 2. Reinventing the wheel is really hard. If you want to support internation…
Ahh, 3D Secure/Verified By Visa/MasterCard SecureCode.
It really needs to die right now. Basically it teachers consumers to fill in random iframes on merchant sites.
And the fact that the card industry thinks 3D Secure is secure or in any way a good idea is why they'll never make standardised forms.
Re: The anatomy of a credit card form
#47> Is this form safe and secure? We just add a lock icon, sure it's secure. Lock means secure, right? Joke aside sure, it's not the designer's fault. Every time I fill out a credit card form without even pulling out my card I cringe. Why do I need a physical credit card for this, I just authenticated myself with only something I know and not something I own and I know. And my authentication credentials are just writte…
With Apple Pay, I now get iOS notifications for all the purchases on my Amex card.
Barclays now let me use their iPhone app as a software 2FA (bank-specific hardware 2FA needs to die—not being able to check your online banking at the office or whatever is a major PITA).
Both Barclays and NatWest have TouchID in their iOS apps.
I'm hopeful that mobile might lead the banks and card issuers to turn this ship around and make things less crap.
Re: The anatomy of a credit card form
#48From a primarily selfish perspective, I would like developers to think about password managers like Lastpass etc. An enemy of password managers is for example the 4 boxes with 4 digits, as well as form-reloads on changing card types.
https://twitter.com/BritishGasHelp/status/620956147680432128
British Gas have JavaScript that actively prevents you from using LastPass because "as a business we've chosen not to have the compatibility with password managers".
I want to be a fly on the wall at the meeting where they decided that making security worse was a good idea.
Re: The anatomy of a credit card form
#49Earlier quoted context omitted.
I don't get the name and zip code requirements, is that standard in some countries? I only ever encounter the "Name on card" when shopping on US and UK sites. Danish online stores don't care. Is the name and zip actually used as part of a validation process? If not it should just be left out.
From the article: "As an extra security measure, we have to ask customers for the ZIP code associated with their card. There is a trade-off here: adding extra inputs to the form can increase bounce rates, but by adding it, our business is more secure and less prone to fraud."
I've implemented card payments on multiple occasions, but not once have I seen a credit card processor that offered to validate the zip code.
Unless the name and zip can actually be sent to the credit card processor, and they have access to that information based on the credit card number alone, I don't see the use. Which brings up names, how fare of can your name be? I know plenty of people who wouldn't think twice about leaving out a middle name that they hate.
Re: The anatomy of a credit card form
#50> “My card number has spaces. Do I enter my card number with spaces, or without?” To solve for this, we limit the input values to numbers only, so 0–9. So if a user types a space, it does not register and it does not affect the number format. They failed, at the most important part of the form. The correct, i.e. the most user friendly solution is, obviously, to allow spaces (and optionally other characters, like "-,.…
jquery.payment from stripe[0] helps with formatting and automatically adjusts it to the card type as you type in the numbers. It does seem to ignore spaces though, but it adds them for you as you type. If you type in a VISA number it will format it as XXXX XXXX XXXX XXXX, but if you type in AMEX, it will format it as XXXX XXXXXX XXXXX. Pretty neat if you ask me. You can try it here http://codepen.io/anon/pen/WvygyO V…