#lordofd.
sonic bane
dawn bronze
Not exactly, that's something that you'd need to build into your application
warped oak
I see, so Stripe "only" handles the payment processing?
dawn bronze
Yes exactly. You need to handle the 'provisioning' of access to your app yourself. The idea is you'd persist subscription status with Stripe against a user/session record in your app via webhooks
warped oak
But if I implement an interface where the user can enter his Stripe log in data, can I get his subscription status to see if he is subscribed to my service and thus use that as authentication?
dawn bronze
Not sure what Stripe log in data you mean?
warped oak
Oh, I was under the impression that you need an account to use Stripe like with PayPal or so
If that's not the case then my approach obviously wouldn't work out
dawn bronze
Let's take a step back. What are you trying to build?
warped oak
To keep things simple an application that offers some form of image processing. I want to sell it in a subscription based model and I was wondering if I can use Stripe's API to determine if a user currently has an active subscription and pays for it and therefore has access to the application or if he doesn't pay and thus gets denied access
dawn bronze
Ok, makes sense. I was confused when you mentioned your customers logging into Stripe. They don't necessarily need a Stripe account in order to purchase from you
warped oak
Ok, so I guess that wouldn't work out then. But thank you for your time
warped oak
If an account is not required then not every user can be authenticated that way
The only other option I would see is to use the transaction ID since both the user and I should have it
Or what would you suggest?
dawn bronze
Well the idea is that your application would have it's own authentication system that you can then persist subscription status with
dawn bronze
Yes
warped oak
Ok, then thanks again and have a nice day 🙂
dawn bronze
you too