Ask HN: simplifying credit card forms.
This is 37signal's beautifully simple credit card capture form for Highrise.
http://img.ly/2u8H
I'd like to know how feasible it is to create a form with so few fields. Presumably there are some fraud checks being skipped? Is this something that many payment gateways will allow? Does anybody know of any hacks to remove extra/unnecessary fields from card capture forms?
4 comments
[ 4.0 ms ] story [ 23.2 ms ] threadFor AVS verification, only the zip code is needed. I do get an additional discount on my merchant account if I send the numeric part of the street address, but, designing a form to ask for the street number but not the suite/apartment number for an extra half percent may drop the conversion ratio of the form. At best, you could get some people to enter the numeric portion, at worst, you probably require the two address lines for the billing address on the card.
The gateway I use allows me to specify the fields as optional, hidden or visible for every field, billing/shipping address, notes, etc. We can also submit a form to our gateway that can be used. However, we maintain a secure certificate and use our own forms to send the data and get back a recurring billing token from the gateway. That allows us to maintain a bit more control over the sales process.
Another way to make it easier for the user is to auto-type the card. This table illustrates which card types match which patterns (e.g., cards starting with 4 are visas. If the user types in a 4, you can auto-select the card type, and save the user a step): http://www.merriampark.com/anatomycc.htm
Aside from that, if you already have the user's information in a database (regular info, not credit) -- you can prepopulate some of the fields (first name, last name, zip), and just give them a button for 'not me'.