-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Use Stripe Applications instead of Stripe Connect #3618
Labels
Comments
I must admit, I haven't used the Stripe provider myself. It was contributed by @akolpakov here: If Stripe Applications is a completely different provider (different endpoints, different user payload, ...) then it would make sense to add a provider dedicated for that ( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was wondering why django-allauth uses Stripe Connect for auth, where it seems to me that since 2021, Stripe Applications are the way to go. Connect seems to mainly be used for handling payments, and it requires
read_write
scope. For our use case, and I believe many others as well,read_only
is enough, but this scope isn't allowed with Connect, it's only allowed on Stripe Applications.Here's some background info: https://support.stripe.com/questions/security-permissions-and-access-levels-when-connecting-your-stripe-account-to-a-third-party-platform#:~:text=Starting%20in%20July%202021%2C%20Platforms
The text was updated successfully, but these errors were encountered: