• Almost every update has been re-enabling the “link” feature. Now with the latest update , despite begin disabled , it is forcing the link options to be present and confusing customers .

    They have also implemented an element that you cannot see called “AiAgentPaymentSteering”

    it always amazes me when a company continues to find new ways to aggravate its customer base.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Thu P. a11n

    (@thup90)

    Hi @ctwatty,

    Thanks for flagging both of these, and I get why it’s annoying when a setting doesn’t stay where you put it.

    Regarding the Link option being re-enabled: The Stripe plugin keeps its payment methods in sync with your connected Stripe account, so Link can reappear if it’s still enabled on the Stripe side, even after you switch it off in the plugin. To make it stick, please disable it in both places:

    1. In your store, go to WooCommerce > Settings > Payments > Stripe > Payment Methods, make sure Link by Stripe is unchecked, and Save changes.
    2. Disable Link directly in your Stripe Dashboard under the payment method settings, since the plugin reads the list of enabled methods from Stripe.

    On the “AiAgentPaymentSteering” element: this comes from the Agentic Commerce feature introduced in a recent version. It prepares your catalog so products can be discovered and purchased through AI shopping agents via Stripe’s Agentic Commerce Suite. It does not add or change anything in your normal checkout for regular shoppers.

    If Link still re-enables after following the steps above, please contact our support team by creating a ticket, and I’ll take a closer look.

    The explanation of what AiAgentPaymentSteering does is useful, but it sidesteps the actual complaint: it shipped on and invisible, with no toggle and no changelog callout. That’s the wrong default for anything that exposes your catalog to a new purchasing channel — merchants should opt into agent-facing commerce features deliberately, the same way you’d opt into any other data-sharing integration, not discover the name of an internal flag after the fact.

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

You must be logged in to reply to this review.