-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stripe connect error #372
Comments
Hi @splendidrob please make sure you set the right |
@andrelopez Thank you that got me one step closer! Now I get:
|
@andrelopez I have been through all my Stripe Connect settings and all of the Stripe Payments settings and cant find anything in relation to this. Any advice as to how to progress past the Strip error above? My settings in Stripe as below |
Hi @splendidrob I am looking into this, it looks like Stripe deprecates |
@andrelopez Any updates here? Stripe connect seems to be unusable at present... Just to add an update. I created and connected an account in the stripe dashboard and then edited the database to add the account number to stripe payments vendor. Running a sale via stripe checkout results in the following error in stripe:
|
Sorry about the slow response, it looks like this needs a big refactor that I just started, just a heads up that this may not be ready until January next year |
@andrelopez no problem and thanks for the heads up. I actually ended up building my own direct integration in the end as needed to get it working. |
@andrelopez is this fixed? Does the Stripe Connect (commissions) aspect of the plugin work as we are evaluating it for a project? Thanks! |
Description
Using the example templates as directed in the docs clicking the "connect with stripe" button results in the following stripe error:
This is on a local development server currently - does this require a live environment to work correctly?
Can't see anyway past this to verify a vendor as there isnt anyway to connect stripe via the craft control panel?
Additional info
The text was updated successfully, but these errors were encountered: