Bug 34919 - Customer never prompted for type of CC
Summary: Customer never prompted for type of CC
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Web Site
Classification: Red Hat
Component: New Store
Version: current
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Cameron Prince
QA Contact: wbirkhea
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-04-05 20:09 UTC by Jay Turner
Modified: 2015-01-07 23:44 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-05-04 00:53:50 UTC


Attachments (Terms of Use)

Description Jay Turner 2001-04-05 20:09:09 UTC
The Customer is not prompted for the type of CC that they will be using. 
Are we just assuming this from the numbers that get entered or what?  In
addition, we never state what CCs are taken at Red Hat, so the user does
not know what cards they can use.

Comment 1 Jason Kohles 2001-04-23 17:19:07 UTC
Fixed... 

The card type is deduced from the number, but I have added a card type popup on
the form anyway, to let people know what types of cards they can use.

Comment 2 Jay Turner 2001-05-01 14:43:01 UTC
We now have a drop-down list where the user can select the type of credit card,
but that selection means nothing.  I just placed an order on
http://webdevel.redhat.com stating that the card was a Visa and providing a
Mastercard number . . . order went through.

Comment 3 Cameron Prince 2001-05-01 15:43:36 UTC
This is field is completely un-needed. We auto detect the card type based on 
the number. Why make them select instead of just saying we take these types of 
cards?

Comment 4 Jay Turner 2001-05-01 15:51:09 UTC
OK, it appears that I have lost this battle.  Remove the list from the site.

Comment 5 Jay Turner 2001-05-01 20:18:09 UTC
Drop-down list needs to be removed from webdevel.

Comment 6 Cameron Prince 2001-05-04 00:53:45 UTC
Select box removed.

Comment 7 Jay Turner 2001-05-04 11:13:24 UTC
This is fixed and showing up on bmantest.meridian.  Closing out this bug.


Note You need to log in before you can comment on or make changes to this bug.