OAuth deprecated for connect

Hello,

Thank you for the information.
Yes, I will start to work on a refactoring of the Stripe V3 plugins in order to support the new workflow for the account link.

Regards,

Hello,

I am really sorry, I've got sick and not in a good shape to work correctly on the plugin.
But I've look at the API and the current state of the plugin ; which was using the "standard" oauth and not the "express" one.
Which gives me a question : do you want a setting to choose between "express" and "standard" ?

Another thing that I've plan for some time now, is to store the current "mode" of the plugin with the vendor stripe account id ; so it will be possible to know when a vendor has been created in "test" mode to not impact the website when switching to "production".
Two problems remain : it will be a major impact during the upgrade (if the plugin is in "test" mode") and the only way to detect the "mode" is to check the beginning of the credential...
But the interesting point is that there is now an API to delete an account (with safe guards in production).

Regards,

Hello,

If you're not using OAuth then you should unpublish the plugin "hikamarket / stripeconnect".
The "hikashoppayment / stripeconnect" plugin is the payment plugin ; while the HikaMarket plugin is there to allow the vendor to link their stripe account with your store.

Regards,

Hello DogPeople,

CF : www.hikashop.com/support/documentation/2...ipeconnect-form.html

Client Id (Connect Only) If you're using the Connect platform, you need to provide your Client Id so vendors will be able to connect with your store.

If you're not using OAuth ; you're not using the "Connect" API so you don't need the ClientID nor the HikaMarket/StripeConnect plugin because your vendors are not paid with stripe (and they do not link their account with your store).

Regards,

Hello,

I've a pre-version of the new Stripe Connect plugins ;which are using "account" API instead of OAuth.

In the same time, I'm performing tests for the new (new new new) recommended API for payments. It's still based on "payment intent" but can now support directly third party methods such as Google Pay, etc.
Since they remove the need of "payment method types" (with they "dynamic oayment methods" feature), it starts to be an API that we can use.... But, their future new API for the Confirmation Token is clearly a regression and does not allow the payment capture during the checkout (so just at the end page).
It's still complicated to navigate in the Stripe documentation, which contains a lot of "deprecated" API and not a clear vision on the "current recommended" one ; various pages are clearly in contradiction.

Nevertheless, if someone is interesting to test the Stripe Connect without OAuth for vendors ; you can use the "contact us" form in order to get more details.

Regards,

Hello,

The new version of the plugins are currently available.
You can download them in order to test the "Account API" instead of the "OAuth API".
Please note that this version of the plugin is still in "beta" and can receive some "hot fixes" thanks to your feedbacks.

Regards,