- This topic has 3 replies, 2 voices, and was last updated 7 months ago by
.
-
Posts
-
-
Hello,
When creating a Stripe Secret Key to provide to the MVX settings, I saw a message from Stripe “For security reasons, you can’t share secret keys with third parties. Create a restricted key instead (see screenshot).
Will a restricted key work for setting up Stripe via MVX? If so, which permissions are needed?
If it only works with a Secret Key, if Stripe itself doesn’t allow it for security reasons, why are you requiring it?
-
-
Hello, Thank you for your cooperation.
We’ve reviewed the Stripe integration on our end using the Secret Key and haven’t encountered the issue you mentioned with secret keys. That said, we understand Stripe’s recent message regarding the use of restricted keys and completely understand your concern.
At this stage, we recommend reaching out directly to Stripe’s support team(https://support.stripe.com/) with the details of your use case — specifically, that you’re integrating Stripe with a third-party plugin like MultiVendorX. You can ask whether a restricted key can be used in this context, and if so, request guidance on the exact scopes or permissions required. Share the details of the error message in detail.
Once Stripe confirms that a restricted key can function similarly to the secret key and provides the appropriate configuration, you’re welcome to use that in the MultiVendorX settings.
Please note that our system currently requires the Secret Key because it ensures full API access for essential functions such as payment processing, refunds, and other backend operations. However, if Stripe verifies that a restricted key can fully support these operations, it should work fine on your end.
Let us know if you need any further assistance – we’re happy to help!
-
-
- The topic ‘Stripe Secret Key Cannot be provided’ is closed to new replies.
