Feature Request: Allow newly added supported_payment_methods to default to disabled for existing merchants

Extensions
1

Hi,

We’re running into a platform-level limitation with our offsite payments extension and wanted to raise it here.

The Issue:

When we add a new payment method to supported_payment_methods in shopify.extension.toml and deploy, it is automatically enabled (checked) for ALL existing merchants — including those who have not opted in.

What We Want:

We’d like new payment methods to be visible in the merchant’s Shopify admin (Settings → Payments), but unchecked/disabled by default, requiring merchants to manually opt in.

There is currently no way to control this default enabled state — no TOML flag, no API, no workaround.

Our Ask:

  1. A configuration flag (e.g. default_enabled = false) in the TOML so new methods don’t auto-enable for existing merchants
  2. Or an API to programmatically control the enabled state per merchant install

Has anyone found a workaround for this? Is this on the roadmap?

Thanks

2

Hey @UseePay_Limited :waving_hand:

Thanks for flagging this. Just to make sure I’m understanding the exact flow here: you’re releasing a new version of the offsite payments extension with an additional value added to supported_payment_methods, and after that release, that newly added payment method is automatically checked/enabled for merchants who already had the payment app installed before the release. Is that right?

Could you share the app name or app ID, the extension handle/UID if you have it, and the before/after supported_payment_methods values from the TOML? A screenshot of the payment method state in Settings > Payments would also help if you’re able to share one.

Once I have that, I can for sure look into this further. Hope to hear from you soon.

3

Hi Alan,

Thanks for your follow-up. Here are the details:

  • App name: Local Payment - UseePay
  • App ID: 71134150657
  • Extension handle: local-payment
  • Extension UID: d52fbfe5-93f4-eb87-171f-b93c4ab4c5a4ed49b1a0

When we deployed version local-payment-prod-11 (version ID: 1014138372097), the newly added payment methods were automatically checked/enabled for merchants who had already installed the app, without any action on their part.

We then rolled back to the previous version local-payment-prod-10 (version ID: 874200268801) to mitigate the impact.

supported_payment_methods before (v10):
“visa”, “master”, “maestro”, “american_express”, “jcb”, “discover”, “diners_club”, “pix”, “bancontact”, “oxxo”, “klarna”, “afterpay”, “affirm”, “sofort”, “giropay”, “pay_easy”, “ideal”, “boleto”, “pse”

supported_payment_methods after (v11, newly added):
“merpay”, “poli”, “gcash”, “pay_pay”, “rabbitlinepay”, “familymart”, “seveneleven”, “lawson”, “circlek”, “ministop”, “sunkus”, “dailyyamazaki”, “seicomart”, “wechatpay”

Could you please clarify if this is expected behavior? And is there any way to deploy new payment methods without them being automatically enabled for existing merchants?

Please let us know if you need any additional information.

Best regards,
UseePay Partnership

Alannotifications@shopifycommunity.discoursemail.com 在 2026年6月26日 周五 4:03 写道：

| Alan_G Shopify Staff
June 25 |

  • | - |

Hey @UseePay_Limited

Thanks for flagging this. Just to make sure I’m understanding the exact flow here: you’re releasing a new version of the offsite payments extension with an additional value added to supported_payment_methods, and after that release, that newly added payment method is automatically checked/enabled for merchants who already had the payment app installed before the release. Is that right?

Could you share the app name or app ID, the extension handle/UID if you have it, and the before/after supported_payment_methods values from the TOML? A screenshot of the payment method state in Settings > Payments would also help if you’re able to share one.

Once I have that, I can for sure look into this further. Hope to hear from you soon.