cancel
Showing results for 
Search instead for 
Did you mean: 

Better overview for Payment Methods

0 Kudos

Better overview for Payment Methods

Feature request from avoelkl, posted on GitHub Jan 27, 2015

Given that you run a big shop with a lot of payment methods, some of the payment extensions bring a lot of unneeded/unwanted payment methods with them which appear in the payment method list. Of course you can generate a list and hide them via custom xml (at least in M1), but it's not very handy.

Edit: To get an idea what I mean: Currently we have a shop which has 68 payment methods in this list. These 68 payment methods are added by 10 payment extensions whereas one of them brings > 20 possible payment methods. Only 8 of the payment methods are currently activated in the shop frontend. This makes the list quite confusing.

The list under Configuration > Payment Methods can get quite long so I'd like to suggest to either

1 Highlight activated Payment Methods (having "Enabled" > "Yes")

paymentmethod_var1

2 Put the enabled payment methods on top incl. highlighting

This would require to prioritize the status "Enabled" over the defined sort order.

paymentmethod_var2

Another addition to this could be to sort them into activated and deactivated payment methods and hide the deactivated by default.

I think version 1 would already bring an improvement.

8 Comments
Not applicable
Status changed to: Investigating
 
Not applicable

Comment from andreaspenz, posted on GitHub Jan 28, 2015

this could be very helpful :metal:

Not applicable

Comment from cbmd, posted on GitHub Jan 28, 2015

@avoelkl this could be not just for payment methods, but for all similar functionality, shipping methods for example....

Not applicable

Comment from avoelkl, posted on GitHub Jan 28, 2015

@cbmd yes, at least for shipping methods this would also make sense.

Not applicable

Comment from avoelkl, posted on GitHub Jan 28, 2015

I have updated my issue with some details regarding payment method count.

Not applicable

Comment from vpelipenko, posted on GitHub Jan 28, 2015

@avoelkl, thanks for contribution. This issue will be reviewed by responsible product owner soon.

Not applicable

Comment from asemenenko, posted on GitHub Feb 02, 2015

Hi @avoelkl,

Thank you for contribution. We added this improvement into the backlog. The issue will be updated once it fixed.

/regards Andrii

Not applicable

Comment from vpelipenko, posted on GitHub Feb 04, 2015

Internal ticket: MAGETWO-33515