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 payments not working - Mandatory configuration key STRIPE_CONNECTED_ID not present #392
Comments
I've solved the issue just inserting a new row in the 'Configuration' table containing a new entry |
please check if you have enabled "Platform Mode". If yes, disable it. Platform mode uses Stripe Connect for multi-tenant environments, where the manager of the instance collects fees from (other) event organizers for each ticket sold. I don't think it could be useful for your use case. If you want to collect fees from customers, you can add a new Additional Option with the following policy: |
Hi. |
…NNECTED_ID has been configured (cherry picked from commit fb88035)
this should be solved now. Will be released in the upcoming v1.14 |
Hi.
We are using a PaaS where we have deployed a new version of the db that is using Alf.io. We've found that something wrong happened.
We've checked that now payments with Stripe are not working:
Please, have a look, how we can solve it? We are about to open the sales!
The text was updated successfully, but these errors were encountered: