Thread Starter
pogle
(@pogle)
@jkohlbach , do you know if this would be possible?
Hey @pogle sorry for the slow reply.
If you’re looking at ACH, is this intended for bank transfers? If so, you could use the Invoice gateway for your NET30, then use the Bank Transfers gateway (which is included in WC core) for the ACH.
If you’re using Wholesale Suite, you’ll be able to hide these from regular retain customers using the payment gateway mapping feature.
Here’s a couple articles that might also help you with setting this up:
https://wholesalesuiteplugin.com/kb/how-to-restrict-wholesale-customers-to-use-particular-payment-gateways/
https://wholesalesuiteplugin.com/kb/how-to-let-wholesale-customers-pay-via-invoice-rather-than-regular-gateways/
Let me know if this is what you’re after, if I interpreted the need correctly!
Cheers
Thread Starter
pogle
(@pogle)
Hey Thanks Josh,
We tried the Bank Transfers method, but my company didn’t want to email out our bank info and just wait for the customer to initiate the transaction. We use Quickbooks, and can email the customer directly an invoice with ACH terms, so that would be pretty quick and easy for us, and that’s how we use it for the ‘Net 30’ invoice. I think if there was a way to toggle on a second Invoice gateway just like the one you have, but just call it something different, that would work best for us. But it seems there can only be one ‘Invoice’ gateway natively in Woocommerce, unless there is a way to duplicate your plugin somehow to offer a secondary one that we can change the name of so when we get new order emails we can tell the payment methods apart and send a Quickbook invoice to the customer as needed.
Thread Starter
pogle
(@pogle)
I wouldn’t call this post ‘resolved’ yet. @jkohlbach do you know if there would be a way to just duplicate the functionality as I mentioned above?
Hi @pogle the plugin only adds one gateway unfortunately.
It might be possible to get a dev to duplicate the plugin and have it register a second gateway, but they would also need to be careful to rename all meta and wp_options values used in the code as well.
It’s not a hard thing to do and since updates on this code a pretty rare (it’s a very simple plugin) I don’t see any obstacles in doing that. Unfortunately it’s just not something it can do natively as is.
Hope this gives you an option to explore!
Cheers
