• Hi,

    I’m having an issue with the WooCommerce Stripe Payment Gateway plugin and the Link by Stripe payment method.

    After migrating the website to a new server, it looks like Link by Stripe was enabled automatically in WooCommerce/Stripe. The problem is that I cannot disable it.

    Situation:

    In WooCommerce, I go to: WooCommerce → Settings → Payments → Stripe → Payment Methods

    I disable Link by Stripe and save the settings, but after refreshing the page, Link appears enabled again.

    In the WooCommerce Stripe logs, I can see this message:

    link display_preference is not overridable. Please check the platform settings

    What I have already tried:

    I have checked the following:

    1. Optimized Checkout Suite is not enabled in WooCommerce.
    2. I tried disabling Link by Stripe from the WooCommerce payment methods settings, but after saving and refreshing, it becomes enabled again.
    3. In the Stripe Dashboard, the Link payment method appears enabled, but Stripe does not allow me to disable it either.
    4. I reconnected Stripe from WooCommerce, but the issue still persists.
    5. Tried to disable and enable again the plugin, issue persists.

    What I suspect:

    Based on the log message, it looks like WooCommerce is trying to change the display preference for Link, but Stripe does not allow it because this setting is not overridable:

    display_preference is not overridable

    This seems related to a Payment Method Configuration or a platform-controlled setting, possibly the WooCommerce/Stripe platform configuration.

    Question:

    How can I permanently disable Link by Stripe in WooCommerce if Stripe returns this error?

    Is there a way to make WooCommerce use another Payment Method Configuration where Link is disabled?

    Or does WooCommerce/Stripe need to modify the platform configuration so that link.display_preference.overridable can be changed?

    Thanks.

Viewing 2 replies - 16 through 17 (of 17 total)
Viewing 2 replies - 16 through 17 (of 17 total)

You must be logged in to reply to this topic.