Trying to replace an old v5 module - Payment Designer

[lesliekirk]

I'm trying to replace the old Payment Designer module. It can assign a Payment Method to Price Groups and Availability Groups. If the AI Miva Chat Assistant is correct, Payment Methods cannot be assigned to Price Groups, only to Availability Groups. Does anyone have a solution for this? This is a must-have need for the store I'mtrying to remove it from.

Also, the Payment Designer module can create Payment Methods such as NET 30 (which is something handled in-house). This store has a few other in-house Payment Methods that would need to be created in order to get this old, obsolete module removed.

[lesliekirk]

Follow on to this - the "groups" are not as important as needing to have a way to add in-house Payment Methods. In addition to NET30, the store used Payment Designer to "Call for Terms" and create a method for eChecks.

[Rick Wilson]

Net 30 is just a PO, which is native. You could rename check for Call for Terms, and when you say eCheck do you mean a real live connected one or something else?

[lesliekirk]

Net 30 is just a PO, which is native. You could rename check for Call for Terms, and when you say eCheck do you mean a real live connected one or something else?

Can the PO be used more than once? The site needs both methods, NET 30 AND Call for Terms. There wasn't any live connection for checks. I would have to ask them how they handled them.

[Rick Wilson]

I meant use PO for Net 30 and Check for Call for Terms.

[lesliekirk]

Now that I've had a minute to get back to this. The Payment Designer module enabled the store owner to create / collect specific fields of information. Both the NET30 and Call for Terms have these fields to collect data on the OPAY screen:
ujm7It.png

The "SmartPay" method collects the same information but includes a message: "When your order is ready to ship
you will receive an email from:yadayada@thestore.com with your Final Total and a SmartPay link to pay your order. Thank you."

[Bruce - PhosphorMedia]

The additional data fields could be handled by wrapping custom order fields on the opay screen.

[lesliekirk]

The additional data fields could be handled by wrapping custom order fields on the opay screen.

Thanks Bruce - PhosphorMedia, I'll give that a try. I just wish there was a tried-and-true (not javascript) way to make these fields required. A simple checkbox in the admin when the field is created would be super nice

[Bruce - PhosphorMedia]

You can simply add 'Required' to the input, and they are forced to make a selection. i.e.,

<input type="text" name="Shipping_Instructions" value="" required >