#mxd

1 messages · Page 1 of 1 (latest)

distant galeBOT
vestal viper
#

Can you describe more what you're trying to achieve?

shell yacht
#

Yes so Im building 2 flask apps, where the sign ins use social social-ins or email/password, then once sign-up, paid features, require an upgrade to a paid membership (all in a python flask app context) with a caveat being a hub and spoke model where a sister application (the second flaskapp) can be logged into with the same credentials and paid membership (if that makes sense)

vestal viper
#

Ok so log-in/authentication functionality for your app shouldn't have anything to do with stripe, right?

shell yacht
#

the paid membership would be stripe

vestal viper
#

Right. So what Stripe functionality are you looking for? Application log-in isn't a stripe feature

#

you'd need to implement your own authentication

shell yacht
#

ahh

#

stripe just does the webhook thing

#

ok got it, so roll my own authentication, and then a webhook type thing would provision access and communicate with the authentication

#

for stripe

vestal viper
#

yeah auth would be handled entirely in your application. you could use webhooks to provision access and store that data in your database

shell yacht
#

storing like a session id or key (is the thing being stored)?

vestal viper
#

What do you mean?

#

I just mean you get a webhook event and then you can keep track of who has paid in your database

#

Any other data you want to store is up to you

shell yacht
#

oh like an enum

#

ok

#

thanks