Hacker News new | ask | show | jobs
by jasonlotito 4700 days ago
> Citation needed.

Unfortunately, I've never published anything to any official standard. I can only go by my experience. That experience involves transactions north of $100M.

> Any other credit card form I've seen does nothing to convert either -- and it's not it's job

Perhaps I worded it poorly. However, a CC form's job is to convert a potential customer into a paying customer. Just because you've entered your CC details does not make you a paying customer. You'd be surprised as the number of people who do enter information, and then never actually complete the transaction. It it's a recordable amount.

In the end, a credit card form that creates friction will cost sales. The more friction, the less sales. The amount of problems with this setup will stop sales from going through, even if just the bugs are fixed.

> Most of the objections are dead simple to fix

They aren't objections as much as they are a report of what is wrong. Consider them a list of problems that need to be addressed.

> and address nothing inherently wrong with the core idea.

Correct, the idea is fine, and should be explored. Keep in mind, this isn't the first time I've seen someone use a credit card layout as a form. The CVV on the back is new, but than I'm going to say that's a bad idea the way it's implemented.

Anyways, I already replied to the author of the form, and made it clear I'm not arguing against his attempt. Hell, I applaud him. I just wanted to share my experience because that is what's needed.

1 comments

Being a little less "blunt" may help a bit. I generally don't start my criticism off with "So..." followed by a list of everything that is wrong with it and then a "THIS WON'T CONVERT" in caps.

I think more likely the reason is people with "north of $100M" in transactions are scared to try something new on their form. When there form clearly works fine as it is. But that doesn't mean exploring new methods is a bad idea. I know a lot of people who are still unsure of what a CVV is. And having a replication of their credit card so they know exactly what goes where would work very well.

Anyways just my 2c's

I was trying to be clear. Judging by the OP's response, I think I was successful. But agreed, I could have avoided the So… part. There was really didn't mean anything by that part. Mea culpa.

> I think more likely the reason is people with "north of $100M" in transactions are scared to try something new on their form. When there form clearly works fine as it is.

That's actually far from the truth, at least in my experience. You are constantly looking at how to improve the experience at every level. Between the amount of time a person spends entering in each field, to the errors they get back, and even where the person lives. Everything is scrutinized. Not everything matters, but you keep looking.

> I know a lot of people who are still unsure of what a CVV is.

Yep. And there are ways you can go about resolving that. Hiding the field from the start is a bad idea. There is nothing to suggest that you couldn't also display the back of the credit card below the front.

The most important thing you can do when designing something like this is get real feedback and data. Just because it looks nice doesn't mean it will help.