Home > Solutions > Checkout Enhancements > Change the look and Change functionality > Payment Methods for Groups v5


Payment Methods for Groups v5 by EMPORIUM PLUS
 
Quantity in Basket: none
Code: WCW-PAYGROUP5

Price: $31.50


Other products by this Partner
Contact Partner

Merchant Version:
Version5
 
Quantity:
 
Sort your payment methods, with your preferred method at the top of the list. You can also restrict payment methods by price group, country ship to or bill to, subtotal range of the products in the order, and categories of products that are in the basket. The payment methods can be displayed as either a select list or radio button grouping. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.

Features:
- Sort payment methods in the order you want them
- Template with tokens to layout methods as select list or radio button group
- Default layout for those who do not have skills with HTML and tokens
- Restrict methods by price group customers
- Restrict methods by ship to or bill to country
- Restrict methods by subtotal range of the order
- Restrict methods based on categories of products that are in the basket
- Can have a different configurable message on the order payment and invoice screens. - Can have a configurable message in the notification emails for each payment method using tokens if the email module is compatible with tokens using the syntax %module|payment|html_message%

Feature Details.
This module's admin screen auto-lists payment methods which are assigned as payment modules for use by the store. In the case of a payment module which configures payment methods at runtime, e.g. available based on login or assigned availability/price group, the store owner can manually add that method to the ordered list.

In addition to the ability to sort the methods, you can restrict any of the methods to specific price group(s) customers. Each payment option can have its own list of acceptable or unacceptable price group customers. The default displays the methods without regard to the price group the customer is in.

You can restrict the payment methods to specific countries. You decide whether you will tie it to the ship to or bill to address. Then you can create a list of acceptable or unacceptable countries. The default displays the methods without regard to countries.

You can further control the payment options your customer sees to a specific subtotal range of products. For example, what if you did not want to accept checks for product subtotal over $50? You would setup the range for check payments as 0.00 to 50.00. The default displays the methods without regard to the order subtotal.

You can also restrict payment methods based on categories of products that are in the basket. Thus, if you have certain categories of products that you do not want to allow a specific payment method, you would enter the category codes into the input. If any of those categories of products were in the basket, the method would be hidden.

Each method can have a different configurable message (text or html) which is displayed using render tokens. This message can be displayed on the order payment screen (the screen after payment method is selected) and on the invoice screen. It can also be in the customer and merchant notification emails if they can implement module tokens in the format %module|paygroup|html_message%. This eliminates the need to install a separate, custom module for checkout messages or rely on the payment module to have the message capability (many do not have it).

The store owner can use the default select list layout or use a template for the layout of the payment option menu. The template can use either select inputs or radio inputs.

The module currently fully supports the mivasql configuration of MIVA Merchant 5. It also supports MySQL as long as load balancing has the data stored on the single MySQL server and permissions are set correctly on the data directories. This would be the case in most of the server setups. If you are using Merchant 5.x and your host is web.com, you will not be able to use this module due to the way they configure their servers. There are no known issues with other hosts.