• Advanced Card Processing is enabled in WooCommerce PayPal Payments, but the checkout button stays hidden (ppcp-hidden), so customers can’t complete card payments. The card fields (number, expiry, CVV) appear, but the submit button never shows, blocking checkout.We’ve disabled and re-enabled ACP, cleared cache, and checked for console errors. No errors found. The PayPal account is Business | Live.The hosted card fields never finish loading, so the plugin keeps the checkout button hidden

    • This topic was modified 6 months, 1 week ago by maxsakal.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @maxsakal

    Please start with this basic test:
    1. Activate a Default Theme
    Temporarily switch to the Storefront theme. This helps rule out any issues introduced by your current theme.

    2. Disable All Other Plugins
    Deactivate all plugins except for WooCommerce and PayPal Payments.

    3. Test the Checkout Page
    Try placing a test order using the card fields and check if the button still remains hidden.

    4. Re-enable Plugins One by One
    If it starts working, re-enable your plugins one at a time and test the checkout after each activation. This will help isolate the conflicting plugin or code.

     
    If the problem persists even after the conflict test, please open a ticket with our service desk so we can investigate further. You can do that here: 👉 Request Support

    Please include the URL of this forum thread or describe the current behavior again in the ticket to speed things up.

    Let me know how the conflict test goes.

    Kind Regards,
    Krystian

    Thread Starter maxsakal

    (@maxsakal)

    Hello Krystian,
    I tested everything, but the ppcp-hidden class is always added to the place-order button as soon as I select Advanced Card Processing.

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @maxsakal

    I’m not sure how we missed this response, but just in case, please reach out to us. Most likely, re-boarding the plugin should resolve this.

    Feel free to open a new thread or submit a ticket through our service desk. Please include the URL of this thread in your ticket for reference.

    Kind regards,
    Krystian

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

You must be logged in to reply to this topic.