Invalid Payment Method

  • JustJo

    (@justjo)


    16 hours, 53 minutes ago

    I’ve been trying to fix this for hours, and I really need help now. I have used WooCommerce PayPal on many websites, and the installation has gone smoothly and without a problem, but not this time. For some reason, on the checkout page, whether someone wants to pay using PayPal or a credit card, the transaction doesn’t complete, and the page reloads with a message that says Invalid Payment Method.

    Popups are enabled for this site, so I am at a loss. PayPal works on the Cart but not on the Checkout page.

    I have disconnected and reconnected PayPal several times without success.

    Another issue is that Venmo is checked, but the button doesn’t appear anywhere.

    Thanks in advance for any help I can get!!

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • wpfixpath

    (@wpfixpath)

    15 hours, 2 minutes ago

    Since PayPal works on the Cart page but fails on the Checkout page, I would not treat this as a popup problem first.

    “Invalid Payment Method” usually means WooCommerce is receiving a checkout submission where the selected payment method is not valid/available in that checkout context.

    Check these in order:

    1. Confirm whether the Checkout page is using the Checkout Block or the classic [woocommerce_checkout] shortcode.
    2. Temporarily disable cache/minification for:
    • checkout page
    • cart page
    • account page
    • WooCommerce AJAX endpoints
    • /wp-json/
    1. In WooCommerce → Settings → Payments → PayPal, confirm the PayPal method is enabled for the Checkout location, not only Cart/product express buttons.
    2. Test with only:
    • WooCommerce
    • WooCommerce PayPal Payments
    • default theme
    • no checkout customizer
    • no payment/coupon/cart drawer plugin
    1. Open browser DevTools on checkout and check:
    • console errors
    • network errors
    • whether the checkout request includes the expected payment_method

    Venmo visibility is also eligibility-dependent. It can be enabled in settings and still not appear depending on merchant account, country, buyer/browser/device, and PayPal eligibility. I would debug the main PayPal checkout failure first, then Venmo second.

    Thread Starter JustJo

    (@justjo)

    1 hour, 31 minutes ago

    Thanks for your reply wpfixpath. I built the pages using DIVI Modules, changed the checkout page to shortcodes, and now it works. Thank you so much for your help!! Since you have a genius hat on, could you please tell me how to load the page with the “Ship to a different address” radio button unchecked? At the moment it load checked and it looks very crowded.

    https://prnt.sc/aelmUVVzJaCn

    Thanks in advance!!

    wpfixpath

    (@wpfixpath)

    51 minutes ago

    Glad the shortcode checkout fixed the PayPal issue.

    For the “Ship to a different address?” control, that one is actually a WooCommerce checkbox.

    First try the normal WooCommerce setting:

    WooCommerce → Settings → Shipping → Shipping options / Shipping settings → Shipping destination

    Set it to:

    Default to customer billing address

    Do not choose “Force shipping to customer billing address” unless you want to remove the different shipping address option completely.

    Then clear any checkout/page cache and reload the checkout page in a private/incognito window.

    If Divi or another checkout customization is still forcing it checked, you can force the default state to unchecked with this small snippet:

    add_filter( ‘woocommerce_ship_to_different_address_checked’, ‘__return_false’ );

    Add that through a child theme functions.php file or a code snippets plugin, not by editing WooCommerce core/template files directly.

    Customers will still be able to tick the box manually if their shipping address is different from their billing address.

    • This reply was modified 51 minutes ago by wpfixpath.
Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.