User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The name on card is not used when processing credit card payments. Paypal does not ask the user to enter the name on card when saving a card to the "wallet", while does.

The benefit of asking for it is that the user can feel more "secure" because we are asking for more details. With out the name on card field, the user might think: Hey, does that mean anyone can just grab my card number and the expiration and they can use it? This is taking into account the fact that CCVs and Address Verification can be turned off by the merchant.

The obvious advantage of not having the name on card field is that it's faster. 1 less field to fill in is always better when it comes to form design.

Should we ask for the name on card when users are paying/storing credit card details?

As an aside: We do not plan to store any of the card holder details and billing addresses in our system at the moment (that will happen when be grow to be a huge company and that becomes cost effective and feasible ;)). These will all be stored with the payment processor and details will be passed using direct post/transparent redirect, so that they never ever hit our server.

share|improve this question
Doesn't Paypal use the name on your account for the name, even if you don't enter it for each card? – JohnGB Dec 27 '12 at 6:02
One more example of placebos in UI design – Erics Dec 27 '12 at 7:27
@JohnGB: Yes, paypal uses your account name. But the name on card can be different. I have seen cases where cards are issued to Mr John Z Smith where as in paypal, you can have John Smith as the account name. I have also made transactions (paypal checkouts) where I enter the card on the spot and used a card that did not belong to me and there wasn't anyway to fill in the card holder name. – F21 Dec 27 '12 at 7:36
I do believe Amazon asks (and store) for a cardholder name not only for security reasons but also to easily distinguish one card from another since they show up just 4 last digits of the card number: it's easy to remember the name than expiration date, etc, if you have several cards in your family associated with a single amazon account. – alexeypegov Dec 27 '12 at 7:55
@alexeypegov: That's a good point :) – F21 Dec 27 '12 at 8:26

More often that not, what you have to store is determined by your payment processor and so you usually have very little say in the matter. When you do, the general rule for security is to only store what you absolutely have to. The less information you store, the lower your security risk, and the less information customers have to enter (in general) the better your conversion rates.

So if you don't need the name, or it provides no additional benefit from you provider, then don't require it. However, I know of at least one case where requiring more information on a form resulted in a better conversion (although this wasn't for payment details). So, as always, you should test this hypothesis with your customers.

As an aside, I prefer to always use a payment provider that stores any information that is needed. That way I don't have to deal with any of the legal compliance issues and the accompanying liability.

share|improve this answer

A few things things to consider:

  • Having the name can help with sorting out some kinds of credit card fraud offline. You can usually call the card issuer directly and validate that the name, card number and address match for example.

  • Some folk use the name as a way to filter out some kinds of pre-payment credit cards (like visa gift cards) that don't have a name. There are better ways of doing this - but it's a way.

  • You sometimes need the cardholder name for other parts of the system (e.g. receipts)

share|improve this answer

I would imagine that it would be at the least slightly beneficial to your professional image to ask for the card holder's name as many potential customers are already expecting to answer this question. All in all I would agree that it is another potential vulnerability to even store the name in the first place.

share|improve this answer

While you're correct that Visa and MasterCard do not validate this information, that's not true of all credit card providers.

American Express actually does validate the "Name" field if you collect it as a merchant and by not collecting it you're more likely to have legitimate payments declined with this card.

share|improve this answer

As said by anthonyryan1, it is required for American Express. So either you ask for/require this information only for American Express (which would mean you would either have to ask the user for the card type or start by letting them input the card number and then asking for the rest, or you disable the field if you see it's not required once a Non-Amex card number was entered) or you always ask for it since it's something customers kinda expect because they are asked for in many other places as well.

But: if you go for the latter, you should at least not make this field mandatory, or add something like "If written on card" to it, because there are also cards without any name on it, such as this one:

enter image description here

...and it is frustrating and confusing when you are asking for information the user can't provide, and since they are unsure what to enter (not everybody knows that in this case it's fine to enter "John Doe" because this information is not verified anyway) they might think they can't use their card and might even abort the checkout in such a case.

See also Name on card, or Card number first?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.