Title: Plugin is killing all payment methods
Last modified: August 31, 2016

---

# Plugin is killing all payment methods

 *  Resolved [refedge](https://wordpress.org/support/users/refedge/)
 * (@refedge)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/plugin-is-killing-all-payment-methods/)
 * Hi
 * I love the idea of your system. so easy and built into the payment methods and
   ordering system and requiring full registration – yes – brilliant. But I can’t
   get it to work. I have a CC gateway and a check method turned on and then added
   Woo-RFQ. I am also using role based methods to only show certain pay methods 
   by role (only wholesalers can pay by check). After installing Woo-RFQ, the other
   2 went away and a new message about shipping and taxes showed up under the cart
   total. The RFQ method did not show up and it said something about no method being
   defined for my state. Seemed odd. I turned Woo-rfq off for now. Can you help 
   me get it to work?
 * [https://wordpress.org/plugins/woo-rfq-for-woocommerce/](https://wordpress.org/plugins/woo-rfq-for-woocommerce/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Neah Plugins](https://wordpress.org/support/users/gplsaver/)
 * (@gplsaver)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/plugin-is-killing-all-payment-methods/#post-7156391)
 * Hi
    I think i understand the problem. You requirement is to allow both RFQ and
   regular checkout through other methods. Right now it is setup to allow either/
   or. We will release the new version soon(next couple of weeks) which allows RFQ
   along with other regular checkout methods which i think will be useful in your
   setting. Although RFQ should show now. I think there is connection to the role
   based methods. Maybe include it and allow it for everyone role?
 *  Plugin Author [Neah Plugins](https://wordpress.org/support/users/gplsaver/)
 * (@gplsaver)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/plugin-is-killing-all-payment-methods/#post-7156394)
 * Can you tell me what your setting are in woocommerce->settings->RFQ ?
 *  Thread Starter [refedge](https://wordpress.org/support/users/refedge/)
 * (@refedge)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/plugin-is-killing-all-payment-methods/#post-7156616)
 * I got it to work but as you said, it is either/or. Please write me an email at
   jason { at } refedge { dot } com. I’d like to talk abou the details of what I’d
   like changed/added.
 *  Plugin Author [Neah Plugins](https://wordpress.org/support/users/gplsaver/)
 * (@gplsaver)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/plugin-is-killing-all-payment-methods/#post-7156618)
 * Hi Jason,
    Today/Tomorrow we will release a new version that will not be an either/
   or proposition. Customers can checkout normally and create an RFQ as well. Please
   check it out.
 *  Plugin Author [Neah Plugins](https://wordpress.org/support/users/gplsaver/)
 * (@gplsaver)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-killing-all-payment-methods/#post-7156638)
 * try 1.4.2 and see if it is helpful . it is no longer either / or

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Plugin is killing all payment methods’ is closed to new replies.

 * ![](https://ps.w.org/woo-rfq-for-woocommerce/assets/icon-128x128.png?rev=2024323)
 * [NP Quote Request for WooCommerce](https://wordpress.org/plugins/woo-rfq-for-woocommerce/)
 * [Support Threads](https://wordpress.org/support/plugin/woo-rfq-for-woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/woo-rfq-for-woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woo-rfq-for-woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woo-rfq-for-woocommerce/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Neah Plugins](https://wordpress.org/support/users/gplsaver/)
 * Last activity: [10 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-killing-all-payment-methods/#post-7156638)
 * Status: resolved