Title: Payment method bug
Last modified: November 20, 2023

---

# Payment method bug

 *  Resolved [pegahszi](https://wordpress.org/support/users/pegahszi/)
 * (@pegahszi)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/payment-method-bug/)
 * We use the Iranian payment plugin and we encounter this error with the new WooCommerce
   update. **There are no payment methods available. This may be an error on our
   side. **
   ** Please contact us if you need any help placing your order.**
    -  This topic was modified 2 years, 6 months ago by [pegahszi](https://wordpress.org/support/users/pegahszi/).

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

 *  [Beauty of Code (woo-hc)](https://wordpress.org/support/users/beautyofcode/)
 * (@beautyofcode)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/payment-method-bug/#post-17214866)
 * Hey [@pegahszi](https://wordpress.org/support/users/pegahszi/),
 * Thanks for reaching out!
 * It looks like updating WooCommerce to its latest version has resulted in an error
   on your sites checkout page when using the Iranian payment plugin, is this correct?
 * Are you currently using the [Checkout shortcode](https://woo.com/document/woocommerce-shortcodes/#checkout)
   or the [Checkout block](https://woo.com/document/using-the-new-block-based-checkout/)?
   If the latter, it’s possible that this is due to incompatibility between the 
   payment gateway plugin and the Checkout block. You can see the list of compatible
   payment gateways here:
    - [Checkout Block Supported Payment Gateways](https://woo.com/document/cart-checkout-blocks-status/#section-11)
 * If this is not the case, please clarify if this same issue occurs when using 
   a different payment method/gateway on your site. To check, can you navigate to**
   WooCommerce → Settings → Payments**, temporarily disable the Iranian payment 
   gateway, enable **“Cash on Delivery”**, and see if the issue is resolved:
 * ![](https://i0.wp.com/snipboard.io/FRa47C.jpg?ssl=1)
 * If you do make any changes to your live site, we always recommend ensuring that
   you have a good [backup](https://woocommerce.com/document/backup-wordpress-content/)
   of your [full site and database](https://wordpress.org/support/article/wordpress-backups/)
   before doing this, so that, should something go wrong, you are able to easily
   restore your site to a functioning state.
 * Let us know how this goes!
 *  Thread Starter [pegahszi](https://wordpress.org/support/users/pegahszi/)
 * (@pegahszi)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/payment-method-bug/#post-17215238)
 * By removing the payment and cart pages and creating new pages with shortcode,
   this problem was solved. But I am the developer of this payment plugin. Please
   tell me which part of the code needs to be edited. Because I have many users,
   the plugin must be updated.
 *  [industrialweb](https://wordpress.org/support/users/industrialweb/)
 * (@industrialweb)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/payment-method-bug/#post-17216718)
 * I applied this fix months ago for another issue. Now it has returned. When I 
   edit the checkout page, the shortcode is still there, but all payment methods
   are now broken. Oddly, if I duplicate the Checkout page, the payment methods 
   on _that_ one work… but not the actual page that is assigned as the checkout 
   page.
 * If I set checkout in Woocommerce settings to the newly created page, then _that_
   one is broken just like the original.
    -  This reply was modified 2 years, 6 months ago by [industrialweb](https://wordpress.org/support/users/industrialweb/).
      Reason: clarity
 *  [xue28 (woo-hc)](https://wordpress.org/support/users/xue28/)
 * (@xue28)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/payment-method-bug/#post-17220437)
 * Hi [@pegahszi](https://wordpress.org/support/users/pegahszi/)
 * > By removing the payment and cart pages and creating new pages with shortcode,
   > this problem was solved.
 * We’re glad that the solution suggested above solved your problem here and it 
   is indeed an incompatibility issue.
 * > But I am the developer of this payment plugin. Please tell me which part of
   > the code needs to be edited. Because I have many users, the plugin must be 
   > updated.
 * This is a bit of a complicated topic that would need some customization to address.
   Unfortunately, [custom coding](https://woocommerce.com/support-policy/) is not
   something we can assist with directly. However, I’ll keep this thread open for
   a bit to see if anyone from the community can lend a hand.
 * If you have any other questions related to development or custom coding, don’t
   hesitate to reach out to some of the great resources we have available for support.
   The WooCommerce community is filled with talented open-source developers, and
   many of them are active on the channels listed below:
    - [WooCommerce Developer Resources Portal](https://developer.woocommerce.com/)
    - [WooCommerce Advanced Facebook group](https://www.facebook.com/groups/advanced.woocommerce/)
    - [WooCommerce Developer Slack Channel](https://woocommerce.com/community-slack/)
    - Hire a [WooCommerce Expert](https://woocommerce.com/experts/)
 * Hope this helps!

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

The topic ‘Payment method bug’ is closed to new replies.

 * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504)
 * [WooCommerce](https://wordpress.org/plugins/woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [xue28 (woo-hc)](https://wordpress.org/support/users/xue28/)
 * Last activity: [2 years, 6 months ago](https://wordpress.org/support/topic/payment-method-bug/#post-17220437)
 * Status: resolved