| Issue 95: | Labels on credit card setup field | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Payment processor screen should include a setting for which credit cards are allowed. This is necessary given that certain processors handle credit cards differently (for example, charging extra for AMEX or Discover). The payment options screen could include a multiselect list for the types of cards accepted for a given payment processor setting. Note: this selector was at one point implemented in the product... |
||||||||||||
,
Oct 23, 2007
(No comment was entered for this change.)
Owner: rs_al...@aeiou.pt
|
|||||||||||||
,
Oct 28, 2007
To be able to configure the accepted credit card types I added a new interface ICreditCardTypeEnumerator. getpaid.core will use an adapter providing ICreditCardTypeEnumerator to return the default credit card lists. PloneGetPaid adds a new adapter that lists the accepted credit cards based on the portal GetPaid configuration.
Status: Fixed
|
|||||||||||||
,
Nov 15, 2007
Reopening to get a small change and note behavior. Change: can we label the columns of credit cards accepted and those available? ie at top of each box "Available", "Accepted". I noticed that when checking out, the list is taken, but my checkout went through even when no card was set. Should we set all to accepted by default? At least for the default payment processor?
Status: Accepted
|
|||||||||||||
,
Nov 15, 2007
oops...nevermind...my order did get rejected on the processing (not sure what I had done before). Still interested in the labels and the question about making things default accepted. |
|||||||||||||
,
Dec 02, 2007
Added default value for accepted credit cards (all types by default), in the schema and in site setup. |
|||||||||||||
,
Dec 02, 2007
About labels in the selection widget, maybe we should find a more general solution.
This field is using OrderedMultiSelectionWidget, like other fields ("buyable content
types", "donable content types", etc), so it will be necessary to pass some
additional parameters in the schema and then use in the widget's template.
|
|||||||||||||
,
Dec 02, 2007
Cool. Defaults look good from a UI perspective. Next round includes: Label the list of "available" credit cards and the list of "accepted" credit cards so users know the different between the two. moving to m2 for that.
Labels: -Milestone-M1 Milestone-M2
|
|||||||||||||
,
Dec 03, 2007
changing name to clarify task.
Summary: Labels on credit card setup field
|
|||||||||||||
,
Dec 19, 2007
This doesn't seems very possible without cusomizing the current widget, the other option would be to add it in the help text. |
|||||||||||||
,
Apr 12, 2008
Added new issue for the usability enhancement: http://code.google.com/p/getpaid/issues/detail?id=191
Status: Fixed
|
|||||||||||||
|
|
|||||||||||||